linux-kernel - Re: (subset) [PATCH v4 0/7] Really implement Qualcomm LAB/IBB regulators

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <161118766212.46058.17597385912492952608.b4-ty@kernel.org>
Date:   Thu, 21 Jan 2021 00:07:42 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-arm-msm@...r.kernel.org,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...ainline.org>
Cc:     bjorn.andersson@...aro.org, agross@...nel.org,
        phone-devel@...r.kernel.org, sumit.semwal@...aro.org,
        linux-kernel@...r.kernel.org, martin.botka@...ainline.org,
        devicetree@...r.kernel.org, konrad.dybcio@...ainline.org,
        robh+dt@...nel.org, marijn.suijten@...ainline.org,
        lgirdwood@...il.com
Subject: Re: (subset) [PATCH v4 0/7] Really implement Qualcomm LAB/IBB regulators

On Tue, 19 Jan 2021 18:44:14 +0100, AngeloGioacchino Del Regno wrote:
> Okay, the title may be a little "aggressive"? However, the qcom-labibb
> driver wasn't really .. doing much.
> The current form of this driver is only taking care of enabling or
> disabling the regulators, which is pretty useless if they were not
> pre-set from the bootloader, which sets them only if continuous
> splash is enabled.
> Moreover, some bootloaders are setting a higher voltage and/or a higher
> current limit compared to what's actually required by the attached
> hardware (which is, in 99.9% of the cases, a display) and this produces
> a higher power consumption, higher heat output and a risk of actually
> burning the display if kept up for a very long time: for example, this
> is true on at least some Sony Xperia MSM8998 (Yoshino platform) and
> especially on some Sony Xperia SDM845 (Tama platform) smartphones.
> 
> [...]

Applied to

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

Thanks!

[1/7] regulator: qcom-labibb: Switch voltage ops from linear_range to linear
      commit: 9a12eb704ea27826ece4414cb8822388ec54883c
[2/7] regulator: qcom-labibb: Implement current limiting
      commit: 8056704ba948c1c54c7a67d78a8399a749f2d04b
[3/7] regulator: qcom-labibb: Implement pull-down, softstart, active discharge
      commit: 3bc7cb99fb6eafae5a40bf71ded444df70a425f7
[4/7] dt-bindings: regulator: qcom-labibb: Document soft start properties
      commit: 5581304004659ddc8d0d45561c1f2abfe080b4d4
[5/7] regulator: qcom-labibb: Implement short-circuit and over-current IRQs
      commit: 390af53e04114f790d60b63802a4de9d815ade03
[6/7] dt-bindings: regulator: qcom-labibb: Document SCP/OCP interrupts
      commit: 9499200484669fe33c20c735a3d5a29a0dc0e9d4

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