From: Mario Limonciello <superm1@kernel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@amd.com>, vkoul@kernel.org
Cc: yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
Sunil-kumar.Dommati@amd.com, venkataprasad.potturu@amd.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] soundwire: amd: clock related changes
Date: Thu, 29 Jan 2026 13:34:01 -0600 [thread overview]
Message-ID: <39c2e480-cfb5-4f31-9ebc-df769d1cdc73@kernel.org> (raw)
In-Reply-To: <20260129061517.38985-1-Vijendar.Mukunda@amd.com>
On 1/29/26 12:14 AM, 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
>
> 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(-)
>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
prev parent reply other threads:[~2026-01-29 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 6:14 [PATCH v4 0/2] soundwire: amd: clock related changes Vijendar Mukunda
2026-01-29 6:14 ` [PATCH v4 1/2] soundwire: amd: add clock init control function Vijendar Mukunda
2026-01-29 6:14 ` [PATCH v4 2/2] soundwire: amd: refactor bandwidth calculation logic Vijendar Mukunda
2026-02-02 17:05 ` Pierre-Louis Bossart
2026-02-02 17:25 ` Mukunda,Vijendar
2026-02-03 13:21 ` Pierre-Louis Bossart
2026-02-04 4:52 ` Mukunda,Vijendar
2026-01-29 19:34 ` Mario Limonciello [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=39c2e480-cfb5-4f31-9ebc-df769d1cdc73@kernel.org \
--to=superm1@kernel.org \
--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=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