[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9c5b1503-4dba-4ac1-8fef-9b28fb8bd4b5@linaro.org>
Date: Thu, 23 Nov 2023 10:50:15 +0000
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
alsa-devel@...a-project.org
Cc: tiwai@...e.de, broonie@...nel.org, vkoul@...nel.org,
gregkh@...uxfoundation.org,
Bard liao <yung-chuan.liao@...ux.intel.com>,
Jaroslav Kysela <perex@...ex.cz>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Philippe Ombredanne <pombredanne@...b.com>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] soundwire: introduce controller ID
On 17/10/2023 17:09, Pierre-Louis Bossart wrote:
> This patchset is an alternate proposal to the solution suggested in
> [1], which breaks Intel machine drivers.
>
> The only difference is to use a known controller ID instead of an IDA,
> which wouldn't work with the hard-coded device name.
>
> This patchset was tested on Intel and AMD platforms, testing on
> Qualcomm platforms is required - hence the RFC status.
>
> [1] https://lore.kernel.org/alsa-devel/20231004130243.493617-1-krzysztof.kozlowski@linaro.org/
Tested on X13s.
Tested-by: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
--srini
>
> Krzysztof Kozlowski (1):
> soundwire: fix initializing sysfs for same devices on different buses
>
> Pierre-Louis Bossart (1):
> soundwire: bus: introduce controller_id
>
> drivers/soundwire/amd_manager.c | 8 ++++++++
> drivers/soundwire/bus.c | 4 ++++
> drivers/soundwire/debugfs.c | 2 +-
> drivers/soundwire/intel_auxdevice.c | 3 +++
> drivers/soundwire/master.c | 2 +-
> drivers/soundwire/qcom.c | 3 +++
> drivers/soundwire/slave.c | 12 ++++++------
> include/linux/soundwire/sdw.h | 4 +++-
> sound/soc/intel/boards/sof_sdw.c | 4 ++--
> 9 files changed, 31 insertions(+), 11 deletions(-)
>
Powered by blists - more mailing lists