[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168081666144.315518.8879348580089402745.b4-ty@kernel.org>
Date: Thu, 06 Apr 2023 22:31:01 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Heiko Stuebner <heiko@...ech.de>,
Bjorn Andersson <andersson@...nel.org>,
Joseph Chen <chenjh@...k-chips.com>,
Ezequiel Garcia <ezequiel@...guardiasur.com.ar>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
kernel@...labora.com
Subject: Re: (subset) [PATCH v2 0/8] Add support for Rockchip RK860X
regulators
On Thu, 06 Apr 2023 20:17:58 +0300, Cristian Ciocaltea wrote:
> This patch series introduces support for the Rockchip RK860X regulators,
> while also providing a few fixes and improvements to the existing fan53555
> driver.
>
> RK8600/RK8601 are fully compatible with the FAN53555 regulators.
>
> RK8602/RK8603 are a bit different, having a wider output voltage
> selection range, from 0.5 V to 1.5 V in 6.25 mV steps. They are used
> in the Rock 5B board to power the ARM Cortex-A76 cores and the NPU.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[2/8] regulator: fan53555: Explicitly include bits header
commit: 4fb9a5060f73627303bc531ceaab1b19d0a24aef
[3/8] regulator: fan53555: Fix wrong TCS_SLEW_MASK
commit: c5d5b55b3c1a314137a251efc1001dfd435c6242
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
Powered by blists - more mailing lists