linux-kernel - Re: [PATCH] ASoC: cs35l56: Workaround for ACPI with broken spk-id-gpios property

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <170786662332.1076782.7482522938030150798.b4-ty@kernel.org>
Date: Tue, 13 Feb 2024 23:23:43 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Workaround for ACPI with broken
 spk-id-gpios property

On Fri, 09 Feb 2024 11:18:40 +0000, Richard Fitzgerald wrote:
> The ACPI in some SoundWire laptops has a spk-id-gpios property but
> it points to the wrong Device node. This patch adds a workaround to
> try to get the GPIO directly from the correct Device node.
> 
> If the attempt to get the GPIOs from the property fails, the workaround
> looks for the SDCA node "AF01", which is where the GpioIo resource is
> defined. If this exists, a spk-id-gpios mapping is added to that node
> and then the GPIO is got from that node using the property.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: cs35l56: Workaround for ACPI with broken spk-id-gpios property
      commit: 0db0c1770834f39e11a2902e20e1f11a482f4465

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark