From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH libdrm] modetest: Allow full testing of primary planes
Date: Thu, 19 Oct 2017 19:17:37 +0300 [thread overview]
Message-ID: <20171019161737.GX10981@intel.com> (raw)
In-Reply-To: <20171016171056.10877-1-ville.syrjala@linux.intel.com>
On Mon, Oct 16, 2017 at 08:10:56PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Allow the user to override the default configuration set by setcrtc
> for the primary plane. On some hardware primary planes can be freely
> positioned/sized, and it'd be nice if we can actually test that feature.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
No one objected, so I went ahead and pushed this.
> ---
> tests/modetest/modetest.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/modetest/modetest.c b/tests/modetest/modetest.c
> index b8891ff5e2e8..eca8cde68123 100644
> --- a/tests/modetest/modetest.c
> +++ b/tests/modetest/modetest.c
> @@ -1005,7 +1005,8 @@ static int set_plane(struct device *dev, struct plane_arg *p)
> if (!format_support(ovr, p->fourcc))
> continue;
>
> - if ((ovr->possible_crtcs & (1 << pipe)) && !ovr->crtc_id) {
> + if ((ovr->possible_crtcs & (1 << pipe)) &&
> + (ovr->crtc_id == 0 || ovr->crtc_id == p->crtc_id)) {
> plane_id = ovr->plane_id;
> break;
> }
> --
> 2.13.6
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-10-19 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 17:10 [PATCH libdrm] modetest: Allow full testing of primary planes Ville Syrjala
2017-10-19 16:17 ` Ville Syrjälä [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=20171019161737.GX10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@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