All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kailang <kailang@realtek.com>
Cc: " \(alsa-devel@alsa-project.org\)" <alsa-devel@alsa-project.org>
Subject: Re: HP NB right speaker no sound
Date: Thu, 30 Jul 2020 13:42:34 +0200	[thread overview]
Message-ID: <s5hy2n1cjpx.wl-tiwai@suse.de> (raw)
In-Reply-To: <022139c65ccc443bb94df7f11118a709@realtek.com>

On Thu, 30 Jul 2020 10:53:35 +0200,
Kailang wrote:
> 
> 
> 
> > -----Original Message-----
> > From: Takashi Iwai <tiwai@suse.de>
> > Sent: Thursday, July 30, 2020 4:17 PM
> > To: Kailang <kailang@realtek.com>
> > Cc: (alsa-devel@alsa-project.org) <alsa-devel@alsa-project.org>
> > Subject: Re: HP NB right speaker no sound
> > 
> > On Thu, 30 Jul 2020 07:53:57 +0200,
> > Kailang wrote:
> > On Thu, 30 Jul 2020 07:53:57 +0200,
> > Kailang wrote:
> > >
> > > Hi Takashi,
> > >
> > > HP NB platform right side speaker no sound.
> > > Attach patch was help EC to initial I2S Amp normally.
> > > Thanks.
> > >
> > > BR,
> > > Kailang
> > > [2 0000-alc285-hp-amp-init.patch <application/octet-stream (base64)>]
> > >
> > >
> > > Hi Takashi,
> > >
> > > HP NB platform right side speaker no sound.
> > > Attach patch was help EC to initial I2S Amp normally.
> > > Thanks.
> > >
> > > BR,
> > > Kailang
> > 
> > Thanks, applied now.
> > 
> > If I understand correctly from your patch description, it implies the
> > GPIO1 high, and that's already done in the chained quirk?
> No.
> BIOS verb table had fill GPIO1 to high already.
> BIOS verb table had fill PD pin to test mode.
> It will cause GPIO1 to low.
> This case just need to disable PD pin test mode. GPIO1 will return to high.

OK, thanks for the details.


Takashi

      reply	other threads:[~2020-07-30 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30  5:53 HP NB right speaker no sound Kailang
2020-07-30  8:17 ` Takashi Iwai
2020-07-30  8:53   ` Kailang
2020-07-30 11:42     ` Takashi Iwai [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=s5hy2n1cjpx.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kailang@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.