From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>, vkoul@kernel.org
Cc: yung-chuan.liao@linux.intel.com, Sunil-kumar.Dommati@amd.com,
Mario.Limonciello@amd.com, venkataprasad.potturu@amd.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5 0/2] soundwire: amd: clock related changes
Date: Mon, 23 Feb 2026 10:39:34 +0530 [thread overview]
Message-ID: <4f0b039f-f4b1-49e7-8554-3cdbc6bd866b@amd.com> (raw)
In-Reply-To: <34aa5902-8bb7-4f44-a80b-2f2a7a21c1a4@linux.dev>
On 07/02/26 19:22, Pierre-Louis Bossart wrote:
> On 2/5/26 17:44, Vijendar Mukunda wrote:
>> Refactor clock init sequence to support different bus clock frequencies
>> other than 12Mhz. Modify the bandwidth calculation logic to support 12Mhz,
>> 6Mhz with different frame sizes.
>>
>> Vijendar Mukunda (2):
>> soundwire: amd: add clock init control function
>> soundwire: amd: refactor bandwidth calculation logic
> Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
@Vinod: Could you please review the patch series?
>> Changes since v4:
>> - update commit message
>>
>> Changes since v3:
>> - drop unnecessary debug logs.
>>
>> Changes since v2:
>> - Update commit message
>> - add comments in the code.
>>
>> Changes since v1:
>> - Update Cover letter title.
>> - Fix typo error in commit message.
>> - drop unnecessary condition check in compute params callback.
>>
>> drivers/soundwire/amd_manager.c | 109 +++++++++++++++++++++++++++---
>> drivers/soundwire/amd_manager.h | 4 --
>> include/linux/soundwire/sdw_amd.h | 4 ++
>> 3 files changed, 102 insertions(+), 15 deletions(-)
>>
next prev parent reply other threads:[~2026-02-23 5:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 16:44 Vijendar Mukunda
2026-02-05 16:44 ` [PATCH V5 1/2] soundwire: amd: add clock init control function Vijendar Mukunda
2026-02-23 7:21 ` Vinod Koul
2026-02-23 8:20 ` Mukunda,Vijendar
2026-02-05 16:44 ` [PATCH V5 2/2] soundwire: amd: refactor bandwidth calculation logic Vijendar Mukunda
2026-02-07 13:52 ` [PATCH V5 0/2] soundwire: amd: clock related changes Pierre-Louis Bossart
2026-02-23 5:09 ` Mukunda,Vijendar [this message]
2026-03-09 7:05 ` 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=4f0b039f-f4b1-49e7-8554-3cdbc6bd866b@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=Mario.Limonciello@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=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®