Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Linux-ALSA <linux-sound@vger.kernel.org>,
	Lars-Peter <lars@metafoo.de>
Subject: Re: ASoC: soc-pcm2.c ?
Date: Wed, 4 Feb 2026 13:33:29 +0100	[thread overview]
Message-ID: <7380b4dd-91e0-43d0-91ed-e475b03f7559@perex.cz> (raw)
In-Reply-To: <87y0l8r95r.wl-tiwai@suse.de>

On 2/4/26 13:21, Takashi Iwai wrote:
> On Wed, 04 Feb 2026 13:10:41 +0100,
> Mark Brown wrote:
>>
>> On Wed, Feb 04, 2026 at 09:50:51AM +0100, Takashi Iwai wrote:
>>
>>> Basically it should be relatively easy to implement a mechanism to
>>> make kcontrols invisible, though; e.g. by introducing a new kcontrol
>>> flag like SNDRV_CTL_ELEM_ACCESS_INVISIBLE, and some machine drivers or
>>> codec drivers may set it up depending on the demands.
>>
>> We already have some support for marking controls as not visible by
>> default IIRC (I'm not immediately remembering the term that was used),
>> the trick is more finding a sensible way to turn it on - with so few
>> custom machine drivers these days it's much harder to enable sensibly.
> 
> IIRC, the existing mechanism isn't about visibility but accessibility
> via SNDRV_CTL_ELEM_ACCESS_INACTIVE flag.
> kcontrols are still exposed to user-space unless they are explicitly
> removed.

But do we want to hide those controls completely ? They may be good for 
debugging. The new flag may be just a hint to user space to not show those 
controls by default (and eventually make it read only or locked for the user 
space - depends on the use).

				Jaroslav				

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  reply	other threads:[~2026-02-04 12:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26  6:41 ASoC: soc-pcm2.c ? Kuninori Morimoto
2026-01-31 13:29 ` Mark Brown
2026-02-03  6:27   ` Kuninori Morimoto
2026-02-03 13:34     ` Pierre-Louis Bossart
2026-02-03 15:16       ` Mark Brown
2026-02-04  6:19         ` Kuninori Morimoto
2026-02-04 12:55           ` Mark Brown
2026-02-03 18:07     ` Liam Girdwood
2026-02-03 18:17       ` Mark Brown
2026-02-04  5:59         ` Kuninori Morimoto
2026-02-04  8:50         ` Takashi Iwai
2026-02-04 12:10           ` Mark Brown
2026-02-04 12:21             ` Takashi Iwai
2026-02-04 12:33               ` Jaroslav Kysela [this message]
2026-02-04 12:45                 ` Mark Brown
2026-02-03  7:45 ` Péter Ujfalusi
2026-02-03 10:11   ` Péter Ujfalusi
2026-02-04  7:28     ` Kuninori Morimoto
2026-02-04 13:07       ` Péter Ujfalusi
2026-02-03 16:18   ` Mark Brown
2026-02-04 10:18     ` Péter Ujfalusi
2026-02-04 12:39       ` 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=7380b4dd-91e0-43d0-91ed-e475b03f7559@perex.cz \
    --to=perex@perex.cz \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --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