From: HyeongJun An <sammiee5311@gmail.com>
To: broonie@kernel.org
Cc: lgirdwood@gmail.com, shenghao-ding@ti.com, kevin-lu@ti.com,
baojun.xu@ti.com, sen@ti.com, marex@denx.de,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] ASoC: codecs: Fix more control definitions that write another control's bits
Date: Sun, 18 Oct 2026 15:47:43 +0900 [thread overview]
Message-ID: <cover.1792135145.git.sammiee5311@gmail.com> (raw)
These are the last fixes found by the overlap scan from the first
series [1]. In sta32x and sta350 a 4-bit field has a maximum of 16, so
the control also writes the bit above it. In tlv320aic32x4 a TAS2505
control uses the wrong register.
[1] https://lore.kernel.org/all/20261008130953.2446692-1-sammiee5311@gmail.com/
HyeongJun An (3):
ASoC: codecs: sta32x: Fix definition of limiter threshold controls
ASoC: codecs: sta350: Fix definition of limiter threshold controls
ASoC: tlv320aic32x4: Fix definition of TAS2505 HP Driver Gain Volume
control
sound/soc/codecs/sta32x.c | 16 ++++++++--------
sound/soc/codecs/sta350.c | 16 ++++++++--------
sound/soc/codecs/tlv320aic32x4.c | 2 +-
sound/soc/codecs/tlv320aic32x4.h | 1 +
4 files changed, 18 insertions(+), 17 deletions(-)
--
2.43.0
next reply other threads:[~2026-10-18 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 6:47 HyeongJun An [this message]
2026-10-18 6:47 ` [PATCH 1/3] ASoC: codecs: sta32x: Fix definition of limiter threshold controls HyeongJun An
2026-10-18 6:47 ` [PATCH 2/3] ASoC: codecs: sta350: " HyeongJun An
2026-10-18 6:47 ` [PATCH 3/3] ASoC: tlv320aic32x4: Fix definition of TAS2505 HP Driver Gain Volume control HyeongJun An
2026-10-18 12:23 ` [PATCH 0/3] ASoC: codecs: Fix more control definitions that write another control's bits Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1792135145.git.sammiee5311@gmail.com \
--to=sammiee5311@gmail.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=marex@denx.de \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®