From: Pavel Machek <pavel@denx.de>
To: Rajat Jain <rajatja@google.com>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Sean Paul" <sean@poorly.run>, "David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Imre Deak" <imre.deak@intel.com>,
"José Roberto de Souza" <jose.souza@intel.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, gregkh@linuxfoundation.org,
mathewk@google.com,
"Daniel Thompson" <daniel.thompson@linaro.org>,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH] drm: Add support for integrated privacy screens
Date: Thu, 24 Oct 2019 13:06:46 +0200 [thread overview]
Message-ID: <20191024110646.GA3419@amd> (raw)
In-Reply-To: <20191023001206.15741-1-rajatja@google.com>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
On Tue 2019-10-22 17:12:06, Rajat Jain wrote:
> Certain laptops now come with panels that have integrated privacy
> screens on them. This patch adds support for such panels by adding
> a privacy-screen property to the drm_connector for the panel, that
> the userspace can then use to control and check the status. The idea
> was discussed here:
Much better than separate /sys interface, thanks!
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@denx.de>
To: Rajat Jain <rajatja@google.com>
Cc: seanpaul@google.com, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Daniel Thompson <daniel.thompson@linaro.org>,
Jonathan Corbet <corbet@lwn.net>,
jsbarnes@google.com, rajatxjain@gmail.com,
intel-gfx@lists.freedesktop.org, mathewk@google.com,
Maxime Ripard <mripard@kernel.org>,
Duncan Laurie <dlaurie@google.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Pavel Machek <pavel@denx.de>
Subject: Re: [Intel-gfx] [PATCH] drm: Add support for integrated privacy screens
Date: Thu, 24 Oct 2019 13:06:46 +0200 [thread overview]
Message-ID: <20191024110646.GA3419@amd> (raw)
Message-ID: <20191024110646.OBWRhYHJ1zNHWJDTgHiZZZWxt0JjgZkDCB04Nl8hxag@z> (raw)
In-Reply-To: <20191023001206.15741-1-rajatja@google.com>
[-- Attachment #1.1: Type: text/plain, Size: 576 bytes --]
On Tue 2019-10-22 17:12:06, Rajat Jain wrote:
> Certain laptops now come with panels that have integrated privacy
> screens on them. This patch adds support for such panels by adding
> a privacy-screen property to the drm_connector for the panel, that
> the userspace can then use to control and check the status. The idea
> was discussed here:
Much better than separate /sys interface, thanks!
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-24 11:06 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 0:12 [PATCH] drm: Add support for integrated privacy screens Rajat Jain
2019-10-23 0:12 ` [Intel-gfx] " Rajat Jain
2019-10-23 9:21 ` Daniel Vetter
2019-10-23 9:21 ` [Intel-gfx] " Daniel Vetter
2019-10-24 1:48 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2019-10-24 1:48 ` [Intel-gfx] " Patchwork
2019-10-24 7:01 ` Jani Nikula
2019-10-24 7:01 ` [Intel-gfx] " Jani Nikula
2019-10-24 18:18 ` Rajat Jain
2019-10-24 18:18 ` [Intel-gfx] " Rajat Jain
2019-10-24 11:06 ` Pavel Machek [this message]
2019-10-24 11:06 ` [Intel-gfx] [PATCH] " Pavel Machek
2019-10-24 11:20 ` Thierry Reding
2019-10-24 11:20 ` [Intel-gfx] " Thierry Reding
2019-10-24 20:45 ` Rajat Jain
2019-10-25 11:36 ` Thierry Reding
2019-10-25 11:36 ` [Intel-gfx] " Thierry Reding
2019-10-25 19:00 ` Rajat Jain
2019-10-25 19:00 ` [Intel-gfx] " Rajat Jain
2019-10-25 19:03 ` Daniel Vetter
2019-10-25 19:03 ` [Intel-gfx] " Daniel Vetter
2019-10-28 8:12 ` Pekka Paalanen
2019-10-28 8:12 ` [Intel-gfx] " Pekka Paalanen
2019-10-26 11:07 ` Daniel Stone
2019-10-26 11:07 ` Daniel Stone
2019-10-26 17:18 ` Daniel Vetter
2019-10-26 17:18 ` Daniel Vetter
2019-10-24 18:57 ` kbuild test robot
2019-10-24 18:57 ` [Intel-gfx] " kbuild test robot
2019-10-24 19:44 ` kbuild test robot
2019-10-24 19:44 ` [Intel-gfx] " kbuild test robot
2019-11-04 19:41 ` [PATCH v2 1/3] drm/i915: Move the code to populate ACPI device ID into intel_acpi Rajat Jain
2019-11-04 19:41 ` [Intel-gfx] " Rajat Jain
2019-11-04 19:41 ` [PATCH v2 2/3] drm/i915: Lookup and attach ACPI device node for connectors Rajat Jain
2019-11-04 19:41 ` [Intel-gfx] " Rajat Jain
2019-11-20 14:50 ` Jani Nikula
2019-11-20 14:50 ` [Intel-gfx] " Jani Nikula
2019-12-05 9:34 ` Rajat Jain
2019-11-04 19:41 ` [PATCH v2 3/3] drm/i915: Add support for integrated privacy screens Rajat Jain
2019-11-04 19:41 ` [Intel-gfx] " Rajat Jain
2019-11-12 19:12 ` Rajat Jain
2019-11-12 19:12 ` [Intel-gfx] " Rajat Jain
2019-11-12 19:12 ` Rajat Jain
2019-11-12 19:12 ` [Intel-gfx] " Rajat Jain
2019-11-20 15:10 ` Jani Nikula
2019-11-20 15:10 ` [Intel-gfx] " Jani Nikula
2019-11-20 21:35 ` Rajat Jain
2019-11-20 21:35 ` [Intel-gfx] " Rajat Jain
2019-11-20 15:04 ` Jani Nikula
2019-11-20 15:04 ` [Intel-gfx] " Jani Nikula
2019-12-05 9:34 ` Rajat Jain
2019-12-20 20:39 ` Rajat Jain
2019-11-20 14:40 ` [PATCH v2 1/3] drm/i915: Move the code to populate ACPI device ID into intel_acpi Jani Nikula
2019-11-20 14:40 ` [Intel-gfx] " Jani Nikula
2019-12-05 9:34 ` Rajat Jain
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=20191024110646.GA3419@amd \
--to=pavel@denx.de \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=corbet@lwn.net \
--cc=daniel.thompson@linaro.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=jose.souza@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mathewk@google.com \
--cc=mripard@kernel.org \
--cc=rajatja@google.com \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
--cc=ville.syrjala@linux.intel.com \
/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