linux-kernel - Re: [PATCH v5 0/2] Add support for ADP5055 triple buck regulator.

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: <174422992361.1502590.6910464577711922993.b4-ty@kernel.org>
Date: Wed, 09 Apr 2025 21:18:43 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, 
 Alexis Czezar Torreno <alexisczezar.torreno@...log.com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, 
 Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v5 0/2] Add support for ADP5055 triple buck regulator.

On Tue, 08 Apr 2025 12:25:47 +0800, Alexis Czezar Torreno wrote:
> Introduce a regulator driver support for ADP5055. The device combines 3
> high performance buck regulators in a 43-termminal land grid array
> package. The device enables direct connection to high input voltages up
> to 18V with no preregulator. Channel 1 and 2 deliver a programmable
> output current of 3.5A or 7.5A or provide a single output with up to 14A
> in parallel operation. Channel 3 has a programmable output current of
> 1.5A or 3A.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: adi,adp5055-regulator: Add adp5055 support
      commit: 5bfc88c4e5783357399ce66f40a479a090af2ba0
[2/2] regulator: adp5055: Add driver for adp5055
      commit: 147b2a96f24e0cfcc476378f9356b30662045c7e

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