[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173861266637.674751.16665389874730608623.b4-ty@kernel.org>
Date: Mon, 03 Feb 2025 19:57:46 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-arm-kernel@...ts.infradead.org, Marek Vasut <marex@...x.de>,
Conor Dooley <conor@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
devicetree@...r.kernel.org, Frieder Schrempf <frieder.schrempf@...tron.de>,
imx@...ts.linux.dev, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org,
Rob Herring <robh@...nel.org>, Robin Gong <yibin.gong@....com>,
Sascha Hauer <s.hauer@...gutronix.de>, Shawn Guo <shawnguo@...nel.org>,
Frieder Schrempf <frieder@...s.de>
Cc: Bo Liu <liubo03@...pur.com>, Conor Dooley <conor.dooley@...rochip.com>,
Fabio Estevam <festevam@...il.com>, Frank Li <Frank.Li@....com>,
Joy Zou <joy.zou@....com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Pengutronix Kernel Team <kernel@...gutronix.de>
Subject: Re: (subset) [PATCH v3 0/9] Use correct LDO5 control registers for
PCA9450
On Wed, 18 Dec 2024 16:27:23 +0100, Frieder Schrempf wrote:
> This is a follow-up of [1].
>
> The main objective of this is to fix the PCA9450 driver to
> use the correct control register for the LDO5 regulator.
>
> Currently the control register to use for LDO5 is hardcoded to
> LDO5CTRL_H. This is wrong for two reasons:
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/9] dt-bindings: regulator: pca9450: Add properties for handling LDO5
commit: f9cbf56b0a1966d977df87d15a5bdbff2c342062
[2/9] arm64: dts: imx8mp-skov-reva: Use hardware signal for SD card VSELECT
commit: b5ec74c2aec76fbdff9bc16951455602e11902bf
[3/9] Revert "regulator: pca9450: Add SD_VSEL GPIO for LDO5"
commit: c73be62caabbec6629689c705aea65e5ce364d5d
[4/9] regulator: pca9450: Fix control register for LDO5
commit: 3ce6f4f943ddd9edc03e450a2a0d89cb025b165b
[5/9] regulator: pca9450: Fix enable register for LDO5
commit: f5aab0438ef17f01c5ecd25e61ae6a03f82a4586
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