From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Attach a PSR property on eDP
Date: Sat, 14 Jun 2014 00:45:30 +0100 [thread overview]
Message-ID: <20140613234530.GA30903@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <CAKMK7uEPZBRAaxC4=SzqXqoDtajFLAr9TBvWRXOJC8_nbsxaGQ@mail.gmail.com>
On Sat, Jun 14, 2014 at 01:39:45AM +0200, Daniel Vetter wrote:
> On Fri, Jun 13, 2014 at 10:32 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > Let userspace know the status of Panel Self-Refresh by virtue of a
> > property on the appropriate connector.
> >
> > v2: Only attach the property if the driver is capable of PSR.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Shouldn't we attach this to the crtc? Imo makes semantically more
> sense. Or maybe to each plane and then we could label it a generic
> "frontbuffer rendering discourage" option.
It depends on the eDP panel itself, so it ties quite neatly into a
connector property. I'd also like a generic please don't render to the
directly into this CRTC property as well.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2014-06-13 23:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 20:28 [PATCH] drm/i915: Attach a PSR property on eDP Chris Wilson
2014-06-13 20:32 ` Chris Wilson
2014-06-13 23:39 ` Daniel Vetter
2014-06-13 23:45 ` Chris Wilson [this message]
2014-06-14 8:17 ` Damien Lespiau
2014-06-14 8:26 ` Chris Wilson
2014-06-14 8:48 ` Damien Lespiau
2014-06-14 8:39 ` Damien Lespiau
2014-06-14 12:28 ` Chris Wilson
2014-06-16 7:28 ` Chris Wilson
2014-06-16 7:32 ` Chris Wilson
2015-03-25 20:11 Rodrigo Vivi
2015-03-25 20:31 ` Chris Wilson
2015-03-25 20:37 ` Vivi, Rodrigo
2015-03-26 14:12 ` chris
2015-03-26 19:22 ` Rodrigo Vivi
2015-03-26 21:04 ` Chris Wilson
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=20140613234530.GA30903@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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.