From: Sean Paul <seanpaul@chromium.org>
To: Rob Clark <robdclark@gmail.com>
Cc: Sean Paul <seanpaul@chromium.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
freedreno <freedreno@lists.freedesktop.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Brian Starkey <brian.starkey@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
Mihail Atanassov <mihail.atanassov@arm.com>,
Gustavo Padovan <gustavo@padovan.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
David Airlie <airlied@linux.ie>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC 1/4] drm: Add writeback connector type
Date: Fri, 23 Feb 2018 11:43:29 -0500 [thread overview]
Message-ID: <20180223164329.GO223881@art_vandelay> (raw)
In-Reply-To: <CAF6AEGs3EHxzwW4MaYc+LXmKL3amD8pUysamrprPy-F-W8=6AQ@mail.gmail.com>
On Fri, Feb 23, 2018 at 11:25:11AM -0500, Rob Clark wrote:
> On Fri, Feb 23, 2018 at 10:59 AM, Sean Paul <seanpaul@chromium.org> wrote:
> >
> > Have we considered hiding writeback behind a client cap instead?
>
> It is kinda *almost* unneeded, since the connector reports itself as
> disconnected.
>
> I'm not sure what the reason was to drop the cap, but I think it would
> be better to have a cap so WB connectors don't show up in, for ex,
> xrandr
Yeah, the disconnected hack is kind of gross, IMO. I hate to introduce churn in
the patch series given that it was initially introduced with the client cap.
There are also cases where we might want to make writeback unavailable, such as
when content protection is enabled. In those cases, it's conceivable that we
might want to use disconnected as a signal to u/s. I suppose we could also just
fail the check, so most of this is just academic.
Sean
>
> BR,
> -R
--
Sean Paul, Software Engineer, Google / Chromium OS
next prev parent reply other threads:[~2018-02-23 16:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180223131758.18362-1-robdclark@gmail.com>
2018-02-23 13:17 ` [RFC 1/4] drm: Add writeback connector type Rob Clark
2018-02-23 14:00 ` Liviu Dudau
2018-02-23 14:24 ` Rob Clark
2018-02-23 14:27 ` Liviu Dudau
2018-02-23 15:59 ` Sean Paul
2018-02-23 16:21 ` Liviu Dudau
2018-02-23 16:39 ` Sean Paul
2018-02-23 16:52 ` Liviu Dudau
2018-02-23 16:25 ` Rob Clark
2018-02-23 16:43 ` Sean Paul [this message]
2018-02-23 16:48 ` Liviu Dudau
2018-02-23 17:04 ` Sean Paul
2018-02-23 13:17 ` [RFC 2/4] drm: writeback: Add out-fences for writeback connectors Rob Clark
2018-02-23 16:14 ` Sean Paul
2018-02-23 13:17 ` [RFC 3/4] drm/msm/mdp5: add config for writeback pipes Rob Clark
2018-02-23 16:32 ` Sean Paul
2018-02-23 13:17 ` [RFC 4/4] drm/msm/mdp5: writeback support Rob Clark
2018-02-23 16:30 ` Sean Paul
2018-02-23 18:15 ` Rob Clark
2018-02-26 15:41 ` Sean Paul
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=20180223164329.GO223881@art_vandelay \
--to=seanpaul@chromium.org \
--cc=airlied@linux.ie \
--cc=brian.starkey@arm.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mihail.atanassov@arm.com \
--cc=robdclark@gmail.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