summaryrefslogtreecommitdiff
path: root/doc/README.nand-boot-ppc440
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2016-03-11 22:07:13 -0700
committerBin Meng <bmeng.cn@gmail.com>2016-03-17 10:27:25 +0800
commit7ac99be6e2087dc9c1f6be780ec10cc0ad8ad71b (patch)
tree8cee7466208468530d63eb1890c0bcf343a2ac28 /doc/README.nand-boot-ppc440
parent0a10f440e3ba8b37b986c5eb7f7c1ac191c6a56d (diff)
downloadu-boot-imx-7ac99be6e2087dc9c1f6be780ec10cc0ad8ad71b.zip
u-boot-imx-7ac99be6e2087dc9c1f6be780ec10cc0ad8ad71b.tar.gz
u-boot-imx-7ac99be6e2087dc9c1f6be780ec10cc0ad8ad71b.tar.bz2
x86: Add an ICH6 pin configuration driver
Add a driver which sets up the pin configuration on x86 devices with an ICH6 (or later) Platform Controller Hub. The driver is not in the pinctrl uclass due to some oddities of the way x86 devices work: - The GPIO controller is not present in I/O space until it is set up - This is done by writing a register in the PCH - The PCH has a driver which itself uses PCI, another driver - The pinctrl uclass requires that a pinctrl device be available before any other device can be probed It would be possible to work around the limitations by: - Hard-coding the GPIO address rather than reading it from the PCH - Using special x86 PCI access to set the GPIO address in the PCH However it is not clear that this is better, since the pin configuration driver does not actually provide normal pin configuration services - it simply sets up all the pins statically when probed. While this remains the case, it seems better to use a syscon uclass instead. This can be probed whenever it is needed, without any limitations. Also add an 'invert' property to support inverting the input. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'doc/README.nand-boot-ppc440')
0 files changed, 0 insertions, 0 deletions