summaryrefslogtreecommitdiff
path: root/arch/x86/dts/baytrail_som-db5800-som-6867.dts
diff options
context:
space:
mode:
authorGeorge McCollister <george.mccollister@gmail.com>2016-07-28 09:49:37 -0500
committerBin Meng <bmeng.cn@gmail.com>2016-08-16 11:44:09 +0800
commit144fdbdeb1f5cbf3ee99300f7d903da373b0a90d (patch)
tree5258014bfc0cd4d06f86722dfa9fd0cc522e2f56 /arch/x86/dts/baytrail_som-db5800-som-6867.dts
parent4cf9e464f78e58117b9a57e1e4e092e609d96b59 (diff)
downloadu-boot-imx-144fdbdeb1f5cbf3ee99300f7d903da373b0a90d.zip
u-boot-imx-144fdbdeb1f5cbf3ee99300f7d903da373b0a90d.tar.gz
u-boot-imx-144fdbdeb1f5cbf3ee99300f7d903da373b0a90d.tar.bz2
x86: som-db5800-som-6867: fix SERIRQ on reset
Explicitly enable ILB_SERIRQ function 1 in cfio_regs_pad_ilb_serirq_PCONF0. Pad configuration for SERIRQ is not set to enable the SERIRQ function after a reset though strangely, it is on initial boot. Rebooting from Linux, reset command in u-boot and even pushing the reset button on the development board all lead to the SERIRQ function being disabled (address 0xfed0c560 with value of 0x2003cc80). Signed-off-by: George McCollister <george.mccollister@gmail.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'arch/x86/dts/baytrail_som-db5800-som-6867.dts')
-rw-r--r--arch/x86/dts/baytrail_som-db5800-som-6867.dts6
1 files changed, 6 insertions, 0 deletions
diff --git a/arch/x86/dts/baytrail_som-db5800-som-6867.dts b/arch/x86/dts/baytrail_som-db5800-som-6867.dts
index 64e2e52..e1d81a7 100644
--- a/arch/x86/dts/baytrail_som-db5800-som-6867.dts
+++ b/arch/x86/dts/baytrail_som-db5800-som-6867.dts
@@ -63,6 +63,12 @@
pad-offset = <0x270>;
mode-func = <2>;
};
+
+ /* SERIRQ */
+ soc_gpio_s0_50@0 {
+ pad-offset = <0x560>;
+ mode-func = <1>;
+ };
};
chosen {