From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: vkoul@kernel.org, yung-chuan.liao@linux.intel.com,
sanyog.r.kale@intel.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH 2/2] soundwire: bus: Add internal slave ID and use for IRQs
Date: Fri, 25 Apr 2025 18:35:27 +0200 [thread overview]
Message-ID: <dc069aec-8f34-4745-804b-936e0466559c@linux.dev> (raw)
In-Reply-To: <aAeHgqcQCtuFKW/A@opensource.cirrus.com>
On 4/22/25 14:11, Charles Keepax wrote:
> On Tue, Apr 22, 2025 at 01:50:13PM +0200, Pierre-Louis Bossart wrote:
>> On 4/22/25 12:42, Charles Keepax wrote:
>> I see the patch add a limit during probe, so now that
>> means the number of ACPI devices MUST be lower than 11. That
>> doesn't sound right to me and could cause some configurations
>> to fail. It's perfectly ok to have ghost devices and no limits
>> on how many our BIOS colleagues decide to list.
>
> Yeah it will limit the ACPI to 11 devices. I can't say I am a
> huge fan of the "ghost" devices, like its ACPI it is for
> describing the hardware, so it should describe the hardware.
>
> That said my thinking on this was I have not seen a system with
> more than 4 real devices on a single bus, and not more than a
> couple ghosts in the ACPI. So this didn't look like a big issue.
>
>> Using a dedicated IDA for IRQ mapping looks like a good
>> idea to me, but I don't think you can really use the same IDA
>> for dev_num
>
> If you are really concerned about the ghost devices I could back
> out the part that reuses the ID for the dev_num. However I do
> need to know the maximum number of devices when the IRQ domain is
> allocated. So I can't really see a way to avoid picking a maximum
> number of devices for the bus. What number of real + ghosts would
> you be comfortable with? Although I guess if not using it for the
> dev_num it is then fairly easy to expand if needed so perhaps I
> just back out the dev_num bit, but stick with 11 for now and we
> can expand if necessary?
A maximum of 16 devices total is probably ok. That's 10 more than the worst-case configuration we've seen so far, and I can't think of a case where more than 10 ghost devices would be listed.
prev parent reply other threads:[~2025-04-25 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 10:42 [PATCH 0/2] Fix minor issue in SoundWire slave IRQ mapping Charles Keepax
2025-04-22 10:42 ` [PATCH 1/2] soundwire: bus: Simplify sdw_assign_device_num() Charles Keepax
2025-04-22 10:42 ` [PATCH 2/2] soundwire: bus: Add internal slave ID and use for IRQs Charles Keepax
2025-04-22 11:50 ` Pierre-Louis Bossart
2025-04-22 12:11 ` Charles Keepax
2025-04-25 16:35 ` Pierre-Louis Bossart [this message]
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=dc069aec-8f34-4745-804b-936e0466559c@linux.dev \
--to=pierre-louis.bossart@linux.dev \
--cc=ckeepax@opensource.cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=sanyog.r.kale@intel.com \
--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