From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Ser <contact@emersion.fr>
Cc: dri-devel@lists.freedesktop.org,
"Mateusz Kwiatkowski" <kfyatek+publicgit@gmail.com>,
"Pekka Paalanen" <ppaalanen@gmail.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Maxime Ripard" <maxime@cerno.tech>
Subject: Re: [PATCH v2] drm: document connector margin properties
Date: Tue, 28 Feb 2023 14:44:54 +0200 [thread overview]
Message-ID: <Y/33RipzQtGhPJCg@intel.com> (raw)
In-Reply-To: <20230228123156.175973-1-contact@emersion.fr>
On Tue, Feb 28, 2023 at 12:32:04PM +0000, Simon Ser wrote:
> Add docs for "{left,right,top,bottom} margin" properties.
>
> v2:
> - Mention the purpose: mitigate underscan on TVs
> - Move out of analog TV section into standard props (Pekka)
> - Mention HDMI AVI InfoFrames (Pekka, Ville)
>
> Signed-off-by: Simon Ser <contact@emersion.fr>
> Cc: Maxime Ripard <maxime@cerno.tech>
> Cc: Daniel Vetter <daniel@ffwll.ch>
> Cc: Pekka Paalanen <ppaalanen@gmail.com>
> Cc: Noralf Trønnes <noralf@tronnes.org>
> Cc: Mateusz Kwiatkowski <kfyatek+publicgit@gmail.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/drm_connector.c | 18 ++++++++++++++----
> 1 file changed, 14 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
> index ffd65eddce42..a180f541736a 100644
> --- a/drivers/gpu/drm/drm_connector.c
> +++ b/drivers/gpu/drm/drm_connector.c
> @@ -1446,6 +1446,20 @@ static const struct drm_prop_enum_list dp_colorspaces[] = {
> * a firmware handled hotkey. Therefor userspace must not include the
> * privacy-screen sw-state in an atomic commit unless it wants to change
> * its value.
> + *
> + * left margin, right margin, top margin, bottom margin:
> + * Add margins to the connector's viewport. This is typically used to
> + * mitigate underscan on TVs.
"used to mitigate overscan" or "used to underscan" would make
more sense to me.
> + *
> + * The value is the size in pixels of the black border which will be
> + * added. The attached CRTC's content will be scaled to fill the whole
> + * area inside the margin.
Dunno if there should be something even more explicit here
about the CRTCs viewport/canvas/<whatever you call it> size
remaining unchaned, ie. still 'hdisplay x vdisplay'?
Another very open question is how these would interact with
the 'scaling mode' property/connectors that already scale
the passed in mode to whatever fixed size the panel needs.
In my i915 patches I totally sidestepped that question by
not registering the margin properties for eDP at all.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-02-28 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 12:32 [PATCH v2] drm: document connector margin properties Simon Ser
2023-02-28 12:44 ` Ville Syrjälä [this message]
2023-02-28 12:45 ` Pekka Paalanen
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=Y/33RipzQtGhPJCg@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=kfyatek+publicgit@gmail.com \
--cc=maxime@cerno.tech \
--cc=noralf@tronnes.org \
--cc=ppaalanen@gmail.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