alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Martin Povišer" <povik+lin@cutebit.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	Sven Peter <sven@svenpeter.dev>,
	linux-kernel@vger.kernel.org, Hector Martin <marcan@marcan.st>,
	Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Kettenis <kettenis@openbsd.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [RFC PATCH 2/5] HACK: ASoC: Add card->filter_controls hook
Date: Thu, 31 Mar 2022 12:34:29 +0100	[thread overview]
Message-ID: <YkWRxWjQSnJ9f281@sirena.org.uk> (raw)
In-Reply-To: <20220331000449.41062-3-povik+lin@cutebit.org>

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

On Thu, Mar 31, 2022 at 02:04:46AM +0200, Martin Povišer wrote:

> Add a new ASoC card callback for filtering the kcontrols of the card's
> constituent components. This lets the card take over some of the
> controls, deciding their value instead of leaving it up to userspace.

Define "filter".  What is this trying to accomplish?  As a matter of
policy we don't put use case configuration in the kernel, the goal is to
avoid having to update the kernel when people decide to do new things
with their userspace.

> Also, and here's the HACK: part, move dapm_new_widgets call in front
> of the card's late_probe call. This way all kcontrols should have been
> created (and are safe to use) by the time late_probe is called.

This will break any card that adds new controls, you could add a second
call earlier but deleting the existing call is going to break other
users.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-03-31 11:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31  0:04 [RFC PATCH 0/5] Apple Macs machine-level ASoC driver Martin Povišer
2022-03-31  0:04 ` [RFC PATCH 1/5] dt-bindings: sound: Add Apple Macs sound system Martin Povišer
2022-03-31  0:04 ` [RFC PATCH 2/5] HACK: ASoC: Add card->filter_controls hook Martin Povišer
2022-03-31 11:34   ` Mark Brown [this message]
2022-03-31  0:04 ` [RFC PATCH 3/5] HACK: ASoC: Tolerate N-cpus-to-M-codecs links Martin Povišer
2022-04-04 12:28   ` Mark Brown
2022-04-22 14:06     ` Martin Povišer
2022-04-25 12:25       ` Mark Brown
2022-04-25 12:34         ` Martin Povišer
2022-04-25 12:55           ` Mark Brown
2022-04-25 13:11             ` Martin Povišer
2022-04-25 13:46               ` Mark Brown
2022-04-25 13:55                 ` Martin Povišer
2022-03-31  0:04 ` [RFC PATCH 4/5] ASoC: Introduce snd_soc_of_get_dai_link_cpus Martin Povišer
2022-03-31  0:04 ` [RFC PATCH 5/5] ASoC: Add macaudio machine driver Martin Povišer
2022-03-31 11:59   ` Mark Brown
     [not found]     ` <4651D426-BA1A-418F-90E5-278C705DA984@cutebit.org>
2022-03-31 12:56       ` Mark Brown
2022-03-31 12:34 ` [RFC PATCH 0/5] Apple Macs machine-level ASoC driver Mark Brown
2022-03-31 13:28   ` Hector Martin
2022-03-31 14:33     ` Mark Brown
     [not found]   ` <CCE4A06E-6D6F-457D-B3C5-C36209BF38D3@cutebit.org>
2022-03-31 14:18     ` Mark Brown
     [not found]       ` <6D199EAB-FE14-4030-96A7-2E0E89D25FAB@cutebit.org>
2022-03-31 15:36         ` Mark Brown
2022-04-22 10:43           ` Martin Povišer
2022-04-22 11:19             ` Mark Brown
2022-04-22 11:28               ` Martin Povišer
2022-04-22 11:33                 ` Mark Brown
2022-04-22 11:44                   ` Martin Povišer
2022-04-22 12:22                     ` Mark Brown
2022-04-22 12:36                       ` Martin Povišer
2022-04-22 12:44                         ` Mark Brown
2022-04-22 12:53                           ` Martin Povišer
2022-04-22 13:06                             ` Mark Brown
2022-04-22 13:59                               ` Martin Povišer
2022-04-05  9:31 ` (subset) " 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=YkWRxWjQSnJ9f281@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kettenis@openbsd.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=povik+lin@cutebit.org \
    --cc=robh+dt@kernel.org \
    --cc=sven@svenpeter.dev \
    --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).