On Tue, Mar 20, 2012 at 11:38 PM, Nick Dyer <nick.dyer@xxxxxxxxxxx> wrote: > Daniel Kurtz wrote: >> This function attempts to make the CHG pin high by reading a bunch of >> messages until the device is happy. Instead of just blindly trying to >> read a fixed number of messages, let's actually read and process them. >> >> It turns out that the messages after boot or nvupdates are T6 reports, >> containing a status, and the config memory checksum. So, let's parse >> them and dump a useful info message. >> >> Signed-off-by: Daniel Kurtz <djkurtz@xxxxxxxxxxxx> > > mxt_make_highchg exists due to the interrupts being edge triggered. It > forces the CHG line to go high. > > With this implementation, I suspect that if a new message arrives after you > have read T44 and before you finish processing messages, then the interrupt > handler will not ever be run. What testing have you done on this? Actually, for the MXT224E on which I've been testing, the CHG line goes high after reading the first byte of the T5 message (in other words, the first byte of the first message, no matter how many messages T44 reports). Expect an updated version of this patchset soon. Thanks for all of your reviews! > > The printout of T6 messages looks OK, though. I'd prefer to see a lookup > table for the report IDs. > > -- > Nick Dyer > Software Engineer, ITDev Ltd > Hardware and Software Development Consultancy > Website: http://www.itdev.co.uk -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
