From: Daniel Vetter <daniel@ffwll.ch>
To: "Lofstedt, Marta" <marta.lofstedt@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 1/3] igt/kms_fbcon_fbt: Handle ENODEV when checking i915_edp_psr_status for chipset support
Date: Tue, 6 Mar 2018 15:56:27 +0100 [thread overview]
Message-ID: <20180306145627.GO22212@phenom.ffwll.local> (raw)
In-Reply-To: <CA5F6A4B62957246A95956419746064382B39509@IRSMSX106.ger.corp.intel.com>
On Thu, Feb 22, 2018 at 07:48:53AM +0000, Lofstedt, Marta wrote:
>
>
> > -----Original Message-----
> > From: Chris Wilson [mailto:chris@chris-wilson.co.uk]
> > Sent: Thursday, February 22, 2018 9:47 AM
> > To: Lofstedt, Marta <marta.lofstedt@intel.com>; igt-
> > dev@lists.freedesktop.org
> > Subject: Re: [igt-dev] [PATCH i-g-t 1/3] igt/kms_fbcon_fbt: Handle ENODEV
> > when checking i915_edp_psr_status for chipset support
> >
> > Quoting Marta Lofstedt (2018-02-22 07:43:41)
> > > If the machine doesn't support PSR, it will return -ENODEV from
> > > i915_edp_psr_status, which we want to interpret as unsupported.
> > > This is in line with what Chris just fixed for FBC.
> > >
> > > Signed-off-by: Marta Lofstedt <marta.lofstedt@intel.com>
> > > ---
> > > tests/kms_fbcon_fbt.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/tests/kms_fbcon_fbt.c b/tests/kms_fbcon_fbt.c index
> > > 1b236f8b..6aa171e6 100644
> > > --- a/tests/kms_fbcon_fbt.c
> > > +++ b/tests/kms_fbcon_fbt.c
> > > @@ -164,6 +164,8 @@ static bool psr_supported_on_chipset(int fd) {
> > > char buf[256];
> > >
> > > + if (*buf == '\0') /* !HAS_PSR -> -ENODEV*/
> > > + return false;
> > > igt_debugfs_read(fd, "i915_edp_psr_status", buf);
> >
> > After the read :)
>
> Yeah, was way too trigger happy here
Since Chris wrote the same patch from kms_frontbuffer_tracking ... should
we extract these into helpers in lib/ somewhere?
-Daniel
>
> >
> > > return strstr(buf, "Sink_Support: yes\n"); }
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-03-06 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 7:43 [igt-dev] [PATCH i-g-t 1/3] igt/kms_fbcon_fbt: Handle ENODEV when checking i915_edp_psr_status for chipset support Marta Lofstedt
2018-02-22 7:43 ` [igt-dev] [PATCH i-g-t 2/3] igt/kms_fronbuffer_tracking: " Marta Lofstedt
2018-02-22 7:43 ` [igt-dev] [PATCH i-g-t 3/3] HACK to get some PSR tests run on BAT Marta Lofstedt
2018-02-22 7:46 ` [igt-dev] [PATCH i-g-t 1/3] igt/kms_fbcon_fbt: Handle ENODEV when checking i915_edp_psr_status for chipset support Chris Wilson
2018-02-22 7:48 ` Lofstedt, Marta
2018-03-06 14:56 ` Daniel Vetter [this message]
2018-03-07 6:16 ` Lofstedt, Marta
2018-03-07 17:01 ` Daniel Vetter
2018-02-22 8:39 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] " Patchwork
2018-02-22 10:51 ` [igt-dev] ✗ Fi.CI.IGT: warning " Patchwork
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=20180306145627.GO22212@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=igt-dev@lists.freedesktop.org \
--cc=marta.lofstedt@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