aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/trace
diff options
context:
space:
mode:
authorAlexandru Gagniuc <mr.nuke.me@gmail.com>2020-10-20 17:14:58 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-01-19 18:27:19 +0100
commit47319c4b81a3f2e2832f8f0eaf8f2c737dddd972 (patch)
treed6880d2f95df34f332c0c113a1c2bdf5c0c44631 /kernel/trace
parentaf402f64ca08400eb7ca2d7d5799636eb2c9f30e (diff)
downloadkernel_replicant_linux-47319c4b81a3f2e2832f8f0eaf8f2c737dddd972.tar.gz
kernel_replicant_linux-47319c4b81a3f2e2832f8f0eaf8f2c737dddd972.tar.bz2
kernel_replicant_linux-47319c4b81a3f2e2832f8f0eaf8f2c737dddd972.zip
drm/bridge: sii902x: Enable I/O and core VCC supplies if present
commit cc5f7e2fcbe396f2f461cd67c872af771a334bca upstream. On the SII9022, the IOVCC and CVCC12 supplies must reach the correct voltage before the reset sequence is initiated. On most boards, this assumption is true at boot-up, so initialization succeeds. However, when we try to initialize the chip with incorrect supply voltages, it will not respond to I2C requests. sii902x_probe() fails with -ENXIO. To resolve this, look for the "iovcc" and "cvcc12" regulators, and make sure they are enabled before starting the reset sequence. If these supplies are not available in devicetree, then they will default to dummy-regulator. In that case everything will work like before. This was observed on a STM32MP157C-DK2 booting in u-boot falcon mode. On this board, the supplies would be set by the second stage bootloader, which does not run in falcon mode. Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com> Signed-off-by: Sam Ravnborg <sam@ravnborg.org> [Fix checkpatch warnings] Link: https://patchwork.freedesktop.org/patch/msgid/20201020221501.260025-2-mr.nuke.me@gmail.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/trace')
0 files changed, 0 insertions, 0 deletions