linux-kernel - Re: [PATCH v2 0/2] ASoC: codecs: aw88261: add dvdd-supply 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: <176842660767.229619.9557284936368561049.b4-ty@kernel.org>
Date: Wed, 14 Jan 2026 21:36:47 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Weidong Wang <wangweidong.a@...nic.com>, 
 Bharadwaj Raju <bharadwaj.raju@...hinesoul.in>
Cc: Bhushan Shah <bhushan.shah@...hinesoul.in>, 
 Luca Weiss <luca.weiss@...rphone.com>, 
 ~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org
Subject: Re: [PATCH v2 0/2] ASoC: codecs: aw88261: add dvdd-supply property

On Wed, 14 Jan 2026 16:03:23 +0530, Bharadwaj Raju wrote:
> The AW88261 has a DVDD chip which needs to be powered on for it to
> function correctly. The property for this was missing, so this patchset
> adds the dvdd-supply property which enables a regulator to be bound
> to it in a device tree.
> 
> 

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: document dvdd-supply property for awinic,aw88261
      commit: 18d524de812ff37e7de12a2acddfe7eee6b4ca3c
[2/2] ASoC: codecs: aw88261: use dvdd-supply regulator
      commit: 519d0a6b2ca5a891340b6c24a4c40545f518e1a8

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