From: Daniel Vetter <daniel@ffwll.ch>
To: Eric Anholt <eric@anholt.net>
Cc: nouveau@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
"Boris Brezillon" <boris.brezillon@bootlin.com>,
dri-devel@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Ben Skeggs" <bskeggs@redhat.com>
Subject: Re: [PATCH v3 1/3] drm/connector: Add generic underscan properties
Date: Tue, 4 Dec 2018 11:42:31 +0100 [thread overview]
Message-ID: <20181204104231.GA21184@phenom.ffwll.local> (raw)
In-Reply-To: <87k1kqfw2q.fsf@anholt.net>
On Mon, Dec 03, 2018 at 07:50:53AM -0800, Eric Anholt wrote:
> Boris Brezillon <boris.brezillon@bootlin.com> writes:
>
> > On Mon, 3 Dec 2018 16:40:11 +0200
> > Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> >
> >> On Thu, Nov 22, 2018 at 12:23:29PM +0100, Boris Brezillon wrote:
> >> > @@ -924,6 +978,29 @@ struct drm_connector {
> >> > */
> >> > struct drm_property_blob *path_blob_ptr;
> >> >
> >> > + /**
> >> > + * @underscan_mode_property: Optional connector underscan mode. Used by
> >> > + * the driver to scale the output image and compensate an overscan done
> >> > + * on the display side.
> >> > + */
> >> > + struct drm_property *underscan_mode_property;
> >> > +
> >> > + /**
> >> > + * @underscan_hborder_property: Optional connector underscan horizontal
> >> > + * border (expressed in pixels). Used by the driver to adjust the
> >> > + * output image position and compensate an overscan done on the display
> >> > + * side.
> >> > + */
> >> > + struct drm_property *underscan_hborder_property;
> >> > +
> >> > + /**
> >> > + * @underscan_hborder_property: Optional connector underscan vertical
> >> > + * border (expressed in pixels). Used by the driver to adjust the
> >> > + * output image position and compensate an overscan done on the display
> >> > + * side.
> >> > + */
> >> > + struct drm_property *underscan_vborder_property;
> >>
> >> I'm wondering why we're adding these new props when we already have the
> >> (slightly more flexible) margin properties for TV out. We could just
> >> reuse those AFAICS.
> >
> > I'm not against the idea, but I can't use
> > drm_mode_create_tv_properties() directly, as most props created by this
> > function are not applicable to an HDMI displays. Should I move the
> > margins props out of the tv_connector_state and provide new helpers to
> > create those props?
>
> TV margin props look good to me, FWIW.
Yeah extracting the margin props from the tv props sounds like a good
idea. If we go full ocd we'd also split out margin_connector_state or
something like that (should be doable with some cocci), but not sure
that's fully worth it. Tuning margins is largely an analog TV issue I
think, so could just leave them there.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-12-04 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 11:23 [PATCH v3 0/3] drm/connector: Provide generic support for underscan Boris Brezillon
2018-11-22 11:23 ` [PATCH v3 1/3] drm/connector: Add generic underscan properties Boris Brezillon
[not found] ` <20181122112331.17735-2-boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2018-11-22 17:36 ` Brian Starkey
2018-11-28 17:17 ` Eric Anholt
2018-12-03 14:40 ` Ville Syrjälä
2018-12-03 15:36 ` Boris Brezillon
2018-12-03 15:50 ` Eric Anholt
2018-12-04 10:42 ` Daniel Vetter [this message]
[not found] ` <20181122112331.17735-1-boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2018-11-22 11:23 ` [PATCH v3 2/3] drm/vc4: Take underscan setup into account when updating planes Boris Brezillon
2018-11-22 11:23 ` [PATCH v3 3/3] drm/vc4: Attach underscan props to the HDMI connector Boris Brezillon
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=20181204104231.GA21184@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=boris.brezillon@bootlin.com \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=nouveau@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