mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Brent Lu <brent.lu@intel.com>,
	alsa-devel@alsa-project.org, Hans de Goede <hdegoede@redhat.com>,
	Bard Liao <bard.liao@intel.com>,
	linux-kernel@vger.kernel.org,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH] ALSA: hda: intel-dsp-config: add JasperLake support
Date: Wed, 01 Dec 2021 07:44:21 +0100	[thread overview]
Message-ID: <s5hsfvczuwq.wl-tiwai@suse.de> (raw)
In-Reply-To: <4e0ec119-2b15-644d-9cab-b2e19b5c0e48@linux.intel.com>

On Wed, 01 Dec 2021 03:32:39 +0100,
Pierre-Louis Bossart wrote:
> 
> 
> 
> On 11/30/21 6:46 PM, Brent Lu wrote:
> > Add rules to select SOF driver for Jasper Lake systems if digital
> > microphone is present or the system is a Chromebook.
> 
> Thanks Brent, yes this is an oversight, we should have added this a long
> time ago.
> 
> I don't think however that this will apply on Takashi's for-next branch,
> it'll conflict with the ALSA: intel-dsp-config: add quirk for JSL
> devices based on ES8336 codec

Actually it's for-linus branch, destined to 5.16-rc4.

> +/* JasperLake */
> +#if IS_ENABLED(CONFIG_SND_SOC_SOF_JASPERLAKE)
> +	{
> +		.flags = FLAG_SOF,
> +		.device = 0x4dc8,
> +		.codec_hid = "ESSX8336",
> +	},
> +#endif
> 
> Do you mind rebasing and resending the update? Let's keep the ESS stuff
> last as done in other platforms, and add your changes on top of this.

Yes, please resubmit.  I can merge and resolve the conflict in my
side, but it's better to get a cleaner patch from the beginning.


thanks,

Takashi

> 
> Thanks!
> 
> > 
> > Signed-off-by: Brent Lu <brent.lu@intel.com>
> > ---
> >  sound/hda/intel-dsp-config.c | 21 +++++++++++++++++++++
> >  1 file changed, 21 insertions(+)
> > 
> > diff --git a/sound/hda/intel-dsp-config.c b/sound/hda/intel-dsp-config.c
> > index b9ac9e9e45a4..be47a1ca12b6 100644
> > --- a/sound/hda/intel-dsp-config.c
> > +++ b/sound/hda/intel-dsp-config.c
> > @@ -299,6 +299,27 @@ static const struct config_entry config_table[] = {
> >  	},
> >  #endif
> >  
> > +/* Jasper Lake */
> > +#if IS_ENABLED(CONFIG_SND_SOC_SOF_JASPERLAKE)
> > +	{
> > +		.flags = FLAG_SOF,
> > +		.device = 0x4dc8,
> > +		.dmi_table = (const struct dmi_system_id []) {
> > +			{
> > +				.ident = "Google Chromebooks",
> > +				.matches = {
> > +					DMI_MATCH(DMI_SYS_VENDOR, "Google"),
> > +				}
> > +			},
> > +			{}
> > +		}
> > +	},
> > +	{
> > +		.flags = FLAG_SOF | FLAG_SOF_ONLY_IF_DMIC,
> > +		.device = 0x4dc8,
> > +	},
> > +#endif
> > +
> >  /* Tigerlake */
> >  #if IS_ENABLED(CONFIG_SND_SOC_SOF_TIGERLAKE)
> >  	{
> > 
> 

  reply	other threads:[~2021-12-01  6:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01  0:46 Brent Lu
2021-12-01  2:32 ` Pierre-Louis Bossart
2021-12-01  6:44   ` Takashi Iwai [this message]
2021-12-02  8:15     ` Lu, Brent
2021-12-02  8:27       ` Takashi Iwai
2022-01-13 10:57         ` Lu, Brent

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=s5hsfvczuwq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bard.liao@intel.com \
    --cc=brent.lu@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.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

all inboxes | Powered by JetHome®