arm64: dts: qcom: sc7280: Add 3ms ramp to herobrine's pp3300_left_in_mlb
authorDouglas Anderson <dianders@chromium.org>
Tue, 7 Feb 2023 02:48:11 +0000 (18:48 -0800)
committerBjorn Andersson <andersson@kernel.org>
Thu, 9 Feb 2023 04:09:36 +0000 (20:09 -0800)
commit4261cea17a2f5e0ec78eb3ceebb68dddb918aee9
treef23e3d5d3f0c1e5feac5853945f4705d1c4116ac
parent428df177013bad1a0a062878e3d5224122b7a5fe
arm64: dts: qcom: sc7280: Add 3ms ramp to herobrine's pp3300_left_in_mlb

The "pp3300_left_in_mlb" rail on herobrine eventually connects up to
"vreg_edp_3p3" on the qcard. On several herobrine designs this rail
has been measured to need more than 1ms to turn on.

While technically a herobrine derivative (defined as anyone including
the "herobrine.dtsi") could change the board to make the rail rise
faster or slower, the fact that two boards (evoker and villager) both
measured it as taking more than 1ms implies that it's probably going
to be the norm. Thus, let's add a "regulator-enable-ramp-delay"
straight into the herobrine.dtsi to handle this. If a particular
derivative board needs a faster or slower one then they can override
it, though that feels unlikely.

While we measured something a bit over 1ms, we'll choose 3ms to give
us a tiny bit of margin. This isn't a rail that turns off and on all
the time anyway and 3ms is nothing compared to the total amount of
time to power on a panel.

Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Link: https://lore.kernel.org/r/20230206184744.2.I13814cefc5ab3e0a39ebd09f052e3fd25d4e8f1d@changeid
arch/arm64/boot/dts/qcom/sc7280-herobrine.dtsi