Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Singh, Guneshwor" <guneshwor.o.singh@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: PeiSen Hou <pshou@realtek.com>,
	ALSA ML <alsa-devel@alsa-project.org>,
	kailang@realtek.com, CHLin <doomko@realtek.com>
Subject: Re: [PATCH] ALSA: hda/realtek - Enable jack detection for Intel CFL + ALC700
Date: Wed, 15 Nov 2017 08:28:37 +0530	[thread overview]
Message-ID: <20171115025837.GA20938@g2> (raw)
In-Reply-To: <s5h8tf99bjm.wl-tiwai@suse.de>

On Tue, Nov 14, 2017 at 03:31:41PM +0100, Takashi Iwai wrote:
> On Tue, 14 Nov 2017 04:00:08 +0100,
> Guneshwor Singh wrote:
> > 
> > From: PeiSen Hou <pshou@realtek.com>
> > 
> > ALC700 has jack detection disabled by default in Intel Coffeelake
> > Reference board. To enable it, this fixup is required.
> > 
> > Signed-off-by: PeiSen Hou <pshou@realtek.com>
> > Signed-off-by: Guneshwor Singh <guneshwor.o.singh@intel.com>
> > ---
> >  sound/pci/hda/patch_realtek.c | 17 +++++++++++++++++
> >  1 file changed, 17 insertions(+)
> > 
> > diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
> > index 0ce71111b4e3..61ef08173b1c 100644
> > --- a/sound/pci/hda/patch_realtek.c
> > +++ b/sound/pci/hda/patch_realtek.c
> > @@ -5264,6 +5264,7 @@ enum {
> >  	ALC233_FIXUP_LENOVO_MULTI_CODECS,
> >  	ALC294_FIXUP_LENOVO_MIC_LOCATION,
> >  	ALC700_FIXUP_INTEL_REFERENCE,
> > +	ALC700_FIXUP_INTEL_CFL,
> >  };
> >  
> >  static const struct hda_fixup alc269_fixups[] = {
> > @@ -6074,6 +6075,21 @@ static const struct hda_fixup alc269_fixups[] = {
> >  			{}
> >  		}
> >  	},
> > +	[ALC700_FIXUP_INTEL_CFL] = {
> > +		.type = HDA_FIXUP_VERBS,
> > +		.v.verbs = (const struct hda_verb[]) {
> > +			/* Enables internal speaker */
> > +			{0x20, AC_VERB_SET_COEF_INDEX, 0x45},
> > +			{0x20, AC_VERB_SET_PROC_COEF, 0x5289},
> > +			{0x20, AC_VERB_SET_COEF_INDEX, 0x4a},
> > +			{0x20, AC_VERB_SET_PROC_COEF, 0x201b},
> 
> I see only one bit here is different from the previous quirk for Intel
> reference board.  Do we really need to keep both quirks separately?
> Or maybe this new one is the correct verb in anyway?
> 
> 

Will check if both are needed. Otherwise the same quirk can be reused
(by correcting the older verb if required). Thanks for the review.

> thanks,
> 
> Takashi

      reply	other threads:[~2017-11-15  2:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14  3:00 [PATCH] ALSA: hda/realtek - Enable jack detection for Intel CFL + ALC700 Guneshwor Singh
2017-11-14 14:31 ` Takashi Iwai
2017-11-15  2:58   ` Singh, Guneshwor [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=20171115025837.GA20938@g2 \
    --to=guneshwor.o.singh@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=doomko@realtek.com \
    --cc=kailang@realtek.com \
    --cc=pshou@realtek.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