From: Brian Norris <briannorris@chromium.org>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
David Airlie <airlied@linux.ie>,
linux-rockchip@lists.infradead.org,
"Kristian H . Kristensen" <hoegsberg@google.com>,
Doug Anderson <dianders@chromium.org>,
Rob Clark <robdclark@chromium.org>,
Rob Clark <robdclark@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Brian Norris <briannorris@chromium.org>
Subject: [PATCH 0/2] drm: Support input-boosted panel self-refresh exit
Date: Wed, 3 Nov 2021 16:40:16 -0700 [thread overview]
Message-ID: <20211103234018.4009771-1-briannorris@chromium.org> (raw)
A variety of applications have found it useful to listen to
user-initiated input events to make decisions within a DRM driver, given
that input events are often the first sign that we're going to start
doing latency-sensitive activities:
* Panel self-refresh: software-directed self-refresh (e.g., with
Rockchip eDP) is especially latency sensitive. In some cases, it can
take 10s of milliseconds for a panel to exit self-refresh, which can
be noticeable. Rockchip RK3399 Chrome OS systems have always shipped
with an input_handler boost, that preemptively exits self-refresh
whenever there is input activity.
* GPU drivers: on GPU-accelerated desktop systems, we may need to
render new frames immediately after user activity. Powering up the
GPU can take enough time that it is worthwhile to start this process
as soon as there is input activity. Many Chrome OS systems also ship
with an input_handler boost that powers up the GPU.
I implement the first bullet in this series, and I also compared with
some out-of-tree patches for the second, to ensure this could be useful
there too.
Past work on upstreaming a variety of Chromebook display patches got
held up for this particular feature, as there was some desire to make it
a bit more generic, for one. See the latest here:
https://lore.kernel.org/all/20180405095000.9756-25-enric.balletbo@collabora.com/
[PATCH v6 24/30] drm/rockchip: Disable PSR on input events
I significantly rewrote this to adapt it to the new common
drm_self_refresh_helpers and to add a new drm_input_helper thin library,
so I only carry my own authorship on this series.
Admittedly, this "drm_input_helper" library is barely DRM-specific at
all, except that all display- and GPU-related input-watchers are likely
to want to watch similar device behavior (unlike, say, rfkill or led
input_handler code). If we find other applications need the same
behavior outside of drivers/gpu/drm/, maybe this could find a home
elsewhere.
Brian Norris (2):
drm/input_helper: Add new input-handling helper
drm/self_refresh: Disable self-refresh on input events
drivers/gpu/drm/Makefile | 3 +-
drivers/gpu/drm/drm_input_helper.c | 143 ++++++++++++++++++++++
drivers/gpu/drm/drm_self_refresh_helper.c | 54 +++++++-
include/drm/drm_input_helper.h | 22 ++++
4 files changed, 215 insertions(+), 7 deletions(-)
create mode 100644 drivers/gpu/drm/drm_input_helper.c
create mode 100644 include/drm/drm_input_helper.h
--
2.34.0.rc0.344.g81b53c2807-goog
next reply other threads:[~2021-11-03 23:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 23:40 Brian Norris [this message]
2021-11-03 23:40 ` [PATCH 1/2] drm/input_helper: Add new input-handling helper Brian Norris
2021-11-04 10:47 ` kernel test robot
2021-11-04 21:45 ` Brian Norris
2021-11-04 13:20 ` kernel test robot
2021-11-04 13:46 ` kernel test robot
2021-11-05 23:11 ` Dmitry Torokhov
2021-11-13 0:52 ` Doug Anderson
2021-11-17 18:38 ` Brian Norris
2021-11-17 20:47 ` Dmitry Torokhov
2021-11-17 20:56 ` Doug Anderson
2021-11-17 22:27 ` Rob Clark
2021-11-03 23:40 ` [PATCH 2/2] drm/self_refresh: Disable self-refresh on input events Brian Norris
2021-11-13 0:52 ` Doug Anderson
2021-11-17 18:24 ` Brian Norris
2021-11-17 19:12 ` Daniel Vetter
2021-11-17 19:36 ` Brian Norris
2021-11-18 6:39 ` Daniel Vetter
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=20211103234018.4009771-1-briannorris@chromium.org \
--to=briannorris@chromium.org \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hoegsberg@google.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).