ASoC: cs35l56: Put OTP register defines in correct address order
Subsystems (3)
Richard Fitzgerald
maintainerPATCH 1/1 ASoC: cs35l56: Put OTP register defines in correct address order
Move the defines for the OTP registers to keep the register defines in order of increasing address.
--- include/sound/cs35l56.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
include/sound/cs35l56.h +3 -3
@@ -32,9 +32,6 @@ struct snd_ctl_elem_value;#define CS35L56_UPDATE_REGS 0x0002A0C#define CS35L56_REFCLK_INPUT 0x0002C04#define CS35L56_GLOBAL_SAMPLE_RATE 0x0002C0C -#define CS35L56_OTP_MEM_53 0x00300D4 -#define CS35L56_OTP_MEM_54 0x00300D8 -#define CS35L56_OTP_MEM_55 0x00300DC#define CS35L56_ASP1_ENABLES1 0x0004800#define CS35L56_ASP1_CONTROL1 0x0004804#define CS35L56_ASP1_CONTROL2 0x0004808
@@ -86,6 +83,9 @@ struct snd_ctl_elem_value;#define CS35L56_DIE_STS1 0x0017040#define CS35L56_DIE_STS2 0x0017044#define CS35L56_DSP_RESTRICT_STS1 0x00190F0 +#define CS35L56_OTP_MEM_53 0x00300D4 +#define CS35L56_OTP_MEM_54 0x00300D8 +#define CS35L56_OTP_MEM_55 0x00300DC#define CS35L56_DSP1_XMEM_PACKED_0 0x2000000#define CS35L56_DSP1_XMEM_PACKED_6143 0x2005FFC#define CS35L56_DSP1_XMEM_UNPACKED32_0 0x2400000
Signature · 1 line
2.47.3
Mark Brown
maintainerQuoted 2 lines · Richard Fitzgerald
Move the defines for the OTP registers to keep the register defines in order of increasing address.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: cs35l56: Put OTP register defines in correct address order
commit: 97af961568c8682c44506c9ad4b26c8a5455ec1d
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