From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org
Subject: Re: [PATCH 00/37] ASoC: Standardize ASoC menu
Date: Tue, 10 Jun 2025 15:35:09 +0300 [thread overview]
Message-ID: <11029ccf-5128-4fe8-bef8-9fd6de316e37@linux.intel.com> (raw)
In-Reply-To: <cbef2f84-9f83-4cf0-87b3-39173099d136@sirena.org.uk>
On 10/06/2025 14:07, Mark Brown wrote:
> On Tue, Jun 10, 2025 at 11:51:41AM +0300, Péter Ujfalusi wrote:
>> We have quite menu empty sub-menus, partially because they would include
>> something which would not be select-able in this arch (Apple, Au1x, etc)
>> and things that does not even have select-able options (SoundWire things
>> for example).
>
> It'd be good if we could hide those, indeed.
>
>> I personally would prefer to keep the 'Sound Open Firmware Support' as
>> it was, probably moved above the CODEC drivers. SOF is more like a small
>> subsystem within ASoC and the stack supports various vendors (Intel,
>> NXP, AMD, Mediatek atm).
With some internal discussion about the menu entry name change for SOF,
we concluded that it would be better to use the following to imply that
it encompasses multiple vendors and platforms:
'Support for Sound Open Firmware (SOF) platforms'
>> The other awkward thing with this change (which was awkward before, but
>> going to be double awkwarded) is that the Intel Machine drivers will be
>> quite detached from SOF, not visible of hinted that they are now under
>> "ASoC support for Intel"
>
> That does make things in line with other platforms, though (as you
> mention later). The issue I guess is to an extent that people might not
> know that SOF is important for a given platform, prehaps it should be
> selected by platforms that need it similarly to what we do with CODEC
> drivers?
At least the match modules are selected from SOF stack and if I'm not
mistaken some or most machine driver will be selected as well, likely no
need for users to hunt down the needed one.
But this is the reverse I guess than what you suggest, The platform
selects the machine driver and not the machine driver the platform(s).
We have generic machine drivers for SOF, used on several platforms (HDA,
SDW as main examples).
Probably this can be reversed, but touching Kconfing never goes without
regression ;)
Apart from this, we also discussed that from our side it is OK to move
Intel SST, AVS (and it's machine drivers) and the 'Intel Machine
drivers' under ASoC support for Intel.
This Intel submenu is going to be a bit unorganized as it will contain
only a portion of the drivers for Intel hardware and some of the
platform drivers (SST/AVS), but we don't want to move things around at
this point.
>
>> The other thing which made me wonder is the 'ASoC support for' repeated,
>> would not be simpler:
>
>> --- ALSA for SoC audio support
>> Analog Devices --->
>> AMD --->
>> Apple ----
>> ...
>
>> The title already tells that this menu is for ASoC.
>
> I don't have a strong opinion on that one.
I'm not sure about this now, probably it is better to keep the 'ASoC
support for' in case one searches for symbols? But that will show t*he
path to the menu entry, indicating that it is ASoC.
GPIO for example adds a postfix, some subsystems do not add the
subsystem name in entries.
I guess whichever looks better?
--
Péter
next prev parent reply other threads:[~2025-06-10 12:35 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 0:43 [PATCH 00/37] ASoC: Standardize ASoC menu Kuninori Morimoto
2025-06-10 3:16 ` Chen-Yu Tsai
2025-06-10 3:46 ` Geraldo Nascimento
2025-06-10 3:49 ` Chen-Yu Tsai
2025-06-10 3:57 ` Kuninori Morimoto
2025-06-10 4:00 ` Geraldo Nascimento
2025-06-10 4:18 ` Kuninori Morimoto
2025-06-10 11:36 ` Mark Brown
2025-06-11 2:00 ` Kuninori Morimoto
2025-06-10 4:19 ` [PATCH 01/37] ASoC: ti: " Kuninori Morimoto
2025-06-10 4:19 ` [PATCH 02/37] ASoC: adi: " Kuninori Morimoto
2025-06-10 4:19 ` [PATCH 03/37] ASoC: amd: " Kuninori Morimoto
2025-06-10 9:57 ` Mukunda,Vijendar
2025-06-10 4:19 ` [PATCH 04/37] ASoC: bcm: " Kuninori Morimoto
2025-06-10 4:20 ` [PATCH 05/37] ASoC: dwc: " Kuninori Morimoto
2025-06-10 4:20 ` [PATCH 06/37] ASoC: fsl: " Kuninori Morimoto
2025-06-10 4:20 ` [PATCH 07/37] ASoC: img: " Kuninori Morimoto
2025-06-10 4:20 ` [PATCH 08/37] ASoC: mxs: " Kuninori Morimoto
2025-06-10 4:20 ` [PATCH 09/37] ASoC: pxa: " Kuninori Morimoto
2025-06-10 4:20 ` [PATCH 10/37] ASoC: sof: " Kuninori Morimoto
2025-06-10 4:20 ` [PATCH 11/37] ASoC: sti: " Kuninori Morimoto
2025-06-10 4:20 ` [PATCH 12/37] ASoC: stm: " Kuninori Morimoto
2025-06-10 4:21 ` [PATCH 13/37] ASoC: au1x: " Kuninori Morimoto
2025-06-10 4:21 ` [PATCH 14/37] ASoC: sdca: " Kuninori Morimoto
2025-06-10 4:21 ` [PATCH 15/37] ASoC: sprd: " Kuninori Morimoto
2025-06-10 4:21 ` [PATCH 16/37] ASoC: apple: " Kuninori Morimoto
2025-06-10 4:21 ` [PATCH 17/37] ASoC: atmel: " Kuninori Morimoto
2025-06-10 4:21 ` [PATCH 18/37] ASoC: intel: " Kuninori Morimoto
2025-06-10 4:21 ` [PATCH 19/37] ASoC: spear: " Kuninori Morimoto
2025-06-10 4:22 ` [PATCH 20/37] ASoC: sunxi: " Kuninori Morimoto
2025-06-10 5:29 ` Chen-Yu Tsai
2025-06-10 4:22 ` [PATCH 21/37] ASoC: tegra: " Kuninori Morimoto
2025-06-10 4:22 ` [PATCH 22/37] ASoC: ux500: " Kuninori Morimoto
2025-06-10 4:22 ` [PATCH 23/37] ASoC: cirrus: " Kuninori Morimoto
2025-06-10 19:20 ` Alexander Sverdlin
2025-06-10 4:22 ` [PATCH 24/37] ASoC: google: " Kuninori Morimoto
2025-06-10 4:22 ` [PATCH 25/37] ASoC: jz4740: " Kuninori Morimoto
2025-06-10 4:22 ` [PATCH 26/37] ASoC: xilinx: " Kuninori Morimoto
2025-06-10 4:22 ` [PATCH 27/37] ASoC: xtensa: " Kuninori Morimoto
2025-06-10 4:22 ` [PATCH 28/37] ASoC: renesas: " Kuninori Morimoto
2025-06-10 4:22 ` [PATCH 29/37] ASoC: generic: " Kuninori Morimoto
2025-07-30 11:38 ` Geert Uytterhoeven
2025-07-30 23:25 ` Kuninori Morimoto
2025-06-10 4:23 ` [PATCH 30/37] ASoC: kirkwood: " Kuninori Morimoto
2025-06-10 4:23 ` [PATCH 31/37] ASoC: loongson: " Kuninori Morimoto
2025-06-10 4:23 ` [PATCH 32/37] ASoC: mediatek: " Kuninori Morimoto
2025-06-10 7:05 ` Matthias Brugger
2025-06-12 1:46 ` Kuninori Morimoto
2025-06-10 4:23 ` [PATCH 33/37] ASoC: rockchip: " Kuninori Morimoto
2025-06-10 4:23 ` [PATCH 34/37] ASoC: starfive: " Kuninori Morimoto
2025-06-10 4:23 ` [PATCH 35/37] ASoC: uniphier: " Kuninori Morimoto
2025-06-10 8:47 ` Masami Hiramatsu
2025-06-10 4:23 ` [PATCH 36/37] ASoC: hisilicon: " Kuninori Morimoto
2025-06-10 4:23 ` [PATCH 37/37] ASoC: sdw_utils: " Kuninori Morimoto
2025-06-10 6:50 ` Péter Ujfalusi
2025-06-10 8:51 ` [PATCH 00/37] ASoC: " Péter Ujfalusi
2025-06-10 11:07 ` Mark Brown
2025-06-10 12:35 ` Péter Ujfalusi [this message]
2025-06-10 12:46 ` Mark Brown
2025-06-11 5:40 ` Kuninori Morimoto
2025-06-11 8:52 ` Péter Ujfalusi
2025-06-11 23:15 ` Kuninori Morimoto
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=11029ccf-5128-4fe8-bef8-9fd6de316e37@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).