From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: alsa-devel@alsa-project.org, vkoul@kernel.org
Cc: pierre-louis.bossart@linux.intel.com, vinod.koul@linaro.org,
bard.liao@intel.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] soundwire: allocate device_number with IDA
Date: Tue, 23 Aug 2022 12:50:01 +0800 [thread overview]
Message-ID: <20220823045004.2670658-1-yung-chuan.liao@linux.intel.com> (raw)
The device_number is currently allocated in the scope of each bus and does
not need to be unique at the system level.
This leads e.g. on Dell devices with three or four Device1 on different
bus segments. To make the device_number unique at the system level, and
unified with the HDaudio/iDISP SDI values, this series allocates the
dev_number with an IDA restricted between 4 and 11 (inclusive).
Pierre-Louis Bossart (3):
soundwire: bus: rename sdw_ida as sdw_bus_ida
soundwire: bus: allow device number to be unique at system level
soundwire: intel: set dev_num_ida_min
drivers/soundwire/bus.c | 29 ++++++++++++++++++++---------
drivers/soundwire/intel.c | 4 ++++
include/linux/soundwire/sdw.h | 4 ++++
3 files changed, 28 insertions(+), 9 deletions(-)
--
2.25.1
next reply other threads:[~2022-08-23 4:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 4:50 Bard Liao [this message]
2022-08-23 4:50 ` [PATCH 1/3] soundwire: bus: rename sdw_ida as sdw_bus_ida Bard Liao
2022-08-23 4:50 ` [PATCH 2/3] soundwire: bus: allow device number to be unique at system level Bard Liao
2022-08-23 4:50 ` [PATCH 3/3] soundwire: intel: set dev_num_ida_min Bard Liao
2022-08-23 17:00 ` [PATCH 0/3] soundwire: allocate device_number with IDA Vinod Koul
2022-08-24 7:42 ` Pierre-Louis Bossart
2022-08-30 4:46 ` Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2022-07-13 14:25 Bard Liao
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=20220823045004.2670658-1-yung-chuan.liao@linux.intel.com \
--to=yung-chuan.liao@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
/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