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 v4 2/2] soundwire: amd: refactor bandwidth calculation logic
Date: Wed, 4 Feb 2026 10:22:22 +0530 [thread overview]
Message-ID: <4b5be8db-a42a-40f5-86cf-a3a782cb64ea@amd.com> (raw)
In-Reply-To: <e3b8302c-c12a-4507-b554-d996763187d7@linux.dev>
On 03/02/26 18:51, Pierre-Louis Bossart wrote:
> On 2/2/26 18:25, Mukunda,Vijendar wrote:
>> On 02/02/26 22:35, Pierre-Louis Bossart wrote:
>>> On 1/29/26 07:14, Vijendar Mukunda wrote:
>>>> For current platforms(ACP6.3/ACP7.0/ACP7.1/ACP7.2), AMD SoundWire manager
>>>> doesn't have banked registers for data port programming on Manager's side.
>>>> Need to use fixed block offsets, hstart & hstop for manager ports.
>>>> Earlier amd manager driver has support for 12MHz as a bus clock frequency
>>>> with frame size as 50 x 10 with fixed block offset mapping based on port
>>>> number. Got a requirement to support 6MHz bus clock frequency with
>>>> different frame shapes 50 x 10 and 125 x 2.
>>> the two frame shapes don't carry the same number of bits (500 v. 250). There's probably an additional variable at play, maybe frame rate? Or is 50x10 for 12 MHz and 125x2 for 6 MHz?
>> We need to support 12Mhz as bus clock frequency where frame rate is 48000
>> and number of bits is 500, frame shape as 50 x 10.
>> For 6Mhz bus clock frequency we need to support two different frame shapes
>> i.e number of bits as 250 with frame rate as 48000 and frame shape as
>> 125 x 2 and For second combination number of bits as 500 where frame rate
>> as 24000 and frame size as 50 x10.
>> Few SoundWire peripherals doesn't support 125 x2 frame shape for 6Mhz
>> bus clock frequency. They have explicit requirement for the frame shape.
>> In this scenario, we will use 50 x 10 as frame shape where frame rate as
>> 24000. Based on the platform and SoundWire topology for 6Mhz support
>> frame shape will be decided which is part of SoundWire manager DisCo
>> tables.
> Makes sense, all of the above should be added to the commit message or the code comment, specifically the 125x2 issue with non-conformant devices.
Will update the commit message and re-spin the patch series.
next prev parent reply other threads:[~2026-02-04 4:52 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 [this message]
2026-01-29 19:34 ` [PATCH v4 0/2] soundwire: amd: clock related changes Mario Limonciello
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=4b5be8db-a42a-40f5-86cf-a3a782cb64ea@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