diff options
| author | Mark Brown <broonie@kernel.org> | 2026-11-02 18:02:22 +0000 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-11-02 18:02:22 +0000 |
| commit | 7904338c38426d72c5f7cd9402cb9a20232a7af5 (patch) | |
| tree | 773e7c911799dfbf172ec09bdeb6ddf612dd6873 /rust/zerocopy/src/pointer | |
| parent | 8aed8b66751e006589b6a9474af757d1ba04a857 (diff) | |
| parent | a8d72f246edb9323f6e0ae8283676a323b7847eb (diff) | |
regulator: mt6363: Fix register access and VEMC voltage handling
Alexandre Mergnat <amergnat@baylibre.com> says:
Testing the MT6363 regulator driver showed:
- the VEMC (UFS VCC) voltage reported as 1.25 V while the PMIC is
programmed to 2.55 V
- regmap debugfs showing each register merged with the next one
Reading the code with the datasheet showed more problems:
- a VEMC voltage change to the misreported value is skipped while
VEMC is enabled
- disabling VS2 or a VBUCK rail also clears the enable bits of VS1,
VS3 and three VSRAM rails
- the BUCK and TMA key writes also overwrite the two registers after
each key
- with hardware trap 1, VEMC voltage changes are not applied and the
voltage is misreported
Link: https://patch.msgid.link/20261102-rgp-67-mt6363-regulator-fixes-v1-0-420789a3113e@baylibre.com
Diffstat (limited to 'rust/zerocopy/src/pointer')
0 files changed, 0 insertions, 0 deletions