From: <cy_huang@richtek.com>
To: Mark Brown <broonie@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
ChiYuan Huang <cy_huang@richtek.com>, <musk_wang@richtek.com>,
<roy_chiu@richtek.com>, <allen_lin@richtek.com>,
<devicetree@vger.kernel.org>, <linux-sound@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/3] ASoC: Update rtq9128 document and source file
Date: Mon, 12 Jan 2026 09:27:31 +0800 [thread overview]
Message-ID: <cover.1768180827.git.cy_huang@richtek.com> (raw)
From: ChiYuan Huang <cy_huang@richtek.com>
This patch series include two parts
- Update initial setting for rtq9128 specific feature
- Add rtq9154 backward compatible with rtq9128
v2
- Fix commit message typo
ChiYuan Huang (3):
ASoC: codecs: rtq9128: Modify the chip initial setting
dt-bindings: sound: rtq9128: Add rtq9154 backward compatible
ASoC: codecs: rtq9128: Add compatible changes for rtq9154
.../bindings/sound/richtek,rtq9128.yaml | 12 +-
sound/soc/codecs/rtq9128.c | 114 ++++++++++++++++--
2 files changed, 117 insertions(+), 9 deletions(-)
base-commit: f0b9d8eb98dfee8d00419aa07543bdc2c1a44fb1
--
2.34.1
next reply other threads:[~2026-01-12 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 1:27 cy_huang [this message]
2026-01-12 1:27 ` [PATCH v2 1/3] ASoC: codecs: rtq9128: Modify the chip initial setting cy_huang
2026-01-12 1:27 ` [PATCH v2 2/3] dt-bindings: sound: rtq9128: Add rtq9154 backward compatible cy_huang
2026-01-12 14:31 ` Mark Brown
2026-01-12 1:27 ` [PATCH v2 3/3] ASoC: codecs: rtq9128: Add compatible changes for rtq9154 cy_huang
2026-01-13 13:50 ` [PATCH v2 0/3] ASoC: Update rtq9128 document and source file 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.1768180827.git.cy_huang@richtek.com \
--to=cy_huang@richtek.com \
--cc=allen_lin@richtek.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=musk_wang@richtek.com \
--cc=robh@kernel.org \
--cc=roy_chiu@richtek.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