linux-kernel - Re: (subset) [PATCH 0/4] ASoC: tas*: Fix up GPIO usage

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: <172009333244.28053.17496645260509712348.b4-ty@kernel.org>
Date: Thu, 04 Jul 2024 12:42:12 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Shenghao Ding <shenghao-ding@...com>, 
 Kevin Lu <kevin-lu@...com>, Baojun Xu <baojun.xu@...com>, 
 Linus Walleij <linus.walleij@...aro.org>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Shenghao Ding <13916275206@....com>, alsa-devel@...a-project.org
Subject: Re: (subset) [PATCH 0/4] ASoC: tas*: Fix up GPIO usage

On Mon, 01 Jul 2024 09:02:11 +0200, Linus Walleij wrote:
> The TI TAS drivers use some legacy GPIO code and headers,
> this series fixes it up.
> 
> The TAS2781 is a special case since it adds a handful of
> lines of deviating code to reconfigure a GPIO line for
> IRQ mode and then never actually use the IRQ obtained in
> the code. Is the line used by autonomous hardware? I'm
> puzzled by this.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: tas5086: Convert to GPIO descriptors
      commit: 3b628e617b21144579bbca806a26737e8485d93a

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