From: Vinod Koul <vkoul@kernel.org>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
Cc: alsa-devel@alsa-project.org, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.intel.com,
Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
vinod.koul@intel.com, venkataprasad.potturu@amd.com,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH V4 00/13] soundwire/SOF: add SoundWire Interface support for AMD SOF stack
Date: Tue, 12 Mar 2024 19:58:49 +0530 [thread overview]
Message-ID: <ZfBmoe4Rv2zjS7PV@matsya> (raw)
In-Reply-To: <581a81f4-e540-4de2-b17d-51bc192ae6ec@amd.com>
On 04-03-24, 12:17, Mukunda,Vijendar wrote:
> On 31/01/24 23:21, Mark Brown wrote:
> > On Mon, Jan 29, 2024 at 11:21:34AM +0530, Vijendar Mukunda wrote:
> >> This patch series is to redesign existing platform device creation logic
> >> for SoundWire managers and Implement generic functions for SoundWire
> >> manager probe, start and exit sequence which are common for both Legacy
> >> (NO DSP enabled) and SOF stack, and add SoundWire Interface support for
> >> AMD SOF stack (ACP 6.3 based platform).
> > The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
> >
> > Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
> >
> > are available in the Git repository at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-soundwire-amd-v6.9
>
> Hi Vinod,
>
> As this patch series is merged in to sound git, Could you please let us know
> when this soundwire patch series will be picked in to Soundwire git.
>
> We need to send few fixes on top of this patch series.
If you had told me earlier I would have pulled. It is late now in merge
window, pls send the patches after rc1 is out in two weeks
BR
--
~Vinod
next prev parent reply other threads:[~2024-03-12 14:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 5:51 [PATCH V4 00/13] soundwire/SOF: add SoundWire Interface support for AMD SOF stack Vijendar Mukunda
2024-01-29 5:51 ` [PATCH V4 01/13] ASoC/soundwire: implement generic api for scanning amd soundwire controller Vijendar Mukunda
2024-01-29 5:51 ` [PATCH V4 02/13] soundwire: amd: update license Vijendar Mukunda
2024-01-30 15:58 ` Vinod Koul
2024-01-29 5:51 ` [PATCH V4 03/13] soundwire: amd: refactor amd soundwire manager device node creation Vijendar Mukunda
2024-01-30 16:00 ` Vinod Koul
2024-01-29 5:51 ` [PATCH V4 04/13] soundwire: amd: implement function to extract slave information Vijendar Mukunda
2024-01-30 15:59 ` Vinod Koul
2024-01-29 5:51 ` [PATCH V4 05/13] soundwire: amd: refactor soundwire pads enable Vijendar Mukunda
2024-01-30 16:00 ` Vinod Koul
2024-01-29 5:51 ` [PATCH V4 06/13] soundwire: amd: refactor register mask structure Vijendar Mukunda
2024-01-30 16:00 ` Vinod Koul
2024-01-29 5:51 ` [PATCH V4 07/13] ASoC: SOF: amd: add code for invoking soundwire manager helper functions Vijendar Mukunda
2024-01-29 5:51 ` [PATCH V4 08/13] ASoC: SOF: amd: add interrupt handling for SoundWire manager devices Vijendar Mukunda
2024-01-29 5:51 ` [PATCH V4 09/13] ASoC: SOF: amd: Add Soundwire DAI configuration support for AMD platforms Vijendar Mukunda
2024-01-29 5:51 ` [PATCH V4 10/13] ASoC: SOF: amd: add machine select logic for soundwire based platforms Vijendar Mukunda
2024-01-29 5:51 ` [PATCH V4 11/13] ASoC: SOF: amd: update descriptor fields for acp6.3 based platform Vijendar Mukunda
2024-01-29 5:51 ` [PATCH V4 12/13] ASoC: SOF: amd: select soundwire dependency flag " Vijendar Mukunda
2024-01-29 5:51 ` [PATCH V4 13/13] ASoC: SOF: amd: refactor acp driver pm ops Vijendar Mukunda
2024-01-31 17:11 ` [PATCH V4 00/13] soundwire/SOF: add SoundWire Interface support for AMD SOF stack Mark Brown
2024-01-31 17:51 ` Mark Brown
2024-03-04 6:47 ` Mukunda,Vijendar
2024-03-12 14:28 ` Vinod Koul [this message]
2024-03-12 16:29 ` Mukunda,Vijendar
2024-03-12 16:46 ` Mark Brown
2024-03-13 5:26 ` Mukunda,Vijendar
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=ZfBmoe4Rv2zjS7PV@matsya \
--to=vkoul@kernel.org \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=venkataprasad.potturu@amd.com \
--cc=vijendar.mukunda@amd.com \
--cc=vinod.koul@intel.com \
--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