Furquan Shaikh 219ebb969b 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>		2017-10-09 20:20:40 +00:00
..
acpi
spd
acpi_tables.c
board_info.txt
bootblock_mainboard.c
chromeos.c
chromeos.fmd
cmos.layout	mb/*/*: Remove rtc nvram configurable baud rate	2017-09-23 11:06:25 +00:00
devicetree.cb
dsdt.asl
ec.c	ec/google/chromeec: Add library function google_chromeec_events_init	2017-10-08 19:38:28 +00:00
ec.h
gpio.h	skylake mainboards: Use PAD_CFG_GPI_GPIO_DRIVER instead of PAD_CFG_GPI	2017-10-09 20:20:40 +00:00
Kconfig	mb/google/*: Use newly added Chrome EC boardid function	2017-09-26 15:20:39 +00:00
Kconfig.name
mainboard.c
Makefile.inc	mb/google/*: Use newly added Chrome EC boardid function	2017-09-26 15:20:39 +00:00
pei_data.c
ramstage.c
romstage.c
smihandler.c