The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Callum Wong <mail@callumwong.com>
Cc: tiwai@suse.com, perex@perex.cz, linux-sound@vger.kernel.org,
	sbinding@opensource.cirrus.com, patches@opensource.cirrus.com,
	rf@opensource.cirrus.com, david.rhodes@cirrus.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ALSA: hda: fix HP OmniBook 7 Laptop 14-fr0xxx speaker volume and mute LEDs
Date: Thu, 09 Jul 2026 11:31:05 +0200	[thread overview]
Message-ID: <87zf0033xi.wl-tiwai@suse.de> (raw)
In-Reply-To: <0108019f32ad9dfb-ac2d3ace-aed9-401b-97d5-9d43f5b7e2db-000000@ap-southeast-2.amazonses.com>

On Sun, 05 Jul 2026 16:27:46 +0200,
Callum Wong wrote:
> 
> The HP OmniBook 7 Laptop 14-fr0xxx (SSID 103c:8e3b) has a Realtek ALC245
> codec and two CS35L41 amplifiers. The speakers work, but the CS35L41
> amplifiers are not configured, so they play at a lower volume. The F6
> speaker-mute and F9 mic-mute keyboard LEDs also don't work.
> 
> Patch 1 supplies the CS35L41 _DSD configuration so the amplifiers probe
> and drive the speakers at full volume. Patch 2 switches the existing
> 8e3b quirk to a fixup that additionally enables the two mute LEDs.
> 
> Both patches were tested on the laptop.
> 
> Callum Wong (2):
>   ALSA: hda: cs35l41: Support HP OmniBook 7 Laptop 14-fr0xxx
>   ALSA: hda/realtek: Enable mute LEDs on HP OmniBook 7 Laptop 14-fr0xxx

Although the code changes look OK, I'd like to hear the confirmation
from Cirrus people before merging.


thanks,

Takashi

      reply	other threads:[~2026-07-09  9:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-05 14:27 [PATCH 0/2] ALSA: hda: fix HP OmniBook 7 Laptop 14-fr0xxx speaker volume and mute LEDs Callum Wong
2026-07-09  9:31 ` 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=87zf0033xi.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=david.rhodes@cirrus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mail@callumwong.com \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=sbinding@opensource.cirrus.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