linux-kernel - Re: [RESEND PATCH v3] regulator: pca9450: Handle hardware with fixed SD

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: <174109163933.26710.17795041039558652228.b4-ty@kernel.org>
Date: Tue, 04 Mar 2025 12:33:59 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-arm-kernel@...ts.infradead.org, 
 Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org, 
 Frieder Schrempf <frieder@...s.de>
Cc: Frieder Schrempf <frieder.schrempf@...tron.de>, 
 Bo Liu <liubo03@...pur.com>, Frank Li <Frank.Li@....com>, 
 Joy Zou <joy.zou@....com>, Robin Gong <yibin.gong@....com>
Subject: Re: [RESEND PATCH v3] regulator: pca9450: Handle hardware with
 fixed SD_VSEL for LDO5

On Mon, 03 Mar 2025 14:22:54 +0100, Frieder Schrempf wrote:
> There are two ways to set the output voltage of the LD05
> regulator. First by writing to the voltage selection registers
> and second by toggling the SD_VSEL signal.
> 
> Usually board designers connect SD_VSEL to the VSELECT signal
> controlled by the USDHC controller, but in some cases the
> signal is hardwired to a fixed low level (therefore selecting
> 3.3V as initial value for allowing to boot from the SD card).
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: pca9450: Handle hardware with fixed SD_VSEL for LDO5
      commit: c8c1ab2c5cb797fe455aa18b4ab7bf39897627f6

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