linux-kernel - Re: [PATCH] ASoC: soc-core: add the driver component name to the component struc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 7 Dec 2021 13:08:33 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Köry Maincent <kory.maincent@...tlin.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        alexandre.belloni@...tlin.com, thomas.petazzoni@...tlin.com,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH] ASoC: soc-core: add the driver component name to the
 component struc

On Tue, Dec 07, 2021 at 09:47:32AM +0100, Köry Maincent wrote:
> Mark Brown <broonie@...nel.org> wrote:

> > Why is one device registering multiple components in the first place?

> Because the sound components are more and more complex. Why they shouldn't?

In what way are they more complex?  

> It seems to be already the case:
> sound/soc/codecs/cros_ec_codec.c
> sound/soc/fsl/fsl_easrc.c
> sound/soc/mediatek/mt*/mt*-afe-pcm.c
> sound/soc/sunxi/sun4i-codec.c
> sound/soc/soc-utils.c

Quite a few (I think all?) of these are quite old and and are the result
of refactoring from pre-component code rather than modern drivers, it's
likely there is no concrete reason for them to behave as they do.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)