On Wed, Jun 17, 2015 at 1:59 AM, Daniel Mack <daniel@xxxxxxxxxx> wrote: > On 06/17/2015 08:49 AM, Matt Ranostay wrote: >> Actually after further reading of the datasheet and testing with >> i2ctools it seems cap11xx_input_close() isn't putting the device in >> DEEP SLEEP mode. >> >> Any thoughts why? > > No, sorry. IIRC, the board I wrote the driver for didn't give me the > ability to measure power consumption. > I can confirm it never goes to deep sleep or cap11xx_input_close() gets called. Does evdev kernel module increment/input_open_device even if nothing in userspace is accessing the /dev/event/inputX nodes? - Matt > > Daniel > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
