mbox series

[V2,0/3] ASoC: codecs: Modify some error codes

Message ID 20231101090211.177125-1-wangweidong.a@awinic.com (mailing list archive)
Headers show
Series ASoC: codecs: Modify some error codes | expand

Message

wangweidong.a@awinic.com Nov. 1, 2023, 9:02 a.m. UTC
From: Weidong Wang <wangweidong.a@awinic.com>

The maximum value that calib can set should be
consistent with the maximum value of re.

An error code should be return when the re is greater
than the maximum value or less than the minimum value

The value of vsense_select should be either 32
or 0 in both cases, so modify the
AW88399_DEV_VDSEL_VSENSE macro to 32.

v1 -> v2: Added changes to the calib range

Weidong Wang (3):
  ASoC: codecs: Modify the maximum value of calib
  ASoC: codecs: Modify the wrong judgment of re value
  ASoC: codecs: Modify macro value error

 sound/soc/codecs/aw88395/aw88395.c | 2 +-
 sound/soc/codecs/aw88399.c         | 6 +++---
 sound/soc/codecs/aw88399.h         | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)


base-commit: fa7d0c17278644aa691f96d08bef8001b762f9cd

Comments

Mark Brown Nov. 2, 2023, 2:26 p.m. UTC | #1
On Wed, 01 Nov 2023 17:02:07 +0800, wangweidong.a@awinic.com wrote:
> The maximum value that calib can set should be
> consistent with the maximum value of re.
> 
> An error code should be return when the re is greater
> than the maximum value or less than the minimum value
> 
> The value of vsense_select should be either 32
> or 0 in both cases, so modify the
> AW88399_DEV_VDSEL_VSENSE macro to 32.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/3] ASoC: codecs: Modify the maximum value of calib
      commit: c9e920ffa752b9047d65041cd70495409c768dd7
[2/3] ASoC: codecs: Modify the wrong judgment of re value
      commit: baf46c3c763809fbeabcff5ec6e2ff3081f755f2
[3/3] ASoC: codecs: Modify macro value error
      commit: b729598c1747576bb9a4c997190be3f7c2915726

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark