From: Mark Brown <broonie@kernel.org>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: Val Packett <val@packett.cool>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ASoC: soc-core: use the device tree card name as long_name
Date: Mon, 14 Sep 2026 12:41:12 +0100 [thread overview]
Message-ID: <aqfdWOx4tf9LmDwu@sirena.co.uk> (raw)
In-Reply-To: <aqfbwDUegHcx-kDn@quark2.heme.sigxcpu.org>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Mon, Sep 14, 2026 at 01:34:24PM +0200, Guido Günther wrote:
> On Mon, Sep 14, 2026 at 12:19:15PM +0100, Mark Brown wrote:
> > opposite choice. Any decision here should be policy based in userspace
> > based on the full system information.
> Thanks for the hint. So that would mean we should do something similar
> to what Lenovo does in UCM (that Val pointed to)?
> https://github.com/alsa-project/alsa-ucm-conf/blob/980fb83651e82c3e53d3a0ab7fa9b7d6fc2d809b/ucm2/Qualcomm/x1e80100/x1e80100.conf
That looks plausibe, or possibly some more generic thing that teaches
UCM about when to use DMI.
> > Please don't send content free pings and please allow a reasonable time
> > for review. People get busy, go on holiday, attend conferences and so
> > on so unless there is some reason for urgency (like critical bug fixes)
> > please allow at least a couple of weeks for review. If there have been
> > review comments then people may be waiting for those to be addressed.
> The original mail was from May so I figured ~ half a year would be o.k.?
> Sorry I got that wrong.
Note the bit in the mail about resending if you think things have been
dropped.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-09-14 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 3:58 Val Packett
2026-07-24 23:12 ` Clayton Craft
2026-09-06 11:50 ` David Heidelberg
2026-09-14 11:00 ` Guido Günther
2026-09-14 11:19 ` Mark Brown
2026-09-14 11:34 ` Guido Günther
2026-09-14 11:41 ` Mark Brown [this message]
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=aqfdWOx4tf9LmDwu@sirena.co.uk \
--to=broonie@kernel.org \
--cc=agx@sigxcpu.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=phone-devel@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=val@packett.cool \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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
all inboxes | Powered by JetHome®