linux-kernel - Re: [PATCH v3 0/2] Add support for Richtek RT6190 36V 4-wwtich 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: <166740635395.287466.16386075560173939069.b4-ty@kernel.org>
Date:   Wed, 02 Nov 2022 16:25:53 +0000
From:   Mark Brown <broonie@...nel.org>
To:     cy_huang <u0084500@...il.com>, krzysztof.kozlowski+dt@...aro.org,
        robh+dt@...nel.org
Cc:     linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        cy_huang@...htek.com, lgirdwood@...il.com
Subject: Re: [PATCH v3 0/2] Add support for Richtek RT6190 36V 4-wwtich regulator

On Mon, 31 Oct 2022 10:28:52 +0800, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@...htek.com>
> 
> The RT6190 is a 4-switch Buck-Boost controller designed for USB power delivery
> (USB PD). It operates with wide input voltage range from 4.5V to 36V, and the
> output voltage can be programmable between 3V and 36V. It implements peak
> current mode control mechanism to deliver up to 100W power with the
> programmable constant voltage and constant current output. It also has built-in
> charge pumps for driving external low-cost N-MOSFETs to control the power path.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: Add bindings for Richtek RT6190 regulator
      commit: 8facce4349d46fbc2ac4f6da3786130ddd104440
[2/2] regulator: rt6190: Add support for Richtek RT6190 regulator
      commit: e6999e7cca7eecd64c27dc72c51d11cb33079a0c

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