dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jingoo Han <jingoohan1@gmail.com>
To: Pavel Machek <pavel@denx.de>,
	Daniel Thompson <daniel.thompson@linaro.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"rafael@kernel.org" <rafael@kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Ross Zwisler <zwisler@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Mat King <mathewk@google.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Han Jingoo <jingoohan1@gmail.com>,
	Rajat Jain <rajatja@google.com>, Lee Jones <lee.jones@linaro.org>,
	Alexander Schremmer <alex@alexanderweb.de>
Subject: Re: New sysfs interface for privacy screens
Date: Sun, 6 Oct 2019 16:48:31 +0000	[thread overview]
Message-ID: <SL2P216MB01055AE2F23BB2546DC93708AA980@SL2P216MB0105.KORP216.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20191006110455.GC24605@amd>



> On 10/6/19, 7:04 AM, Pavel Machek wrote:
>
> Hi!
>
> > > >> I have been looking into adding Linux support for electronic privacy
> > > >> screens which is a feature on some new laptops which is built into the
> > > >> display and allows users to turn it on instead of needing to use a
> > > >> physical privacy filter. In discussions with my colleagues the idea of
> > > >> using either /sys/class/backlight or /sys/class/leds but this new
> > > >> feature does not seem to quite fit into either of those classes.
> > > >
> > > > FWIW, it seems that you're not alone in this; 5.4 got some support for
> > > > such screens if I understand things correctly:
> > > >
> > > >   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=110ea1d833ad
> > > 
> > > Oh, I didn't realize it got merged already, I thought this was
> > > related...
> > > 
> > > So we've already replicated the backlight sysfs interface problem for
> > > privacy screens. :(
> > 
> > I guess... although the Thinkpad code hasn't added any standard
> > interfaces (no other laptop should be placing controls for a privacy
> > screen in /proc/acpi/ibm/... ). Maybe its not too late.
>
> There's new interface for controlling privacyguard... but perhaps we
> need better solution than what went in 5.4. Perhaps it should be
> reconsidered?

I agree with your opinion. I also think that better solution can be considered,
although there is already something in 5.4.

Best regards,
Jingoo Han

>
> Best regards,
>									Pavel
> -- 
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-10-06 16:48 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 16:09 New sysfs interface for privacy screens Mat King
2019-10-01 16:27 ` Greg KH
2019-10-01 16:42   ` Mat King
2019-10-02  9:30 ` Jani Nikula
2019-10-02 10:24   ` Daniel Thompson
2019-10-02 10:46     ` Jani Nikula
2019-10-02 15:25       ` Mat King
2019-10-03  8:59         ` Jani Nikula
2019-10-03 19:57           ` Mat King
2019-10-07  4:56             ` Rajat Jain
2019-10-07  8:59               ` Jani Nikula
2019-10-07 13:08             ` Sean Paul
2019-10-07 16:19               ` Mat King
2019-10-07 19:31                 ` Rajat Jain
2019-10-07 19:53                   ` Sean Paul
2019-10-08  6:13                 ` Jani Nikula
2019-10-23  0:14                   ` Rajat Jain
2019-10-23  0:17                     ` Rajat Jain
2019-10-23  8:39                   ` Daniel Vetter
2019-10-02 15:46 ` Jonathan Corbet
2019-10-02 17:13   ` Mat King
2019-10-03  8:19   ` Jani Nikula
2019-10-03 10:22     ` Daniel Thompson
2019-10-06 11:04       ` Pavel Machek
2019-10-06 16:48         ` Jingoo Han [this message]
2019-10-06 20:34       ` Henrique de Moraes Holschuh
2019-10-06 11:00   ` Pavel Machek
2019-10-06 10:58 ` Pavel Machek

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=SL2P216MB01055AE2F23BB2546DC93708AA980@SL2P216MB0105.KORP216.PROD.OUTLOOK.COM \
    --to=jingoohan1@gmail.com \
    --cc=alex@alexanderweb.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=daniel.thompson@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathewk@google.com \
    --cc=pavel@denx.de \
    --cc=rafael@kernel.org \
    --cc=rajatja@google.com \
    --cc=zwisler@google.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;
as well as URLs for NNTP newsgroup(s).