diff options
| author | Emil Renner Berthing <kernel@esmil.dk> | 2021-07-17 22:50:38 +0300 |
|---|---|---|
| committer | Emil Renner Berthing <emil.renner.berthing@canonical.com> | 2025-07-05 00:03:28 +0300 |
| commit | 23990badde97cc5e5ff50ec577680db3da698b56 (patch) | |
| tree | 6b579d851c6e681f38da53d31b5808d9a7e67674 /scripts/lib/kdoc/kdoc_output.py | |
| parent | 090ea58a5353e4899ace71238e6d1abdd68e22fd (diff) | |
| download | linux-23990badde97cc5e5ff50ec577680db3da698b56.tar.xz | |
pinctrl: starfive: Reset pinmux settings
Current u-boot doesn't seem to take into account that some GPIOs are
configured as inputs/outputs of certain peripherals on power-up. This
means it ends up configuring some GPIOs as inputs to more than one
peripheral which the documentation explicitly says is illegal. Similarly
it also ends up configuring more than one GPIO as output of the same
peripheral. While not explicitly mentioned by the documentation this
also seems like a bad idea.
The easiest way to remedy this mess is to just disconnect all GPIOs from
peripherals and have our pinmux configuration set everything up
properly. This, however, means that we'd disconnect the serial console
from its pins for a while, so add a device tree property to keep
certain GPIOs from being reset.
Signed-off-by: Emil Renner Berthing <kernel@esmil.dk>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_output.py')
0 files changed, 0 insertions, 0 deletions