public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: dengxiang <dengxiang@nfschina.com>
Cc: tiwai@suse.com, yangyingliang@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SKU: Set to turn off EAPD control for Internal SPK.
Date: Tue, 27 Jun 2023 12:02:46 +0200	[thread overview]
Message-ID: <87ilb9fcjd.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230627055836.23798-1-dengxiang@nfschina.com>

On Tue, 27 Jun 2023 07:58:36 +0200,
dengxiang wrote:
> 
> Due to unknown reason that could not support DSP function on Raptor Lake
> platform using v2.5 sof-bin firmware and snd_hda_intel would disable codec
> wakeup twice during snd_hda_intel initialization, Internal SPK is forbidden
> to put sound outside with snd_hda_intel driver on Unis B760 sku machine.
> Now find out that PIN47 EAPD status is always low for ALC897 chip on
> Unis B760 sku.
> Solution: set to turn off EAPD control again in avoid to mute internal SPK.
> 
> Signed-off-by: dengxiang <dengxiang@nfschina.com>
> ---
>  sound/pci/hda/patch_realtek.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
> index 36c4adfb11e7..bb0ee265eb7f 100644
> --- a/sound/pci/hda/patch_realtek.c
> +++ b/sound/pci/hda/patch_realtek.c
> @@ -534,6 +534,16 @@ static void set_eapd(struct hda_codec *codec, hda_nid_t nid, int on)
>  {
>  	if (get_wcaps_type(get_wcaps(codec, nid)) != AC_WID_PIN)
>  		return;
> +
> +	switch (codec->core.vendor_id) {
> +	case 0x10ec0897:
> +	case 0x80867a50:
> +		on = 0;
> +		break;
> +	default:
> +		break;
> +	}

Sorry, this is definitely no-go.  It matches generically to all
devices that have this codec chip, so you'll break all those devices.


Takashi

      reply	other threads:[~2023-06-27 10:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  5:58 [PATCH] SKU: Set to turn off EAPD control for Internal SPK dengxiang
2023-06-27 10:02 ` 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=87ilb9fcjd.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=dengxiang@nfschina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=yangyingliang@huawei.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