From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Add a DRM property "psr"
Date: Thu, 20 Mar 2014 17:16:36 +0200 [thread overview]
Message-ID: <20140320151636.GE21652@intel.com> (raw)
In-Reply-To: <87vbv90vt1.fsf@intel.com>
On Thu, Mar 20, 2014 at 04:49:30PM +0200, Jani Nikula wrote:
> On Thu, 20 Mar 2014, Siva Chandra <sivachandra@google.com> wrote:
> > On Thu, Mar 20, 2014 at 6:25 AM, Jani Nikula
> > <jani.nikula@linux.intel.com> wrote:
> >> On Thu, 20 Mar 2014, Siva Chandra <sivachandra@google.com> wrote:
> >>> On Thu, Mar 20, 2014 at 3:52 AM, Jani Nikula
> >>> <jani.nikula@linux.intel.com> wrote:
> >>>> If this is for testing only, and the module parameter does not quite cut
> >>>> it, please add it to debugfs. That we can pretty much change at will.
> >>>
> >>> If I understand correctly, you are suggesting that the on/off knob
> >>> live in debugfs. So, should the module param in sysfs mirror this
> >>> debugfs knob?
> >>
> >> I guess the simplest thing to move forward would be something to update
> >> psr state after the module parameter has been changed, although it's
> >> perhaps a bit clumsy to use.
> >
> > Couldn't understand. May be an example to illustrate what you are saying?
>
> echo 1 > /sys/module/i915/parameters/enable_psr
> echo something > sys/kernel/debug/dri/0/i915_edp_psr_update
>
> where that debugfs file essentially calls intel_edp_psr_update() on
> update.
>
> I guess it could be i915_edp_psr_enable and echoing there would modify
> the module parameter and call update. With debugfs I'm not so fussy.
Whatever the interface I think it might be nice to allow you to force
the mode of PSR operation (main link off vs. standby).
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-03-20 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 19:51 [PATCH] drm/i915: Add a DRM property "psr" Siva Chandra
2014-03-18 20:06 ` Jesse Barnes
2014-03-18 20:53 ` Siva Chandra
2014-03-19 8:44 ` Daniel Vetter
2014-03-19 15:03 ` Damien Lespiau
2014-03-19 17:04 ` Siva Chandra
2014-03-20 10:52 ` Jani Nikula
2014-03-20 13:17 ` Siva Chandra
2014-03-20 13:25 ` Jani Nikula
2014-03-20 13:31 ` Siva Chandra
2014-03-20 14:49 ` Jani Nikula
2014-03-20 15:16 ` Ville Syrjälä [this message]
2014-03-21 21:10 ` Siva Chandra
2014-03-19 15:32 ` Jani Nikula
2014-03-19 16:59 ` Siva Chandra
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=20140320151636.GE21652@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.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