From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
ranjani.sridharan@linux.intel.com, hui.wang@canonical.com,
broonie@kernel.org, srinivas.kandagatla@linaro.org,
jank@cadence.com, mengdong.lin@intel.com,
slawomir.blauciak@intel.com, sanyog.r.kale@intel.com,
Bard Liao <yung-chuan.liao@linux.intel.com>,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH 3/3] soundwire: bus_type: add sdw_master_device support
Date: Tue, 12 May 2020 11:08:37 -0500 [thread overview]
Message-ID: <79ee2b4a-c2e3-aba7-8b67-b1a01922d089@linux.intel.com> (raw)
In-Reply-To: <20200512155927.GA4297@vkoul-mobl>
On 5/12/20 10:59 AM, Vinod Koul wrote:
> On 12-05-20, 09:36, Pierre-Louis Bossart wrote:
>> On 5/11/20 10:30 PM, Vinod Koul wrote:
>>> On 11-05-20, 14:00, Pierre-Louis Bossart wrote:
>>>>>> + md = &bus->md;
>>>>>> + md->dev.bus = &sdw_bus_type;
>>>>>> + md->dev.type = &sdw_master_type;
>>>>>> + md->dev.parent = parent;
>>>>>> + md->dev.of_node = parent->of_node;
>>>>>> + md->dev.fwnode = fwnode;
>>>>>> + md->dev.dma_mask = parent->dma_mask;
>>>>>> +
>>>>>> + dev_set_name(&md->dev, "sdw-master-%d", bus->link_id);
>>>>>
>>>>> This give nice sdw-master-0. In DT this comes from reg property. I dont
>>>>> seem to recall if the ACPI/Disco spec treats link_id as unique across
>>>>> the system, can you check that please, if not we would need to update
>>>>> this.
>>>> Table 3 in the Disco for Soundwire 1.0 spec: "all LinkID values are relative
>>>> to the immediate parent Device."
>>>>
>>>> There isn't any known implementation with more than one controller.
>>>
>>> But then it can come in "future" right. So lets try to make it future
>>> proof by not using the link_id (we can expose that as a sysfs if people
>>> want to know). So a global unique id needs to allocated (hint: idr or
>>> equivalent) and used as master_id
>>
>> Can you clarify if you are asking for a global ID for Intel/ACPI platforms,
>> or for DT as well? I can't figure out from the soundwire-controller.yaml
>> definitions if there is already a notion of unique ID.
>
> If ACPI was unique, then I was planning to update the definition below
> to include that. Given that it is not the case, let's make it agnostic to
> underlying firmware.
I am not sure I understand how this would be done.
The call sequence is
sdw_bus_master_add(bus)
sdw_master_device_add(bus, parent, fw_node)
At the bus level, we don't have any information on which controller the
bus is related to.
We'd need to add an argument to sdw_bus_master_add() and have the
controller unique ID be allocated outside of the SoundWire core, hence
my question on whether the DT definition should not be extended.
>
>>
>> properties:
>> $nodename:
>> pattern: "^soundwire(@.*)?$"
>>
>> soundwire@c2d0000 {
>> #address-cells = <2>;
>> #size-cells = <0>;
>> reg = <0x0c2d0000 0x2000>;
>
next prev parent reply other threads:[~2020-05-12 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 18:51 [PATCH 0/3] soundwire: bus_type: add sdw_master_device support Bard Liao
2020-04-29 18:51 ` [PATCH 1/3] soundwire: bus: rename sdw_bus_master_add/delete, add arguments Bard Liao
2020-04-29 18:51 ` [PATCH 2/3] soundwire: bus_type: introduce sdw_slave_type and sdw_master_type Bard Liao
2020-04-29 18:51 ` [PATCH 3/3] soundwire: bus_type: add sdw_master_device support Bard Liao
2020-05-11 6:32 ` Vinod Koul
2020-05-11 8:04 ` Liao, Bard
2020-05-11 9:00 ` Vinod Koul
2020-05-11 11:34 ` Liao, Bard
2020-05-11 11:41 ` Vinod Koul
2020-05-11 19:00 ` Pierre-Louis Bossart
2020-05-12 3:30 ` Vinod Koul
2020-05-12 14:36 ` Pierre-Louis Bossart
2020-05-12 15:59 ` Vinod Koul
2020-05-12 16:08 ` Pierre-Louis Bossart [this message]
2020-05-12 17:01 ` Pierre-Louis Bossart
2020-05-13 10:16 ` Vinod Koul
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=79ee2b4a-c2e3-aba7-8b67-b1a01922d089@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=slawomir.blauciak@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--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