linux-sound.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Cc: broonie@kernel.org, lgirdwood@gmail.com,
	yung-chuan.liao@linux.intel.com, peter.ujfalusi@linux.intel.com,
	linux-sound@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH v5 5/6] ASoC: SDCA: Create ALSA controls from DisCo
Date: Wed, 14 May 2025 14:35:01 +0100	[thread overview]
Message-ID: <aCScBQHCw9xpsCp2@opensource.cirrus.com> (raw)
In-Reply-To: <f04afa43-ed28-4e2f-a3b9-0d9990d2a8ce@linux.dev>

On Wed, May 14, 2025 at 02:39:20PM +0200, Pierre-Louis Bossart wrote:
> On 5/13/25 12:24, Charles Keepax wrote:
> > On Mon, May 12, 2025 at 06:14:00PM +0100, Charles Keepax wrote:
> >> On Mon, May 12, 2025 at 03:53:36PM +0200, Pierre-Louis Bossart wrote:
> >>>
> >>>> +static bool exported_control(struct sdca_control *control)
> >>>> +{
> >>>> +	/* No need to export control for something that only has one value */
> >>>> +	if (control->has_fixed)
> >>>> +		return false;
> >>>
> >>> why is that? It'd simplify userspace if there was always a way to
> >>> get a value, even if it's fixed?
> >>
> >> Well mostly it is because various things in the stack get
> >> sad with a single value control you can't set. If we wanted
> >> to change that I would suggest we add a FIXME. It isn't really
> >> critical and I would really like to get more of this class
> >> driver stuff moving, it has been out for review for a really long
> >> time now.
> >>
> > 
> > Thinking a little more about this user-space is going to have to
> > handle controls not being there as different controls will be
> > exported across different parts anyway, based of which options
> > are implemented. Also we have seen a bit of people hiding
> > controls by changing the access layer. Although sometimes that
> > does result in things that are technically not class conformant
> > but they do work through the Microsoft drivers, so we will likely
> > need to support it anyway.
> 
> Sorry, I missed what the conclusion was, would this filter stay or be removed?

Not sure I was clear either :-)

I have been poking this a little more today and I think I might
have overstated some of the problems here. I think it might be ok
to just mark the controls are read only. Will keep poking it and
will update soon, but kinda hopeful we could actually export
these in the next rev.

Thanks,
Charles

  reply	other threads:[~2025-05-14 13:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 12:42 [PATCH v5 0/6] Add DAPM/ASoC helpers to create SDCA drivers Charles Keepax
2025-05-12 12:42 ` [PATCH v5 1/6] ASoC: SDCA: Remove regmap module macros Charles Keepax
2025-05-12 12:42 ` [PATCH v5 2/6] ASoC: SDCA: Move allocation of PDE delays array Charles Keepax
2025-05-12 12:42 ` [PATCH v5 3/6] ASoC: dapm: Add component level pin switches Charles Keepax
2025-05-12 12:42 ` [PATCH v5 4/6] ASoC: SDCA: Create DAPM widgets and routes from DisCo Charles Keepax
2025-05-12 13:46   ` Pierre-Louis Bossart
2025-05-12 17:08     ` Charles Keepax
2025-05-14 12:15       ` Pierre-Louis Bossart
2025-05-14 13:30         ` Charles Keepax
2025-05-15 14:50           ` Charles Keepax
2025-05-19 17:53             ` Pierre-Louis Bossart
2025-05-13  9:56     ` Charles Keepax
2025-05-14 12:33       ` Pierre-Louis Bossart
2025-05-14 13:33         ` Charles Keepax
2025-05-12 12:42 ` [PATCH v5 5/6] ASoC: SDCA: Create ALSA controls " Charles Keepax
2025-05-12 13:53   ` Pierre-Louis Bossart
2025-05-12 17:14     ` Charles Keepax
2025-05-13 10:24       ` Charles Keepax
2025-05-14 12:39         ` Pierre-Louis Bossart
2025-05-14 13:35           ` Charles Keepax [this message]
2025-05-14 12:19       ` Pierre-Louis Bossart
2025-05-12 12:42 ` [PATCH v5 6/6] ASoC: SDCA: Create DAI drivers " Charles Keepax
2025-05-12 14:00   ` Pierre-Louis Bossart
2025-05-12 17:16     ` Charles Keepax
2025-05-14 12:38       ` Pierre-Louis Bossart
2025-05-14 13:35         ` Charles Keepax

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=aCScBQHCw9xpsCp2@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=yung-chuan.liao@linux.intel.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).