From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: [alsa-devel] [PATCH 1/2] conf/ucm: Add UCM profile for cht-bsw-rt5672 boards
Date: Tue, 3 Sep 2019 11:19:59 -0500 [thread overview]
Message-ID: <df05fb72-7cf3-abbf-63fd-b9a52dd8566f@linux.intel.com> (raw)
In-Reply-To: <dd42dd36-9a4f-e5fe-e8a1-9b3da1152899@redhat.com>
>> I can't recall if I did any work here, took default settings from Bard
>> Liao (when he was a Realtek) or if I just took examples from a
>> Chromebook UCM file. I know there's a Dell tablet which uses this
>> codec, but I just can't recall other devices.
>
> I only have the Lenovo Thinkpad 8 with this codec.
>
>> Also how does the selection of the configs work, I don't see the same
>> thing as in bytcr_rt5640/51 to play with the card long name and
>> quirks. Do you expect the user to select the 'right' configs based on
>> experimental trial-and-error.
>
> Like with the chtrt5645 and chtnau8824 there is no need for any
> kernel side quirks depending on the input/output config.
>
> So the plan is to have a default profile which
> allows selecting all possible inputs / outputs (including
> ones not present) and then have DMI name based profiles,
> like the profile added for the Lenovo Thinkpad 8 in the
> second patch in this series, which only include the
> relevant inputs / outputs for that specific device
> (as we are doing already for the chtrt5645 and chtnau8824
> profiles)
Makes sense, I am not aware of too many devices so DMI would work. I
have a Dell Venue Pro 5855 which is one of the quirks for this codec.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2019-09-03 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 14:58 [PATCH 1/2] conf/ucm: Add UCM profile for cht-bsw-rt5672 boards Hans de Goede
2019-08-31 14:58 ` [alsa-devel] " Hans de Goede
2019-08-31 14:58 ` [PATCH 2/2] conf/ucm: cht-bsw-rt5672: Add board specific profile for Lenovo Thinkpad 8 tablet Hans de Goede
2019-08-31 14:58 ` [alsa-devel] " Hans de Goede
2019-09-02 7:07 ` [PATCH 1/2] conf/ucm: Add UCM profile for cht-bsw-rt5672 boards Takashi Iwai
2019-09-02 7:07 ` [alsa-devel] " Takashi Iwai
2019-09-02 8:31 ` Hans de Goede
2019-09-02 8:31 ` [alsa-devel] " Hans de Goede
2019-09-02 15:32 ` Takashi Iwai
2019-09-03 7:47 ` Hans de Goede
2019-09-03 8:02 ` Jaroslav Kysela
2019-09-03 14:09 ` Pierre-Louis Bossart
2019-09-03 14:54 ` Hans de Goede
2019-09-03 16:19 ` Pierre-Louis Bossart [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=df05fb72-7cf3-abbf-63fd-b9a52dd8566f@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=hdegoede@redhat.com \
--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