Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Sen Wang <sen@ti.com>
To: <broonie@kernel.org>, <shenghao-ding@ti.com>, <kevin-lu@ti.com>,
	<baojun.xu@ti.com>
Cc: <lgirdwood@gmail.com>, <perex@perex.cz>, <tiwai@suse.com>,
	<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Sen Wang <sen@ti.com>
Subject: [PATCH 0/3] ASoC: codecs: tas675x: misc bugfixes and minor changes
Date: Tue, 30 Jun 2026 13:31:19 -0500	[thread overview]
Message-ID: <20260630183126.2588322-1-sen@ti.com> (raw)

Few miscellaneous bug fixes after the initial merge of TAS675x driver, of
which includes:

- Adding READ_ONCE for all concurrent read params
- Corrected kcontrol bits for temperature range
- Corrected conversion notes in the driver documentation

Sen Wang (3):
  ASoC: codecs: tas675x: use READ_ONCE for params to be used
    concurrently
  ASoC: codecs: tas675x: Fix CHx temperature range register bit fields
  Documentation: sound: tas675x: Fix temperature range and impedance
    documentation

 Documentation/sound/codecs/tas675x.rst | 12 ++++++++----
 sound/soc/codecs/tas675x.c             |  8 ++++----
 2 files changed, 12 insertions(+), 8 deletions(-)

--
2.43.0

             reply	other threads:[~2026-06-30 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 18:31 Sen Wang [this message]
2026-06-30 18:31 ` [PATCH 1/3] ASoC: codecs: tas675x: use READ_ONCE for params to be used concurrently Sen Wang
2026-07-01 18:55   ` Mark Brown
2026-07-02 17:59     ` Wang, Sen
2026-06-30 18:31 ` [PATCH 2/3] ASoC: codecs: tas675x: Fix CHx temperature range register bit fields Sen Wang
2026-06-30 18:31 ` [PATCH 3/3] Documentation: sound: tas675x: Fix temperature range and impedance documentation Sen Wang
2026-07-01 18:53 ` [PATCH 0/3] ASoC: codecs: tas675x: sound bugfixes and minor changes 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=20260630183126.2588322-1-sen@ti.com \
    --to=sen@ti.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=perex@perex.cz \
    --cc=shenghao-ding@ti.com \
    --cc=tiwai@suse.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