From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>,
ALSA development <alsa-devel@alsa-project.org>
Cc: Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v2] ASoC: core: clarify the driver name initialization
Date: Wed, 19 Oct 2022 15:06:29 -0500 [thread overview]
Message-ID: <eb7971c2-f5fe-afb5-9333-4b941b958355@linux.intel.com> (raw)
In-Reply-To: <20220929143754.345144-1-perex@perex.cz>
Hi Jaroslav,
On 9/29/22 09:37, Jaroslav Kysela wrote:
> The driver field in the struct snd_ctl_card_info is a valid
> user space identifier. Actually, many ASoC drivers do not care
> and let to initialize this field using a standard wrapping method.
> Unfortunately, in this way, this field becomes unusable and
> unreadable for the drivers with longer card names. Also,
> there is a possibility to have clashes (driver field has
> only limit of 15 characters).
>
> This change will print an error when the wrapping is used.
> The developers of the affected drivers should fix the problem.
How should we fix this problem?
I see all kinds of errors thrown in our first CI results based on 6.1-rc1:
[ 12.684893] kernel: cml_rt1011_rt5682 cml_rt1011_rt5682: ASoC: driver
name too long 'sof-cml_rt1011_rt5682' -> 'sof-cml_rt1011_'
[ 12.219660] kernel: bxt_da7219_max98357a glk_da7219_mx98357a: ASoC:
driver name too long 'sof-glkda7219max' -> 'sof-glkda7219ma'
I have no idea what is expected here in terms of naming. It's far from
obvious to respect the 15-character limit AND have something
readable/sensible given the proliferation of hardware skews.
Any suggestions?
Thanks,
-Pierre
next prev parent reply other threads:[~2022-10-19 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 14:37 [PATCH v2] ASoC: core: clarify the driver name initialization Jaroslav Kysela
2022-09-29 16:09 ` Nícolas F. R. A. Prado
2022-09-30 8:27 ` Mark Brown
2022-10-19 20:06 ` Pierre-Louis Bossart [this message]
2022-10-20 14:29 ` Jaroslav Kysela
2022-10-20 16:27 ` Pierre-Louis Bossart
2022-10-20 17:46 ` Jaroslav Kysela
2022-10-20 18:13 ` Pierre-Louis Bossart
2022-10-21 6:37 ` Jaroslav Kysela
2022-10-21 14:36 ` Pierre-Louis Bossart
2022-10-24 6:19 ` Jaroslav Kysela
2022-10-24 14:08 ` Pierre-Louis Bossart
2022-10-24 15:29 ` Jaroslav Kysela
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=eb7971c2-f5fe-afb5-9333-4b941b958355@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=perex@perex.cz \
/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