From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
rafael@kernel.org, gregkh@linuxfoundation.org,
Jonathan Corbet <corbet@lwn.net>,
Ross Zwisler <zwisler@google.com>,
linux-kernel@vger.kernel.org, Mat King <mathewk@google.com>,
dri-devel@lists.freedesktop.org,
Jingoo Han <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 17:34:07 -0300 [thread overview]
Message-ID: <20191006203407.GA14301@khazad-dum.debian.net> (raw)
In-Reply-To: <20191003102254.dmwl6qimdca3dbrv@holly.lan>
On Thu, 03 Oct 2019, Daniel Thompson wrote:
> 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.
As far as I am concerned, it is *not* too late. And you can always have
a driver-private way of messing with something, and a more generic way
of doing the same thing.
thinkpad-acpi will always welcome patches switching to the new generic
way (as long as we can have a deprecation period *for long-time-used
facilities* -- which is not the case of the privacy screen, no
deprecation period need there).
The privacy thing is too new, feel free to design a generic one and
send in a patch *switching* thinkpad-acpi to the new generic one.
I would ACK that. If the subsystem maintainer also agrees, (and nobody
*seriously* complain about it from userspace), the private interface
would be gone just like that.
--
Henrique Holschuh
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-06 20:40 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
2019-10-06 20:34 ` Henrique de Moraes Holschuh [this message]
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=20191006203407.GA14301@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--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=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathewk@google.com \
--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