From: Vinod Koul <vkoul@kernel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>
Cc: yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
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 V6 0/2] soundwire: amd: clock related changes
Date: Mon, 09 Mar 2026 08:05:27 +0100 [thread overview]
Message-ID: <177303992707.65210.5693315984444138192.b4-ty@kernel.org> (raw)
In-Reply-To: <20260226065638.1251771-1-Vijendar.Mukunda@amd.com>
On Thu, 26 Feb 2026 12:25:52 +0530, 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
>
> [...]
Applied, thanks!
[1/2] soundwire: amd: add clock init control function
commit: 2a267a8410841ba1c71daa41d1fb2cc21ff23e6b
[2/2] soundwire: amd: refactor bandwidth calculation logic
commit: 27ab4f1e4909a674dfd03058fb9802cae2343a36
Best regards,
--
~Vinod
prev parent reply other threads:[~2026-03-09 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 6:55 [PATCH V6 0/2] soundwire: amd: clock related changes Vijendar Mukunda
2026-02-26 6:55 ` [PATCH V6 1/2] soundwire: amd: add clock init control function Vijendar Mukunda
2026-02-26 6:55 ` [PATCH V6 2/2] soundwire: amd: refactor bandwidth calculation logic Vijendar Mukunda
2026-03-09 6:12 ` [PATCH V6 0/2] soundwire: amd: clock related changes Mukunda,Vijendar
2026-03-11 13:27 ` Harsora, Deep
2026-03-09 7:05 ` Vinod Koul [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=177303992707.65210.5693315984444138192.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=Mario.Limonciello@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=Vijendar.Mukunda@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=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