Re: [PATCH v3 0/3] pinctrl: msm interrupt and muxing fixes

2018-10-01 Thread Niklas Cassel
On Mon, Oct 01, 2018 at 11:46:57AM -0700, Stephen Boyd wrote: > Quoting Niklas Cassel (2018-09-12 03:34:31) > > Hello Stephen, > > > > I'm getting this warning on dragonboard 820c (msm8996) when booting > > linux-next: > > > > [3.211575] WARNING: CPU: 1 PID: 1 at > > drivers/pinctrl/qcom/pi

Re: [PATCH v3 0/3] pinctrl: msm interrupt and muxing fixes

2018-10-01 Thread Stephen Boyd
Quoting Niklas Cassel (2018-09-12 03:34:31) > Hello Stephen, > > I'm getting this warning on dragonboard 820c (msm8996) when booting > linux-next: > > [3.211575] WARNING: CPU: 1 PID: 1 at > drivers/pinctrl/qcom/pinctrl-msm.c:164 msm_pinmux_set_mux+0xc8/0x150 > [3.212127] l28: ramp_delay

Re: [PATCH v3 0/3] pinctrl: msm interrupt and muxing fixes

2018-09-12 Thread Niklas Cassel
Hello Stephen, I'm getting this warning on dragonboard 820c (msm8996) when booting linux-next: [3.211575] WARNING: CPU: 1 PID: 1 at drivers/pinctrl/qcom/pinctrl-msm.c:164 msm_pinmux_set_mux+0xc8/0x150 [3.212127] l28: ramp_delay not set [3.215146] Modules linked in: [3.215168] CPU

[PATCH v3 0/3] pinctrl: msm interrupt and muxing fixes

2018-08-16 Thread Stephen Boyd
Here's a collection of pinctrl fixes for the qcom driver that make things a little smoother for DT writers while also fixing a problem seen with level triggered interrupts. The first patch fixes an issue where we always see one extra level triggered interrupt when the interrupt triggers. The secon