[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200320190040.GP37466@atomide.com>
Date: Fri, 20 Mar 2020 12:00:40 -0700
From: Tony Lindgren <tony@...mide.com>
To: Nick Dyer <nick@...anahar.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Henrik Rydberg <rydberg@...math.org>,
Arthur Demchenkov <spinal.by@...il.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
Merlijn Wajer <merlijn@...zup.org>,
Pavel Machek <pavel@....cz>,
Sebastian Reichel <sre@...nel.org>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org
Subject: Re: [PATCH 3/3] Input: atmel_mxt_ts - use runtime PM autosuspend for
idle config
* Tony Lindgren <tony@...mide.com> [200318 23:10]:
> Let's enable runtime PM autosuspend with a default value of 600 ms and
> switch to idle power config for runtime_suspend. The autosuspend timeout
> can also be configured also via userspace with value of -1 disabling the
> autosuspend.
>
> Let's only allow autosuspend if MXT_SUSPEND_T9_CTRL is not configured for
> suspend_mode as MXT_SUSPEND_T9_CTRL mode powers off the controller.
Hmm looks like with autosuspend enabled I need a short swipe instead of
just clicking on the screen to produce a click. So we may want to default
to autosuspend timeout of -1 and have user set it when suitable and no
other fix is found.
On droid4, I've confirmed that disabling autosuspend fixes the issue FYI:
# echo on > /sys/bus/i2c/drivers/atmel_mxt_ts/1-004a/power/control
Regards,
Tony
Powered by blists - more mailing lists