From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: vkoul@kernel.org
Cc: yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
sanyog.r.kale@intel.com, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, venkataprasad.potturu@amd.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] soundwire: amd: fixes and improvements
Date: Sat, 7 Jun 2025 05:36:02 +0530 [thread overview]
Message-ID: <d25c5e19-5c3c-46d1-8641-75ae36833331@amd.com> (raw)
In-Reply-To: <20250530054447.1645807-1-Vijendar.Mukunda@amd.com>
On 30/05/25 11:13, Vijendar Mukunda wrote:
> This patch series consists of fixes and improvements for
> AMD Soundwire stack.
@vinod: Could you please help to review the patch series?
This patch series contains fix for system level suspend/resume scenarios
which needs to be landed on OEM kernel base.
>
> Vijendar Mukunda (3):
> soundwire: amd: fix for handling slave alerts after link is down
> soundwire: amd: serialize amd manager resume sequence during
> pm_prepare
> soundwire: amd: cancel pending slave status handling workqueue during
> remove sequence
>
> drivers/soundwire/amd_manager.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
next prev parent reply other threads:[~2025-06-07 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 5:43 Vijendar Mukunda
2025-05-30 5:43 ` [PATCH 1/3] soundwire: amd: fix for handling slave alerts after link is down Vijendar Mukunda
2025-05-30 5:43 ` [PATCH 2/3] soundwire: amd: serialize amd manager resume sequence during pm_prepare Vijendar Mukunda
2025-05-30 5:43 ` [PATCH 3/3] soundwire: amd: cancel pending slave status handling workqueue during remove sequence Vijendar Mukunda
2025-06-07 0:06 ` Mukunda,Vijendar [this message]
2025-06-09 16:17 ` [PATCH 0/3] soundwire: amd: fixes and improvements Vinod Koul
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=d25c5e19-5c3c-46d1-8641-75ae36833331@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.dev \
--cc=sanyog.r.kale@intel.com \
--cc=venkataprasad.potturu@amd.com \
--cc=vkoul@kernel.org \
--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
all inboxes | Powered by JetHome®