From: Simon Ser <contact@emersion.fr>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Pekka Paalanen <ppaalanen@gmail.com>,
Rob Clark <robdclark@chromium.org>,
Brian Norris <briannorris@chromium.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
David Airlie <airlied@linux.ie>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Doug Anderson <dianders@chromium.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
"Kristian H . Kristensen" <hoegsberg@google.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-input@vger.kernel.org
Subject: Re: [PATCH v2 1/2] drm/input_helper: Add new input-handling helper
Date: Fri, 19 Nov 2021 16:04:28 +0000 [thread overview]
Message-ID: <98236dpcx39iOz8xAYrwGLfiLdwgUlljrbBgHL3wd8A0Wz4KzRk3PR8s_tb5Rxu4eScKI4483kB6Vhv-T64CJYOeQqwXlqo2c-64HvoS5cg=@emersion.fr> (raw)
In-Reply-To: <YZfIgd8s7uGXAD2X@phenom.ffwll.local>
On Friday, November 19th, 2021 at 16:53, Daniel Vetter <daniel@ffwll.ch> wrote:
> Random idea ... should we perhaps let userspace connect the boosting? I.e.
> we do a bunch of standardized boost targets (render clocks, display sr
> exit), and userspace can then connect it to whichever input device it
> wants to?
On IRC we discussed having user-space hand over a FD to the kernel. When the FD
becomes readable, the kernel triggers the boost.
This would let user-space use e.g. an input device, an eventfd, or an epoll FD
with any combination of these as the boost signal.
next prev parent reply other threads:[~2021-11-19 16:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 22:48 [PATCH v2 0/2] drm: Support input-boosted panel self-refresh exit Brian Norris
2021-11-17 22:48 ` [PATCH v2 1/2] drm/input_helper: Add new input-handling helper Brian Norris
2021-11-18 9:05 ` Daniel Vetter
2021-11-18 19:30 ` Brian Norris
2021-11-19 10:01 ` Daniel Vetter
2021-11-19 19:07 ` Brian Norris
2021-11-25 15:25 ` Daniel Vetter
2021-11-18 10:39 ` Pekka Paalanen
2021-11-18 23:30 ` Rob Clark
2021-11-19 9:54 ` Pekka Paalanen
2021-11-19 15:53 ` Daniel Vetter
2021-11-19 16:04 ` Simon Ser [this message]
2021-11-19 16:11 ` Daniel Vetter
2021-11-22 9:43 ` Pekka Paalanen
2021-11-25 15:30 ` Daniel Vetter
2021-11-19 16:44 ` Rob Clark
2021-11-19 16:50 ` Doug Anderson
2021-11-19 1:46 ` Brian Norris
2021-11-19 10:38 ` Pekka Paalanen
2021-11-19 15:56 ` Daniel Vetter
2021-11-22 9:25 ` Pekka Paalanen
2021-11-30 20:35 ` Brian Norris
2021-12-07 3:16 ` Peter Hutterer
2021-11-17 22:48 ` [PATCH v2 2/2] drm/self_refresh: Disable self-refresh on input events Brian Norris
2021-11-18 9:11 ` Daniel Vetter
2021-11-18 8:34 ` [PATCH v2 0/2] drm: Support input-boosted panel self-refresh exit Simon Ser
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='98236dpcx39iOz8xAYrwGLfiLdwgUlljrbBgHL3wd8A0Wz4KzRk3PR8s_tb5Rxu4eScKI4483kB6Vhv-T64CJYOeQqwXlqo2c-64HvoS5cg=@emersion.fr' \
--to=contact@emersion.fr \
--cc=airlied@linux.ie \
--cc=andrzej.hajda@intel.com \
--cc=briannorris@chromium.org \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoegsberg@google.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ppaalanen@gmail.com \
--cc=robdclark@chromium.org \
--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).