[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7b8fe2b6-84cb-e8c8-22aa-2d940a5c68b7@linux.intel.com>
Date: Tue, 31 Jan 2023 21:52:14 -0600
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: "Mukunda,Vijendar" <vijendar.mukunda@....com>,
"Limonciello, Mario" <Mario.Limonciello@....com>,
"broonie@...nel.org" <broonie@...nel.org>,
"vkoul@...nel.org" <vkoul@...nel.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>
Cc: "Katragadda, Mastan" <Mastan.Katragadda@....com>,
"Dommati, Sunil-kumar" <Sunil-kumar.Dommati@....com>,
"Hiregoudar, Basavaraj" <Basavaraj.Hiregoudar@....com>,
Takashi Iwai <tiwai@...e.com>,
Liam Girdwood <lgirdwood@...il.com>,
open list <linux-kernel@...r.kernel.org>,
Nathan Chancellor <nathan@...nel.org>,
"Saba Kareem, Syed" <Syed.SabaKareem@....com>,
"kondaveeti, Arungopal" <Arungopal.kondaveeti@....com>,
Sanyog Kale <sanyog.r.kale@...el.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>
Subject: Re: [PATCH 01/19] ASoC: amd: ps: create platform devices based on acp
config
>>> In above case, two manager instances will be created.
>>> When manager under SWC1 scope tries to add peripheral
>>> device, In sdw_slave_add() API its failing because peripheral
>>> device descriptor uses link id followed by 48bit encoded address.
>>> In above scenarios, both the manager's link id is zero only.
>> what fails exactly? The device_register() ?
>>
>> If yes, what the issue. the device name?
> device_register() is failing because of duplication of
> device name.
>> I wonder if we need to use something like
>>
>> "name shall be sdw:bus_id:link:mfg:part:class"
>>
>> so as to uniquify the device name, if that was the problem.
> Yes correct.
can you check https://github.com/thesofproject/linux/pull/4165 and see
if this works for you? I tested it on Intel platforms.
Powered by blists - more mailing lists