From: Vinod Koul <vkoul@kernel.org>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
Cc: broonie@kernel.org, alsa-devel@alsa-project.org,
yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.intel.com,
Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
vinod.koul@intel.com, venkataprasad.potturu@amd.com,
Sanyog Kale <sanyog.r.kale@intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 03/13] drivers: soundwire: amd: refactor amd soundwire manager device node creation
Date: Tue, 23 Jan 2024 12:45:59 +0530 [thread overview]
Message-ID: <Za9nrtvDtCT_SLzY@matsya> (raw)
In-Reply-To: <d8f5ee8b-466e-4069-b06b-41cdc7fa9e40@amd.com>
On 22-01-24, 17:18, Mukunda,Vijendar wrote:
> On 22/01/24 13:27, Vinod Koul wrote:
> > On 10-01-24, 15:14, Vijendar Mukunda wrote:
> >
> >> + * @count: link count
> >> + * @num_slaves: total number of devices exposed across all enabled links
> > should this be not per link?
> No, this will be total count of peripheral devices across all the links.
> This variable will be used in snd_soc_acpi_sdw_link_slaves_found()
> API.
yeah noticed later
> >
> >> + * @link_mask: bit-wise mask listing SoundWire links reported by the
> >> + * Controller
> >> + * @ids: array of slave_id, representing Slaves exposed across all enabled
> >> + * links
> > this does not tell us which device to expect in which link..?
> sdw_extended_slave_id structure contains information about link id as well.
ok
--
~Vinod
next prev parent reply other threads:[~2024-01-23 7:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 9:44 [PATCH V2 00/13] soundwire/SOF: add SoundWire Interface support for AMD SOF stack Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 01/13] ASoC/soundwire: implement generic api for scanning amd soundwire controller Vijendar Mukunda
2024-01-22 7:32 ` Vinod Koul
2024-01-10 9:44 ` [PATCH V2 02/13] drivers: soundwire: amd: update license Vijendar Mukunda
2024-01-22 7:34 ` Vinod Koul
2024-01-22 7:40 ` Mukunda,Vijendar
2024-01-10 9:44 ` [PATCH V2 03/13] drivers: soundwire: amd: refactor amd soundwire manager device node creation Vijendar Mukunda
2024-01-22 7:57 ` Vinod Koul
2024-01-22 11:48 ` Mukunda,Vijendar
2024-01-23 7:15 ` Vinod Koul [this message]
2024-01-10 9:44 ` [PATCH V2 04/13] drivers: soundwire: amd: implement function to extract slave information Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 05/13] drivers: soundwire: amd: refactor soundwire pads enable Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 06/13] drivers: soundwire: amd: refactor register mask structure Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 07/13] ASoC: SOF: amd: add code for invoking soundwire manager helper functions Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 08/13] ASoC: SOF: amd: add interrupt handling for SoundWire manager devices Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 09/13] ASoC: SOF: amd: Add Soundwire DAI configuration support for AMD platforms Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 10/13] ASoC: SOF: amd: add machine select logic for soundwire based platforms Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 11/13] ASoC: SOF: amd: update descriptor fields for acp6.3 based platform Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 12/13] ASoC: SOF: amd: select soundwire dependency flag " Vijendar Mukunda
2024-01-10 9:44 ` [PATCH V2 13/13] ASoC: SOF: amd: refactor acp driver pm ops Vijendar Mukunda
2024-01-18 7:00 ` [PATCH V2 00/13] soundwire/SOF: add SoundWire Interface support for AMD SOF stack Mukunda,Vijendar
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=Za9nrtvDtCT_SLzY@matsya \
--to=vkoul@kernel.org \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=venkataprasad.potturu@amd.com \
--cc=vijendar.mukunda@amd.com \
--cc=vinod.koul@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.