From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm: check user mode flags for validity
Date: Thu, 9 May 2013 01:25:59 +0300 [thread overview]
Message-ID: <20130508222559.GP14974@intel.com> (raw)
In-Reply-To: <1368046886-11932-1-git-send-email-jbarnes@virtuousgeek.org>
On Wed, May 08, 2013 at 02:01:25PM -0700, Jesse Barnes wrote:
> Requested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> ---
> drivers/gpu/drm/drm_crtc.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> index 792c3e3..72ae33a 100644
> --- a/drivers/gpu/drm/drm_crtc.c
> +++ b/drivers/gpu/drm/drm_crtc.c
> @@ -1318,6 +1318,18 @@ static int drm_crtc_convert_umode(struct drm_display_mode *out,
> if (in->clock > INT_MAX || in->vrefresh > INT_MAX)
> return -ERANGE;
>
> + /* Reject modes with invalid h/vsync */
> + if (!(in->flags & (DRM_MODE_FLAG_PHSYNC | DRM_MODE_FLAG_NHSYNC)))
> + return -EINVAL;
> + if ((in->flags & DRM_MODE_FLAG_PHSYNC) &&
> + (in->flags & DRM_MODE_FLAG_NHSYNC))
> + return -EINVAL;
> + if (!(in->flags & (DRM_MODE_FLAG_PVSYNC | DRM_MODE_FLAG_NVSYNC)))
> + return -EINVAL;
> + if ((in->flags & DRM_MODE_FLAG_PVSYNC) &&
> + (in->flags & DRM_MODE_FLAG_NVSYNC))
> + return -EINVAL;
That might be a bit too drastic. Well I suppose making sure that both
flags are not enabled at the same time could be OK. But having neither
flag set could be perfectly legal (the user could be asking for composite
sync instead for example).
So my less drastic suggestion would be doing something like this in i915
specific code:
adjusted_mode->flags = 0;
if (requested_mode->flags & NHSYNC)
adjusted_mode->flags |= NHSYNC;
else
adjusted_mode->flags |= PHSYNC;
It would gurantee that we end up picking exactly one of the flags in
every case. If both are set, we pick -, of neither is set we pick +.
> +
> out->clock = in->clock;
> out->hdisplay = in->hdisplay;
> out->hsync_start = in->hsync_start;
> --
> 1.7.9.5
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-05-08 22:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 18:35 [PATCH] drm/i915: add encoder get_config function v3 Jesse Barnes
2013-05-07 22:38 ` Jesse Barnes
2013-05-08 10:39 ` Ville Syrjälä
2013-05-08 21:01 ` [PATCH] drm/i915: add encoder get_config function v4 Jesse Barnes
2013-05-08 22:28 ` Ville Syrjälä
2013-05-10 7:21 ` Daniel Vetter
2013-05-10 20:20 ` Daniel Vetter
2013-05-08 21:01 ` [PATCH] drm: check user mode flags for validity Jesse Barnes
2013-05-08 22:25 ` Ville Syrjälä [this message]
2013-05-10 16:08 ` Jesse Barnes
2013-05-10 18:58 ` Ville Syrjälä
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=20130508222559.GP14974@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.