From: <qianghua.wang@senarytech.com>
To: "'Mark Brown'" <broonie@kernel.org>
Cc: <linux-sound@vger.kernel.org>, <pierre-louis.bossart@linux.dev>,
<yung-chuan.liao@linux.intel.com>,
<liam.r.girdwood@linux.intel.com>,
<peter.ujfalusi@linux.intel.com>, <kai.vehmanen@linux.intel.com>,
<cezary.rojewski@intel.com>, <bo.liu@senarytech.com>
Subject: [PATCH 0/3] ASoC: add Senary SN624x SoundWire SDCA support
Date: Thu, 13 Aug 2026 09:59:10 +0800 [thread overview]
Message-ID: <005301dd2ac7$56d2d8a0$047889e0$@senarytech.com> (raw)
In-Reply-To: <bcd3758c-c7a5-4387-9a35-c14a572a8eb8@sirena.org.uk>
Hi Mark Brown:
My v1 was based on tiwai/sound.git commit f37c5691315d ("Merge
branch 'for-next'", 2026-08-10).
I will rebase onto the latest for-next and resend as v2.
Best regards
Qianghua Wang
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
On Wed, Aug 12, 2026 at 02:59:41PM +0800, qianghua wang wrote:
> From: "qianghua.wang" <qianghua.wang@senarytech.com>
>
> This series adds SoundWire SDCA support for Senary SN624x
> multi-function codecs (jack, speaker amp, DMIC) on Intel Panther Lake.
This doesn't apply against current code, please check and resend.
prev parent reply other threads:[~2026-08-13 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 6:59 [PATCH 0/3] ASoC: add Senary SN624x SoundWire SDCA support qianghua wang
2026-08-12 6:59 ` [PATCH 1/3] ASoC: codecs: add SN624x SDCA SoundWire driver qianghua wang
2026-08-12 8:27 ` Uwe Kleine-König
2026-08-12 8:59 ` reply " qianghua.wang
2026-08-12 18:37 ` Mark Brown
2026-08-13 2:11 ` qianghua.wang
2026-08-12 6:59 ` [PATCH 2/3] ASoC: sdw_utils: add Senary SN624x helpers and codec_info qianghua wang
2026-08-12 6:59 ` [PATCH 3/3] ASoC: Intel: soc-acpi: add SN624x entries for PTL qianghua wang
2026-08-12 18:05 ` [PATCH 0/3] ASoC: add Senary SN624x SoundWire SDCA support Mark Brown
2026-08-13 1:59 ` qianghua.wang [this message]
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='005301dd2ac7$56d2d8a0$047889e0$@senarytech.com' \
--to=qianghua.wang@senarytech.com \
--cc=bo.liu@senarytech.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=yung-chuan.liao@linux.intel.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