Message ID | 20180620203500.28309-1-nick@shmanahar.org (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On Wed, Jun 20, 2018 at 1:35 PM, Nick Dyer <nick@shmanahar.org> wrote: > The pinctrl settings were incorrect for the touchscreen interrupt line, causing > an interrupt storm. This change has been tested with both the atmel_mxt_ts and > RMI4 drivers on the RDU1 units. > > The value 0x4 comes from the value of register IOMUXC_SW_PAD_CTL_PAD_CSI1_D8 > from the old vendor kernel. > > Signed-off-by: Nick Dyer <nick@shmanahar.org> > Fixes: ceef0396f367 ("ARM: dts: imx: add ZII RDU1 board") > Cc: <stable@vger.kernel.org> # 4.15+ > Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com> > --- > Changes in v4: > - Add reviewed by Fabio > Changes in v3: > - Update commit message to add source of 0x4 value, fixes tag and CC stable > Changes in v2: > - Use hex, only alter IRQ line config Tested on an RDU1 with Synaptics touchscreen successfully. No interrupt store any longer... Tested-by: Chris Healy <cphealy@gmail.com>
diff --git a/arch/arm/boot/dts/imx51-zii-rdu1.dts b/arch/arm/boot/dts/imx51-zii-rdu1.dts index df9eca94d812..8a878687197b 100644 --- a/arch/arm/boot/dts/imx51-zii-rdu1.dts +++ b/arch/arm/boot/dts/imx51-zii-rdu1.dts @@ -770,7 +770,7 @@ pinctrl_ts: tsgrp { fsl,pins = < - MX51_PAD_CSI1_D8__GPIO3_12 0x85 + MX51_PAD_CSI1_D8__GPIO3_12 0x04 MX51_PAD_CSI1_D9__GPIO3_13 0x85 >; };