From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Feceoru, Gabriel" <gabriel.feceoru@intel.com>
Subject: Re: [PATCH i-g-t] kms_frontbuffer_tracking: Remove hardcoded PIPE_A
Date: Fri, 4 Mar 2016 22:18:18 +0000 [thread overview]
Message-ID: <1457129896.2375.22.camel@intel.com> (raw)
In-Reply-To: <1457085734-28438-1-git-send-email-gabriel.feceoru@intel.com>
Em Sex, 2016-03-04 às 12:02 +0200, Gabriel Feceoru escreveu:
> Use the pipe which is given from the possible_crcs for that connected
> port
> instead.
>
> On BSW there are constrains for the crtc<-->connector, this fix make
> this test
> passing on BSW.
>
> Signed-off-by: Gabriel Feceoru <gabriel.feceoru@intel.com>
Patch pushed. Thanks for catching this!
> ---
> tests/kms_frontbuffer_tracking.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/kms_frontbuffer_tracking.c
> b/tests/kms_frontbuffer_tracking.c
> index 634c98b..afdb394 100644
> --- a/tests/kms_frontbuffer_tracking.c
> +++ b/tests/kms_frontbuffer_tracking.c
> @@ -1432,7 +1432,8 @@ static void setup_crcs(void)
> {
> enum pixel_format f;
>
> - pipe_crc = igt_pipe_crc_new(0, INTEL_PIPE_CRC_SOURCE_AUTO);
> + int crtc_idx = kmstest_get_crtc_idx(drm.res,
> prim_mode_params.crtc_id);
> + pipe_crc = igt_pipe_crc_new(crtc_idx,
> INTEL_PIPE_CRC_SOURCE_AUTO);
>
> setup_sink_crc();
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-03-04 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 10:02 [PATCH i-g-t] kms_frontbuffer_tracking: Remove hardcoded PIPE_A Gabriel Feceoru
2016-03-04 22:18 ` Zanoni, Paulo R [this message]
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=1457129896.2375.22.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=gabriel.feceoru@intel.com \
--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