dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/connector: Document the optional margin props in the HDMI section
Date: Wed, 27 Mar 2019 13:27:18 +0100	[thread overview]
Message-ID: <20190327132718.3fb1349a@collabora.com> (raw)
In-Reply-To: <20190327111930.GI2665@phenom.ffwll.local>

On Wed, 27 Mar 2019 12:19:30 +0100
Daniel Vetter <daniel@ffwll.ch> wrote:

> On Wed, Mar 27, 2019 at 10:59:15AM +0100, Boris Brezillon wrote:
> > HDMI connectors can optionally be attached margin props. Let's
> > document them.
> > 
> > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> > ---
> >  drivers/gpu/drm/drm_connector.c | 17 +++++++++++++++++
> >  1 file changed, 17 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
> > index 2355124849db..95dfb322b14e 100644
> > --- a/drivers/gpu/drm/drm_connector.c
> > +++ b/drivers/gpu/drm/drm_connector.c
> > @@ -1116,6 +1116,23 @@ EXPORT_SYMBOL(drm_mode_create_dvi_i_properties);
> >   *	Drivers can set up this property by calling
> >   *	drm_connector_attach_content_type_property(). Decoding to
> >   *	infoframe values is done through drm_hdmi_avi_infoframe_content_type().
> > + *
> > + * TV margins (optional):
> > + *	Defines invisible area of a screen so that the CRTC driver can possibly
> > + *	scale the output image and move it to make it entirely visible. All
> > + *	margins are defined in pixels and the valid range is 0 - 100.  
> 
> Maybe add the usual hints for driver writers too:
> 
> "Drivers can set this up by calling
> drm_connector_attach_tv_margin_properties(), the values are stored in
> &drm_connector_state.tv."
> 
> With that: Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> 
> I'm also not entirely sure it's in pixels, but *shrug*

I'm sure the VC4 driver considers it's expressed in pixels :P. This was
decided after the discussion we had with Ville (when I submitted
margins support for VC4).

> -Daniel
> 
> 
> > + *
> > + *	left margin:
> > + *		Left margin
> > + *
> > + *	right margin:
> > + *		Left margin
> > + *
> > + *	top margin:
> > + *		Top margin
> > + *
> > + *	bottom margin:
> > + *		Bottom margin
> >   */
> >  
> >  /**
> > -- 
> > 2.20.1
> >   
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2019-03-27 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27  9:59 [PATCH 1/2] drm/connector: Document the optional margin props in the HDMI section Boris Brezillon
2019-03-27  9:59 ` [PATCH 2/2] drm/connector: Document the TV props Boris Brezillon
2019-03-27 11:26   ` Daniel Vetter
2019-03-27 12:23     ` Boris Brezillon
2019-03-27 14:34       ` Daniel Vetter
2019-03-27 11:19 ` [PATCH 1/2] drm/connector: Document the optional margin props in the HDMI section Daniel Vetter
2019-03-27 12:27   ` Boris Brezillon [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=20190327132718.3fb1349a@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=daniel@ffwll.ch \
    --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