linux-kernel - Re: [PATCH] ASoC: tas5086: use sleeping variants of gpiod API

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: <172416356610.261879.3153828567035739715.b4-ty@kernel.org>
Date: Tue, 20 Aug 2024 15:19:26 +0100
From: Mark Brown <broonie@...nel.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Linus Walleij <linus.walleij@...aro.org>, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: tas5086: use sleeping variants of gpiod API

On Mon, 19 Aug 2024 18:13:47 -0700, Dmitry Torokhov wrote:
> The driver does not access reset GPIO in atomic contexts so it is usable
> with GPIOs that may sleep during access. Switch to using
> gpiod_set_value_cansleep().
> 
> Also the reset GPIO is configured as output at the time it is acquired,
> there is no need to use gpiod_direction_output() when executing reset
> sequence.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tas5086: use sleeping variants of gpiod API
      commit: 5f83ee4b1f0c04a8b4125daab8918606df3dc035

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