From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mat King <mathewk@google.com>, Sean Paul <seanpaul@chromium.org>
Cc: "Daniel Thompson" <daniel.thompson@linaro.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
rafael@kernel.org, "Greg KH" <gregkh@linuxfoundation.org>,
"Ross Zwisler" <zwisler@google.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Rajat Jain" <rajatja@google.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"David Airlie" <airlied@redhat.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Alexander Schremmer" <alex@alexanderweb.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: New sysfs interface for privacy screens
Date: Tue, 08 Oct 2019 09:13:51 +0300 [thread overview]
Message-ID: <87sgo3dasg.fsf@intel.com> (raw)
In-Reply-To: <CAL_quvTe_v9Vsbd0u4URitojmD-_VFeaOQ1BBYZ_UGwYWynjVA@mail.gmail.com>
On Mon, 07 Oct 2019, Mat King <mathewk@google.com> wrote:
> That makes sense; just to confirm can a property be added or removed
> after the connector is registered?
You need to create the property before registering the drm device. You
can attach/detach the property later, but I should think you know by the
time you're registering the connector whether it supports the privacy
screen or not.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2019-10-08 6:13 UTC|newest]
Thread overview: 31+ 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 [this message]
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 11:04 ` Pavel Machek
2019-10-06 16:48 ` Jingoo Han
2019-10-06 16:48 ` Jingoo Han
2019-10-06 20:34 ` Henrique de Moraes Holschuh
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=87sgo3dasg.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@redhat.com \
--cc=alex@alexanderweb.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.thompson@linaro.org \
--cc=daniel.vetter@ffwll.ch \
--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=seanpaul@chromium.org \
--cc=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.