Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Simon Trimmer <simont@opensource.cirrus.com>
Cc: <tiwai@suse.com>, <linux-sound@vger.kernel.org>,
	<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
	<patches@opensource.cirrus.com>
Subject: Re: [PATCH] ALSA: hda/realtek: Autodetect Cirrus Logic companion amplifier bindings
Date: Thu, 29 Aug 2024 18:23:36 +0200	[thread overview]
Message-ID: <87wmjzl2lz.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240829161114.140938-1-simont@opensource.cirrus.com>

On Thu, 29 Aug 2024 18:11:14 +0200,
Simon Trimmer wrote:
> 
> We do not need model specific HDA quirks to construct the component
> binding details of Cirrus Logic companion amplifiers as this information
> is already present in the ACPI.
> 
> Quirks are then only required for special workarounds not described in
> the ACPI such as internal configuration of the Realtek codecs.
> 
> The codec pointer is now initialized in hda_component_manager_init() so
> that we can detect when companion amplifiers are found in the ACPI but
> the SSID invokes a quirk that also attempts to create the component
> binding.
> 
> Signed-off-by: Simon Trimmer <simont@opensource.cirrus.com>
> ---
> v1 - This patch applies to for-next with this additional patch:
>      b1faff28a2bd ("ALSA: hda: hda_component: Fix mutex crash if nothing ever binds")
>      which is currently only in the for-linus.

OK, I now merged for-linus to for-next, and applied yours.

>      We're looking to do the same for the CS35L41 devices, but that will
>      come later because there are many more quirks to work through.

That's understandable.  Thanks!


Takashi

      reply	other threads:[~2024-08-29 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 16:11 [PATCH] ALSA: hda/realtek: Autodetect Cirrus Logic companion amplifier bindings Simon Trimmer
2024-08-29 16:23 ` 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=87wmjzl2lz.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=simont@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