From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Nick Dyer <nick@shmanahar.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@bitmath.org>,
Arthur Demchenkov <spinal.by@gmail.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Merlijn Wajer <merlijn@wizzup.org>,
Sebastian Reichel <sre@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/3] Input: atmel_mxt_ts - use runtime PM instead of custom functions
Date: Wed, 9 Sep 2020 09:04:21 +0300 [thread overview]
Message-ID: <20200909060421.GD2747@atomide.com> (raw)
In-Reply-To: <20200908085111.GA31609@duo.ucw.cz>
* Pavel Machek <pavel@ucw.cz> [200908 08:51]:
> Hi!
>
> > Let's use standard runtime PM functions instead of custom start and stop
> > functions. This way we can implement runtime idle mode using runtime PM
> > autosuspend in the following patches.
>
> This is not in recent kernel. What needs to be done here?
Well it seems that it's lossy for normal use for taps requiring a short
swipe instead. So by default the autosuspend_timeout should be disabled.
This would be still usable for cases where we want to wake up the device
using touchscreen.
Regards,
Tony
prev parent reply other threads:[~2020-09-09 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 23:09 [PATCH 1/3] Input: atmel_mxt_ts - use runtime PM instead of custom functions Tony Lindgren
2020-03-18 23:09 ` [PATCH 2/3] Input: atmel_mxt_ts - add idle power config Tony Lindgren
2020-03-18 23:09 ` [PATCH 3/3] Input: atmel_mxt_ts - use runtime PM autosuspend for idle config Tony Lindgren
2020-03-20 19:00 ` Tony Lindgren
2020-03-19 9:27 ` [PATCH 1/3] Input: atmel_mxt_ts - use runtime PM instead of custom functions kbuild test robot
2020-03-19 9:27 ` [RFC PATCH] Input: mxt_pm_ops can be static kbuild test robot
2020-09-08 8:51 ` [PATCH 1/3] Input: atmel_mxt_ts - use runtime PM instead of custom functions Pavel Machek
2020-09-09 6:04 ` Tony Lindgren [this message]
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=20200909060421.GD2747@atomide.com \
--to=tony@atomide.com \
--cc=dmitry.torokhov@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=nick@shmanahar.org \
--cc=pavel@ucw.cz \
--cc=rydberg@bitmath.org \
--cc=spinal.by@gmail.com \
--cc=sre@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.