From: qby140326 <qby140326@gmail.com>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>,
Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
Mario Limonciello <mario.limonciello@amd.com>,
Venkata Prasad Potturu <venkataprasad.potturu@amd.com>,
"Dommati, Sunil-kumar" <Sunil-kumar.Dommati@amd.com>
Subject: Re: [PATCH] ASoC: amd: add DMIC support for RPL platform
Date: Wed, 11 Feb 2026 18:46:19 +0800 [thread overview]
Message-ID: <b30d7bfc-f92c-48cf-988c-b7dda4f56d36@gmail.com> (raw)
In-Reply-To: <3cf99569-36a7-4ea1-be73-0605043a95ae@amd.com>
On 2/11/26 17:22, Mukunda,Vijendar wrote:
> There is minor delta between RPL and YC platforms for ACP PDM IO enablement.
> No need to duplicate the code. You can include support for RPL platform in
> yc folder itself. Most of the YC code can be reused.
> We can completely remove the RPL folder itself.
> Add extra checks for ACP PCI revision ID.
Hi Mukunda,
Thanks for the feedback. Could you please elaborate on what the 'minor
delta' specifically entails for the RPL platform compared to YC?
next prev parent reply other threads:[~2026-02-11 10:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 2:07 Mingyou Chen
2026-02-06 17:51 ` Mark Brown
2026-02-07 1:44 ` qby140326
2026-02-07 5:50 ` Mukunda,Vijendar
2026-02-07 12:45 ` Mark Brown
2026-02-11 9:22 ` Mukunda,Vijendar
2026-02-11 10:46 ` qby140326 [this message]
2026-02-11 11:16 ` qby140326
2026-02-11 11:19 ` Mukunda,Vijendar
2026-02-11 11:50 ` [PATCH v2] " Mingyou Chen
2026-02-11 15:21 ` Mario Limonciello
2026-02-12 1:42 ` qby140326
2026-02-12 1:46 ` [PATCH v3] " Mingyou Chen
2026-02-12 5:13 ` Mukunda,Vijendar
2026-02-12 11:15 ` [PATCH v4] " Mingyou Chen
2026-02-12 13:26 ` Mark Brown
2026-02-12 13:45 ` Mario Limonciello
2026-02-11 17:13 ` [PATCH v2] " kernel test robot
2026-02-11 22:35 ` kernel test robot
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=b30d7bfc-f92c-48cf-988c-b7dda4f56d36@gmail.com \
--to=qby140326@gmail.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=venkataprasad.potturu@amd.com \
--cc=vijendar.mukunda@amd.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®