From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
bard.liao@intel.com, pierre-louis.bossart@linux.intel.com
Subject: Re: [PATCH 0/3] soundwire: allocate device_number with IDA
Date: Tue, 23 Aug 2022 22:30:23 +0530 [thread overview]
Message-ID: <YwUHp3ivSktx6/Lo@matsya> (raw)
In-Reply-To: <20220823045004.2670658-1-yung-chuan.liao@linux.intel.com>
On 23-08-22, 12:50, Bard Liao wrote:
> 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.
And how is that an issue that should be fixed?
> To make the device_number unique at the system level, and
Why should we do that...
> unified with the HDaudio/iDISP SDI values, this series allocates the
> dev_number with an IDA restricted between 4 and 11 (inclusive).
Does this not place an artificial restriction that a system can have
only 12 devices if we have unique device
Perhaps a better way would be to use dus:dev combination while dealing
with a device always..??
--
~Vinod
next prev parent reply other threads:[~2022-08-23 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 4:50 [PATCH 0/3] soundwire: allocate device_number with IDA Bard Liao
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 ` Vinod Koul [this message]
2022-08-24 7:42 ` [PATCH 0/3] soundwire: allocate device_number with IDA 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=YwUHp3ivSktx6/Lo@matsya \
--to=vkoul@kernel.org \
--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=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