From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Alban Boyé" <alban.boye@protonmail.com>,
cezary.rojewski@intel.com, broonie@kernel.org,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ASoC: Intel: bytcr_rt5640: Add an extra entry for the Chuwi Vi8 tablet
Date: Wed, 28 Feb 2024 17:17:29 -0500 [thread overview]
Message-ID: <5674b85d-2974-4f1c-9241-42982c1dbbe8@linux.intel.com> (raw)
In-Reply-To: <20240228192807.15130-1-alban.boye@protonmail.com>
On 2/28/24 2:28 PM, Alban Boyé wrote:
> The bios version can differ depending if it is a dual-boot variant of the tablet.
> Therefore another DMI match is required.
>
> Signed-off-by: Alban Boyé <alban.boye@protonmail.com>
> ---
> sound/soc/intel/boards/bytcr_rt5640.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/sound/soc/intel/boards/bytcr_rt5640.c b/sound/soc/intel/boards/bytcr_rt5640.c
> index 03be5e26ec4a..05f38d1f7d82 100644
> --- a/sound/soc/intel/boards/bytcr_rt5640.c
> +++ b/sound/soc/intel/boards/bytcr_rt5640.c
> @@ -685,6 +685,18 @@ static const struct dmi_system_id byt_rt5640_quirk_table[] = {
> BYT_RT5640_SSP0_AIF1 |
> BYT_RT5640_MCLK_EN),
> },
> + { /* Chuwi Vi8 dual-boot (CWI506) */
> + .matches = {
> + DMI_EXACT_MATCH(DMI_SYS_VENDOR, "Insyde"),
> + DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "i86"),
> + /* The above are too generic, also match BIOS info */
> + DMI_MATCH(DMI_BIOS_VERSION, "CHUWI2.D86JHBNR02"),
> + },
> + .driver_data = (void *)(BYTCR_INPUT_DEFAULTS |
> + BYT_RT5640_MONO_SPEAKER |
> + BYT_RT5640_SSP0_AIF1 |
> + BYT_RT5640_MCLK_EN),
> + },
> {
> /* Chuwi Vi10 (CWI505) */
> .matches = {
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
next prev parent reply other threads:[~2024-02-28 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 19:28 Alban Boyé
2024-02-28 22:17 ` Pierre-Louis Bossart [this message]
2024-02-29 8:06 ` Cezary Rojewski
2024-02-29 20:19 ` 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=5674b85d-2974-4f1c-9241-42982c1dbbe8@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alban.boye@protonmail.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
/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®