From: Jaroslav Kysela <perex@perex.cz>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Takashi Iwai <tiwai@suse.com>,
Shuah Khan <shuah@kernel.org>,
linux-sound@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kselftest/alsa: Use card name rather than number in test names
Date: Sat, 13 Jul 2024 09:35:36 +0200 [thread overview]
Message-ID: <e52a5a7e-5358-40d4-8f3d-2adb03018c41@perex.cz> (raw)
In-Reply-To: <31e73e81-e60f-4d0b-b0ac-118f1dc72610@sirena.org.uk>
On 12. 07. 24 20:19, Mark Brown wrote:
> On Fri, Jul 12, 2024 at 06:25:21PM +0200, Jaroslav Kysela wrote:
>> On 12. 07. 24 15:00, Mark Brown wrote:
>
>>> The trouble with the ID field is that it's too short and seems likely to
>>> create collisions, for example HDA stuff just seems to default to NVidia
>>> for nVidia cards which seems very likely to create collisions if someone
>>> has two graphics cards in their system.
>
>> The default IDs are always unique - see snd_card_set_id_no_lock() in
>> sound/core/init.c . Basically, the suffix will follow the device probe order
>> in this case.
>
> Sure, but the genesis of this patch is that probe order isn't
> sufficiently stable and we want to avoid names based on it... using the
> ID will be more likely to work out stable than just pure probe order but
> it's still got the same issue.
The probe order is almost stable for the drivers with the non-deferred probe.
Also, administrators may set persistent ID for complex hardware configuration
cases based on other keys like serial number or so (sysfs/udev).
For long name - the device path may change (USB moved to different port, PCI
card moved to different slot), so the stability of this string is also
questionable.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2024-07-13 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 14:33 Mark Brown
2024-07-11 16:08 ` Jaroslav Kysela
2024-07-11 16:19 ` Mark Brown
2024-07-12 8:21 ` Takashi Iwai
2024-07-12 9:20 ` Jaroslav Kysela
2024-07-12 13:00 ` Mark Brown
2024-07-12 16:25 ` Jaroslav Kysela
2024-07-12 18:19 ` Mark Brown
2024-07-13 6:46 ` Takashi Iwai
2024-07-15 13:18 ` Mark Brown
2024-07-15 13:23 ` Takashi Iwai
2024-07-15 17:31 ` Mark Brown
2024-07-13 7:35 ` Jaroslav Kysela [this message]
2024-07-15 12:48 ` Mark Brown
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=e52a5a7e-5358-40d4-8f3d-2adb03018c41@perex.cz \
--to=perex@perex.cz \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®