From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: vkoul@kernel.org
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 0/2] soundwire: amd: refactor clock init sequence and
Date: Mon, 22 Dec 2025 13:27:36 +0530 [thread overview]
Message-ID: <890c81e6-e950-43f2-8fd4-2b2e794367ce@amd.com> (raw)
In-Reply-To: <20251222074847.7270-1-Vijendar.Mukunda@amd.com>
On 22/12/25 13:18, 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 calculaiton logic
>
> drivers/soundwire/amd_manager.c | 108 +++++++++++++++++++++++++++---
> drivers/soundwire/amd_manager.h | 4 --
> include/linux/soundwire/sdw_amd.h | 4 ++
> 3 files changed, 101 insertions(+), 15 deletions(-)
>
Cover letter title is discarded. Will update the cover letter title and
resend the patch series in the next spin.
prev parent reply other threads:[~2025-12-22 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 7:48 [PATCH 0/2] soundwire: amd: refactor clock init sequence and Vijendar Mukunda
2025-12-22 7:48 ` [PATCH 1/2] soundwire: amd: add clock init control function Vijendar Mukunda
2025-12-22 7:48 ` [PATCH 2/2] soundwire: amd: refactor bandwidth calculaiton logic Vijendar Mukunda
2026-01-09 17:40 ` Mario Limonciello
2026-01-10 6:00 ` Mukunda,Vijendar
2025-12-22 7:57 ` Mukunda,Vijendar [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=890c81e6-e950-43f2-8fd4-2b2e794367ce@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