Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Steven 'Steve' Kendall" <skend@chromium.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Override Intel Apollo Lake audio class on Gauteng W3S laptops [8086:5a98]
Date: Thu, 19 Nov 2026 00:57:51 +0000	[thread overview]
Message-ID: <sashiko-outbox-222271@kernel.org> (raw)
In-Reply-To: <20261119-gauteng-audio-class-set-v1-1-e81d6fd620ad@chromium.org>

> Gauteng Education Dept MODEL-W3S laptops advertise PCI class 0x040300
> to use the legacy HDA driver rather than the Audio DSP on the Intel
> Apollo Lake audio controller ([8086:5a98]). However, this board uses an
> I2S ES8336 codec with no analog HDA codec, and its firmware otherwise
> sets up the hardware to enable the DSP.
> 
> Add a PCI header fixup for [8086:5a98] on Gauteng W3S systems to
> override class 0x040300 to 0x040100 so the SOF driver can claim the
> device. Notably this fixes the internal speakers and headphones but
> not jack detection.
> 
> This patch and its initial changelog were generated by Gemini during
> an interactive debugging session given dmesg, lspci and similar
> dumps from Gauteng W3S and MODEL-W3S laptops. The resulting quirk
> was reviewed and tested on physical MODEL-W3S hardware and on a W3S
> with slightly different hardware.
> 
> Signed-off-by: Steven 'Steve' Kendall <skend@chromium.org>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261119-gauteng-audio-class-set-v1-1-e81d6fd620ad@chromium.org?part=1


      reply	other threads:[~2026-11-19  0:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-19  0:52 [PATCH] PCI: Override Intel Apollo Lake audio class on Gauteng W3S laptops [8086:5a98] Steven 'Steve' Kendall
2026-11-19  0:57 ` sashiko-bot [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=sashiko-outbox-222271@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=skend@chromium.org \
    /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