linux-kernel - Re: [PATCH] regulator: slg51000: Wait after asserting CS pin

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: <166878379620.937643.12916671010075524568.b4-ty@kernel.org>
Date:   Fri, 18 Nov 2022 15:03:16 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Konrad Dybcio <konrad.dybcio@...aro.org>,
        linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>
Cc:     Support Opensource <support.opensource@...semi.com>,
        patches@...aro.org
Subject: Re: [PATCH] regulator: slg51000: Wait after asserting CS pin

On Fri, 18 Nov 2022 14:10:35 +0100, Konrad Dybcio wrote:
> Sony's downstream driver [1], among some other changes, adds a
> seemingly random 10ms usleep_range, which turned out to be necessary
> for the hardware to function properly on at least Sony Xperia 1 IV.
> Without this, I2C transactions with the SLG51000 straight up fail.
> 
> Relax (10-10ms -> 10-11ms) and add the aforementioned sleep to make
> sure the hardware has some time to wake up.
> 
> [...]

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: slg51000: Wait after asserting CS pin
      commit: 0b24dfa587c6cc7484cfb170da5c7dd73451f670

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