From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org, Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: Re: [PATCH] ALSA: usb-audio: Use the new macro for HP Dock rename quirks
Date: Mon, 08 Jun 2020 11:22:04 +0200 [thread overview]
Message-ID: <s5ha71d6hfn.wl-tiwai@suse.de> (raw)
In-Reply-To: <0b36a395-0bf3-c853-1640-6356a01e2200@perex.cz>
On Mon, 08 Jun 2020 11:01:43 +0200,
Jaroslav Kysela wrote:
>
> Dne 08. 06. 20 v 10:44 Takashi Iwai napsal(a):
> > On Mon, 08 Jun 2020 10:37:12 +0200,
> > Jaroslav Kysela wrote:
> >>
> >> Dne 08. 06. 20 v 9:15 Takashi Iwai napsal(a):
> >>> Replace the open-code with the new QUIRK_DEVICE_PROFILE() macro for
> >>> simplicity.
> >>>
> >>> Fixes: 0c5086f56999 ("ALSA: usb-audio: Add vendor, product and profile name for HP Thunderbolt Dock")
> >>> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> >>> ---
> >>
> >> Takashi, could we export the profile (hint) for new USB cards via the
> >> components string - snd_component_add()? The long name seems not
> >> appropriate for this. It's a GUI string (which is mangled now).
> >
> > It's possible, and maybe we should move to it, but we'd need to
> > provide in card->longname for now because the component support in
> > user-space side isn't in major releases yet. The longname is ugly,
> > but that's the only way that works stably right now.
> >
> > Also, we need a common helper function for adding the component string
> > in the kernel side, too, not specific to USB-audio.
>
> There is already snd_component_add() function, so we need to settle
> only the identification prefix for those "model" strings.
>
> It would be nice to duplicate this info for the moment (the components
> string should be shorter than used for long name).
Yes, what we need a concrete definition. The implementation in
kernel-side must be easy :)
> Perhaps, we can just add "hw:<hint>" component string for the more
> finer hardware identification, like:
>
> $ amixer -c 0 info
> Components : 'USB0bda:58fe hw:VideoMic'
I don't mind what form, but would the example above work as a UCM
profile properly?
thanks,
Takashi
next prev parent reply other threads:[~2020-06-08 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 7:15 [PATCH] ALSA: usb-audio: Use the new macro for HP Dock rename quirks Takashi Iwai
2020-06-08 8:37 ` Jaroslav Kysela
2020-06-08 8:44 ` Takashi Iwai
2020-06-08 9:01 ` Jaroslav Kysela
2020-06-08 9:22 ` Takashi Iwai [this message]
2020-06-08 9:38 ` Jaroslav Kysela
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=s5ha71d6hfn.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kai.heng.feng@canonical.com \
--cc=perex@perex.cz \
/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