diff options
| author | Simon Glass <sjg@chromium.org> | 2016-10-05 20:42:09 -0600 |
|---|---|---|
| committer | Bin Meng <bmeng.cn@gmail.com> | 2016-10-11 11:55:33 +0800 |
| commit | 26f50fbed2f19edf0c4a2eb80e7fa12941764660 (patch) | |
| tree | 6e7987ed97025caf8beb9e31f7b05c75a86bc8ee /post/board | |
| parent | 88d915b10f44e044dfd874e201a4ce1fcdbff59a (diff) | |
| download | u-boot-imx-26f50fbed2f19edf0c4a2eb80e7fa12941764660.zip u-boot-imx-26f50fbed2f19edf0c4a2eb80e7fa12941764660.tar.gz u-boot-imx-26f50fbed2f19edf0c4a2eb80e7fa12941764660.tar.bz2 | |
Revert "x86: broadwell: gpio: Remove the codes to set up pin control"
This makes the assumption that setting up pinctrl in cpu_init_r() is safe.
On samus we need GPIOs before relocation in order to support power control.
This commit fixes the following message on boot:
initcall sequence ffe5c6f4 failed at call ffe01d3d (err=-1)
### ERROR ### Please RESET the board ###
In any case it seems better to leave init to driver model, so that it can
pick up the GPIO driver when it needs it. Since pinctrl is a dependency of
the GPIO driver, we may as well put the dependency there and avoid these
problems.
This reverts commit 9769e05bcf79939bad23a719982dd1f85a110f3c.
Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'post/board')
0 files changed, 0 insertions, 0 deletions