All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jon Harrison <jonerickharrison@gmail.com>
Cc: skbotnl@disroot.org, david.rhodes@cirrus.com,
	linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
	patches@opensource.cirrus.com, perex@perex.cz,
	rf@opensource.cirrus.com, tiwai@suse.com
Subject: Re: [PATCH v2] ALSA: hda: cs35l41: Support HP OmniBook 7 Laptop 16-bh0xxx
Date: Fri, 16 Oct 2026 16:16:16 +0200	[thread overview]
Message-ID: <87a4od3f4f.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAEG=48+jRv7wHgd-yPTHEf9YFO++XusKQgT+WJz60hgCE8pGww@mail.gmail.com>

On Fri, 16 Oct 2026 00:15:24 +0200,
Jon Harrison wrote:
> 
> On Mon, 24 Aug 2026, Stefan Binding wrote:
> > We are currently awaiting confirmation of the correct settings before we do
> > so.
> 
> I have another HP OmniBook 7 Laptop 16-bh0xxx, SKU D2KR6UA#ABA,
> BIOS F.12, subsystem 103c:8e60, running Linux 7.2.5. Both CS35L41
> amplifiers still fail to probe:
> 
>   cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Failed property
> cirrus,dev-index: -22
>   cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: error -EINVAL: Platform
> not supported
> 
> The speakers only play through the Realtek fallback and are very quiet.
> Has that settings confirmation arrived, and is there an expected time
> for the quirk?

OK, we've waited enough long, so I take the patch to for-next branch
now (for 7.4-rc1).

If this is really breaking something, let me know.  We'll fix up again
before 7.4 release.


thanks,

Takashi

  reply	other threads:[~2026-10-16 14:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 22:15 [PATCH v2] ALSA: hda: cs35l41: Support HP OmniBook 7 Laptop 16-bh0xxx Jon Harrison
2026-10-16 14:16 ` Takashi Iwai [this message]
2026-10-16 14:42   ` Sven
2026-10-16 14:46     ` Sven Jans
2026-10-16 14:53       ` Sven Jans
  -- strict thread matches above, loose matches on Subject: below --
2026-07-09 21:43 Sven Jans
2026-07-15 14:34 ` Takashi Iwai
2026-07-15 14:54   ` Sven Jans
2026-07-15 16:13   ` Stefan Binding (Opensource)
2026-07-23 10:42 ` Sven

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=87a4od3f4f.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=david.rhodes@cirrus.com \
    --cc=jonerickharrison@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=skbotnl@disroot.org \
    --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 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.