On Tue, Mar 14, 2017 at 9:56 PM, Robert Middleton <robert.middleton@xxxxxxxxxx> wrote: > On Tue, Mar 14, 2017 at 5:16 PM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: >> On Tue, Mar 14, 2017 at 6:41 PM, Robert Middleton >> <robert.middleton@xxxxxxxxxx> wrote: >>> On Tue, Mar 14, 2017 at 9:19 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: >>>> On Wed, Feb 22, 2017 at 4:34 PM, <robert.middleton@xxxxxxxxxx> wrote: >>>> >>>>> From: Robert Middleton <robert.middleton@xxxxxxxxxx> >>>>> >>>>> When an interrupt occurs on an MCP23S08 chip, the INTF register will only >>>>> contain one bit as causing the interrupt. If more than two pins change at >>>>> the same time on the chip, this causes one of the pins to not be reported. >>>>> This patch fixes the logic for checking if a pin has changed, so that >>>>> multiple pins will always cause more than one change. >>>>> >>>>> Signed-off-by: Robert Middleton <robert.middleton@xxxxxxxxxx> >>>> >>>> OMG that looks complicated. But good commit with proper comments, >>>> so patch applied for fixes. I had to do some fuzzing patch -p1 < foo.patch >>>> so please check the result. >>>> >>>> Yours, >>>> Linus Walleij >>> >>> Linux, >>> >>> Thanks, I will check it out once that gets pushed(I'm assuming it will >>> be in the linux-gpio repository at >>> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git/) >> >> Unfortunately it explodes in the build servers due to changes in >> the driver. >> >> Can you rebase and test on v4.11-rc1 and resend? >> >> Yours, >> Linus Walleij > > Sure, that will take me a day or two but I can get that done. > > -Robert Middleton Patch v3 has been sent. Looking at the v2 patch, the biggest problem was that I had somehow forgot a ), which was causing a parse error in gcc. I'm not quite sure how that happened. I tested with Torvalds' 4.11-rc1 kernel, everything still worked properly. -Robert Middleton -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html