Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Ilyas Gasanov <public@gsnoff.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org
Subject: Re: [PATCH v2] ALSA: hda/realtek: Add PCI SSIDs to HP ProBook quirks
Date: Tue, 02 Dec 2025 17:55:10 +0100	[thread overview]
Message-ID: <87ikeou8lt.wl-tiwai@suse.de> (raw)
In-Reply-To: <20251202154930.74481-1-public@gsnoff.com>

On Tue, 02 Dec 2025 16:49:30 +0100,
Ilyas Gasanov wrote:
> 
> According to HW probes, there exist upgraded variants of HP ProBook
> 440/450 G8 notebook PC hardware, with PCI SSIDs not yet covered:
> 
>  - https://linux-hardware.org/?id=pci:8086-a0c8-103c-8a76
>    (HP ProBook 440 G8, SSID 103C:8A76, Tiger Lake HDA, ALC236)
>  - https://linux-hardware.org/?id=pci:8086-a0c8-103c-8a77
>    (HP ProBook 450 G8, SSID 103C:8A77, Tiger Lake HDA, ALC236)
> 
> The HDA GPIO indices for the mic mute (0x1) and speaker mute (0x2) LEDs
> are virtually guaranteed to be identical for the HP ProBook 440/450 G8
> variants with motherboard SSIDs 8A74/8A75 (BIOS T87) and 8A76/8A77 (BIOS
> T88); especially since spare keyboard parts are interchangeable between
> different revisions of the same notebook models, and thus necessarily
> have the same slot pinouts.
> 
> Signed-off-by: Ilyas Gasanov <public@gsnoff.com>

Thanks, applied now.


Takashi

      reply	other threads:[~2025-12-02 16:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 13:15 [PATCH] ALSA: hda/realtek: Add codec IDs to HP ProBook G8 fixups Ilyas Gasanov
2025-12-02 13:26 ` Takashi Iwai
2025-12-02 14:11   ` Ilyas Gasanov
2025-12-02 14:14     ` Takashi Iwai
2025-12-02 15:49 ` [PATCH v2] ALSA: hda/realtek: Add PCI SSIDs to HP ProBook quirks Ilyas Gasanov
2025-12-02 16:55   ` 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=87ikeou8lt.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=public@gsnoff.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