public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Attach a PSR property on eDP
Date: Wed, 25 Mar 2015 20:37:29 +0000	[thread overview]
Message-ID: <1427315844.4663.164.camel@intel.com> (raw)
In-Reply-To: <20150325203148.GA18055@nuc-i3427.alporthouse.com>

On Wed, 2015-03-25 at 20:31 +0000, Chris Wilson wrote:
> On Wed, Mar 25, 2015 at 01:11:57PM -0700, Rodrigo Vivi wrote:
> > From: Chris Wilson <chris@chris-wilson.co.uk>
> > 
> > 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.
> > v3: Add docbook courtesy of Damien.
> > v4: Mark the initial value as 'unsupported' - it will be determined
> >     correctly when we later read the DCPD from the panel.
> > v5: Done by Rodrigo:
> >     	 - Add disabled state to match all cases
> > 	 - Attach it anyway to eDP since it is started as unsupported
> > 	 - Change prop name to PSR
> > 	 - Add enum to make states more clear
> > 	 - Rebased on intel_psr.c changing func name and fixing states
> > 
> > +void intel_attach_psr_property(struct drm_connector *connector)
> > +{
> > +	struct drm_device *dev = connector->dev;
> > +	struct drm_i915_private *dev_priv = dev->dev_private;
> > +	struct drm_property *prop;
> > +
> > +	prop = dev_priv->psr.property;
> > +	if (prop == NULL) {
> > +		prop = drm_property_create_enum(dev,
> > +						DRM_MODE_PROP_ENUM |
> > +						DRM_MODE_PROP_IMMUTABLE,
> > +						"PSR",
> > +						psr_names,
> > +						ARRAY_SIZE(psr_names));
> 
> Are you sure you want the user visible string to be "PSR"? Googling
> prefers "Panel Self-Refresh".

To be honest, no I'm not sure... something I regretted already... Sorry!

Also talking about visible names I'm not sure about "Idle" as well...
Every time I read it get confused... I believe it is because PSR active
needs Idle usage...

What do you think about changing to Idle to Enable-Exit and Active to
Enable-Active?


> -Chris
> 

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-03-25 20:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 20:11 [PATCH] drm/i915: Attach a PSR property on eDP Rodrigo Vivi
2015-03-25 20:31 ` Chris Wilson
2015-03-25 20:37   ` Vivi, Rodrigo [this message]
2015-03-26 14:12     ` chris
2015-03-26 19:22       ` Rodrigo Vivi
2015-03-26 21:04         ` Chris Wilson
  -- strict thread matches above, loose matches on Subject: below --
2014-06-13 20:28 Chris Wilson
2014-06-13 20:32 ` Chris Wilson
2014-06-13 23:39   ` Daniel Vetter
2014-06-13 23:45     ` Chris Wilson
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

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=1427315844.4663.164.camel@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox