From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Ranostay Subject: Re: [PATCH v4 2/2] cap11xx: add LED support Date: Wed, 17 Jun 2015 16:36:48 -0700 Message-ID: References: <1434422770-26896-1-git-send-email-mranostay@gmail.com> <1434422770-26896-3-git-send-email-mranostay@gmail.com> <557FD625.1080806@samsung.com> <55809476.90407@zonque.org> <558136FE.7060308@zonque.org> <20150617223852.GA11341@dtor-ws> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20150617223852.GA11341@dtor-ws> Sender: linux-input-owner@vger.kernel.org To: Dmitry Torokhov Cc: Daniel Mack , Jacek Anaszewski , "linux-input@vger.kernel.org" , linux-leds@vger.kernel.org, "devicetree@vger.kernel.org" List-Id: devicetree@vger.kernel.org On Wed, Jun 17, 2015 at 3:38 PM, Dmitry Torokhov wrote: > On Wed, Jun 17, 2015 at 02:53:26PM -0700, Matt Ranostay wrote: >> On Wed, Jun 17, 2015 at 1:59 AM, Daniel Mack 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? > > No it does not. On the other hand there is VT that does keep all > keyboard-like devices open. Ah yes is that is likely the issue. I'll disable CONFIG_VT, and update in v5 to handle to keep the device from going to deep sleep when one or more LEDS is on. - Matt > > Thanks. > > -- > Dmitry