diff options
| author | Furquan Shaikh <furquan@chromium.org> | 2017-10-06 17:05:50 -0700 |
|---|---|---|
| committer | Furquan Shaikh <furquan@google.com> | 2017-10-09 20:20:40 +0000 |
| commit | 219ebb969bb52eb88d49d6ce31dbfc0d7cabfc49 (patch) | |
| tree | 5597f190251338d86df7ee8706faa765d9ee4d5c /util/dtd_parser | |
| parent | e9d8959c4f11399c7ec1609ecff204c8f3c9b3ea (diff) | |
| download | coreboot-219ebb969bb52eb88d49d6ce31dbfc0d7cabfc49.tar.xz | |
skylake mainboards: Use PAD_CFG_GPI_GPIO_DRIVER instead of PAD_CFG_GPI
Change 1760cd3e (soc/intel/skylake: Use common/block/gpio) updated all
skylake boards to use common gpio driver. Common gpio code
defines PAD_CFG_GPI without GPIO_DRIVER ownership. However, for
skylake PAD_CFG_GPI set GPIO_DRIVER ownership by default. This
resulted in Linux kernel failing to configure all GPIO IRQs since the
ownership was not set correctly. (Observed error in dmesg: "genirq:
Setting trigger mode 3 for irq 201
failed (intel_gpio_irq_type+0x0/0x110)")
This change fixes the above issue by replacing all uses of PAD_CFG_GPI
in skylake mainboards to PAD_CFG_GPI_GPIO_DRIVER.
BUG=b:67507004
TEST=Verified on soraka that the genirq error is no longer observed in
dmesg. Also, cat /proc/interrupts has the interrupts configured
correctly.
Change-Id: I7dab302f372e56864432100a56462b92d43060ee
Signed-off-by: Furquan Shaikh <furquan@chromium.org>
Reviewed-on: https://review.coreboot.org/21912
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'util/dtd_parser')
0 files changed, 0 insertions, 0 deletions