[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166966235607.739089.9217119235765482431.b4-ty@kernel.org>
Date: Mon, 28 Nov 2022 19:05:56 +0000
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>,
Lee Jones <lee@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Sebastian Reichel <sebastian.reichel@...labora.com>
Cc: linux-kernel@...r.kernel.org, kernel@...labora.com,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Stephen Boyd <sboyd@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Linus Walleij <linus.walleij@...aro.org>,
devicetree@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
Alessandro Zummo <a.zummo@...ertech.it>,
linux-rockchip@...ts.infradead.org
Subject: Re: (subset) [PATCHv3 00/14] Introduce RK806 Support
On Fri, 9 Sep 2022 19:55:08 +0200, Sebastian Reichel wrote:
> The Rockchip RK3588 Evaluation Boards use SPI connected RK806
> PMICs. Downstream this is handled by a new driver, but apart
> from being SPI connected this chip is quite similar to the
> ther Rockchip PMICs (also RK806 is promoted to also support
> I2C). Thus this series instead updates RK808.
>
> Changelog since PATCHv2:
> * https://lore.kernel.org/all/20220908003107.220143-1-sebastian.reichel@collabora.com/
> * Change DT binding to not allow nldo-reg6
> * Fix DT binding to check for [np]ldo-reg instead of [np]ldo_reg
> * remove rk806_get_voltage_sel_regmap in favour of regulator_get_voltage_sel_regmap
> * drop rk806_set_voltage in favour of regulator_set_voltage_sel_regmap
> * use regulator_set_ramp_delay_regmap
> * drop possibly incorrect printing of chip id register address in case of errors
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[11/14] regulator: rk808: Use dev_err_probe
commit: f39f8709c217d82aabbf51d8669731137ce09aea
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