From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Nick Dyer <nick.dyer@itdev.co.uk>
Cc: linux-input@vger.kernel.org, Alan Bowens <Alan.Bowens@atmel.com>
Subject: Re: [PATCH 2/9] Input: atmel_mxt_ts - use deep sleep mode when stopped
Date: Thu, 6 Aug 2015 15:57:22 -0700 [thread overview]
Message-ID: <20150806225722.GB24261@dtor-ws> (raw)
In-Reply-To: <55C35B4F.2000006@itdev.co.uk>
On Thu, Aug 06, 2015 at 02:04:15PM +0100, Nick Dyer wrote:
>
>
> On 05/08/15 01:02, Dmitry Torokhov wrote:
> > Since the T9 code is for compatibility with old Pixel only I do not think
> > we should be adding it to device tree binding, at least not at the
> > moment. I cut the device tree parsing out and default to deep sleep on
> > DT-based systems. Thanks.
>
> That sounds fair enough. We do need something like this eventually to
> support different suspend implementations (eg powering down via regulators).
That does not really need config I think: in ChromeOS tree wee key the
behavior off presence of reset GPIO line: if it sis there (definied via
ACPI, devicetree or board lookup code) then we assume we need to control
the power up sequence with regulators, otherwise we put the controller
into deep sleep mode.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2015-08-06 22:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 15:23 atmel_mxt_ts - suspend patch and minor fixes Nick Dyer
2015-08-03 15:23 ` [PATCH 1/9] MAINTAINERS: Add maintainer for atmel_mxt_ts Nick Dyer
2015-08-03 15:23 ` [PATCH 2/9] Input: atmel_mxt_ts - use deep sleep mode when stopped Nick Dyer
2015-08-05 0:02 ` Dmitry Torokhov
2015-08-06 13:04 ` Nick Dyer
2015-08-06 22:57 ` Dmitry Torokhov [this message]
2015-08-10 20:11 ` Benjamin Tissoires
2015-08-11 14:24 ` Nick Dyer
2015-08-11 15:55 ` Nick Dyer
2015-08-11 16:29 ` Benjamin Tissoires
2015-08-11 18:32 ` Nick Dyer
2015-08-03 15:23 ` [PATCH 3/9] Input: atmel_mxt_ts - remove unused defines Nick Dyer
2015-08-03 15:23 ` [PATCH 4/9] Input: atmel_mxt_ts - move mxt_initialize after sysfs init Nick Dyer
2015-08-05 0:00 ` Dmitry Torokhov
2015-08-03 15:23 ` [PATCH 5/9] Input: atmel_mxt_ts - suspend/resume causes panic if input_dev fails to init Nick Dyer
2015-08-03 15:23 ` [PATCH 6/9] Input: atmel_mxt_ts - improve device tree parsing Nick Dyer
2015-08-03 15:23 ` [PATCH 7/9] Input: atmel_mxt_ts - disable interrupt for 50ms after reset Nick Dyer
2015-08-03 15:23 ` [PATCH 8/9] Input: atmel_mxt_ts - initialise input slots with INPUT_MT_DIRECT Nick Dyer
2015-08-03 15:23 ` [PATCH 9/9] Input: atmel_mxt_ts - remove warning on zero T44 count Nick Dyer
2015-08-05 0:03 ` atmel_mxt_ts - suspend patch and minor fixes Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150806225722.GB24261@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Alan.Bowens@atmel.com \
--cc=linux-input@vger.kernel.org \
--cc=nick.dyer@itdev.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox