From: Boris Brezillon <boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
To: "Ville Syrjälä" <ville.syrjala-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: "David Airlie" <airlied-cv59FeDIM0c@public.gmane.org>,
nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
"Daniel Vetter" <daniel-/w4YWyX8dFk@public.gmane.org>,
"Alex Deucher" <alexander.deucher-5C7GfCeVMHo@public.gmane.org>,
"Christian König" <christian.koenig-5C7GfCeVMHo@public.gmane.org>,
"Ben Skeggs" <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v2 2/4] drm/vc4: Take underscan setup into account when updating planes
Date: Fri, 11 May 2018 17:52:56 +0200 [thread overview]
Message-ID: <20180511175256.53a3966a@bbrezillon> (raw)
In-Reply-To: <20180511153450.GS23723-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
On Fri, 11 May 2018 18:34:50 +0300
Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Fri, May 11, 2018 at 04:59:17PM +0200, Boris Brezillon wrote:
> > Applying an underscan setup is just a matter of scaling all planes
> > appropriately and adjusting the CRTC X/Y offset to account for the
> > horizontal and vertical border.
> >
> > Create an vc4_plane_underscan_adj() function doing that and call it from
> > vc4_plane_setup_clipping_and_scaling() so that we are ready to attach
> > underscan properties to the HDMI connector.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> > ---
> > Changes in v2:
> > - Take changes on hborder/vborder meaning into account
> > ---
> > drivers/gpu/drm/vc4/vc4_plane.c | 49 ++++++++++++++++++++++++++++++++++++++++-
> > 1 file changed, 48 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/vc4/vc4_plane.c b/drivers/gpu/drm/vc4/vc4_plane.c
> > index 71d44c357d35..61ed60841cd6 100644
> > --- a/drivers/gpu/drm/vc4/vc4_plane.c
> > +++ b/drivers/gpu/drm/vc4/vc4_plane.c
> > @@ -258,6 +258,49 @@ static u32 vc4_get_scl_field(struct drm_plane_state *state, int plane)
> > }
> > }
> >
> > +static int vc4_plane_underscan_adj(struct drm_plane_state *pstate)
> > +{
> > + struct vc4_plane_state *vc4_pstate = to_vc4_plane_state(pstate);
> > + struct drm_connector_state *conn_state = NULL;
> > + struct drm_connector *conn;
> > + struct drm_crtc_state *crtc_state;
> > + int i;
> > +
> > + for_each_new_connector_in_state(pstate->state, conn, conn_state, i) {
> > + if (conn_state->crtc == pstate->crtc)
> > + break;
> > + }
> > +
> > + if (i == pstate->state->num_connector)
> > + return 0;
> > +
> > + if (conn_state->underscan.mode != DRM_UNDERSCAN_ON)
> > + return 0;
> > +
> > + crtc_state = drm_atomic_get_new_crtc_state(pstate->state,
> > + pstate->crtc);
> > +
> > + if (conn_state->underscan.hborder >= crtc_state->mode.hdisplay ||
> > + conn_state->underscan.vborder >= crtc_state->mode.vdisplay)
> > + return -EINVAL;
>
> border * 2 ?
Oops, indeed. I'll fix that.
>
> > +
> > + vc4_pstate->crtc_x += conn_state->underscan.hborder;
> > + vc4_pstate->crtc_y += conn_state->underscan.vborder;
> > + vc4_pstate->crtc_w = (vc4_pstate->crtc_w *
> > + (crtc_state->mode.hdisplay -
> > + (conn_state->underscan.hborder * 2))) /
> > + crtc_state->mode.hdisplay;
> > + vc4_pstate->crtc_h = (vc4_pstate->crtc_h *
> > + (crtc_state->mode.vdisplay -
> > + (conn_state->underscan.vborder * 2))) /
> > + crtc_state->mode.vdisplay;
>
> So you're now scaling all planes? The code seems to reject scaling for
> the cursor plane, how are you dealing with that? Or just no cursor
> allowed when underscanning?
No, I just didn't test with a cursor plane. We should probably avoid
scaling the cursor plane and just adjust its position. Eric any opinion
on that?
>
> I'm also wondering if there's any way we can reconcile these border
> props with the scaling mode prop, should we ever wish to expose
> these props on connectors that already have the scaling mode prop.
Nouveau seems to expose both, and I don't see why we couldn't.
> Maybe we just have to require the scaling mode to be set to fullscreen
> to allow borders to be specified explictly?
>
> > +
> > + if (!vc4_pstate->crtc_w || !vc4_pstate->crtc_h)
> > + return -EINVAL;
> > +
> > + return 0;
> > +}
> > +
> > static int vc4_plane_setup_clipping_and_scaling(struct drm_plane_state *state)
> > {
> > struct drm_plane *plane = state->plane;
> > @@ -269,7 +312,7 @@ static int vc4_plane_setup_clipping_and_scaling(struct drm_plane_state *state)
> > int num_planes = fb->format->num_planes;
> > u32 h_subsample = 1;
> > u32 v_subsample = 1;
> > - int i;
> > + int i, ret;
> >
> > for (i = 0; i < num_planes; i++)
> > vc4_state->offsets[i] = bo->paddr + fb->offsets[i];
> > @@ -292,6 +335,10 @@ static int vc4_plane_setup_clipping_and_scaling(struct drm_plane_state *state)
> > vc4_state->crtc_w = state->crtc_w;
> > vc4_state->crtc_h = state->crtc_h;
> >
> > + ret = vc4_plane_underscan_adj(state);
> > + if (ret)
> > + return ret;
> > +
> > vc4_state->x_scaling[0] = vc4_get_scaling_mode(vc4_state->src_w[0],
> > vc4_state->crtc_w);
> > vc4_state->y_scaling[0] = vc4_get_scaling_mode(vc4_state->src_h[0],
> > --
> > 2.14.1
> >
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-05-11 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 14:59 [PATCH v2 0/4] drm/connector: Provide generic support for underscan Boris Brezillon
[not found] ` <20180511145919.22447-1-boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2018-05-11 14:59 ` [PATCH v2 1/4] drm/connector: Add generic underscan properties Boris Brezillon
2018-05-11 14:59 ` [PATCH v2 2/4] drm/vc4: Take underscan setup into account when updating planes Boris Brezillon
[not found] ` <20180511145919.22447-3-boris.brezillon-LDxbnhwyfcJBDgjK7y7TUQ@public.gmane.org>
2018-05-11 15:34 ` Ville Syrjälä
[not found] ` <20180511153450.GS23723-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-05-11 15:52 ` Boris Brezillon [this message]
2018-05-11 16:54 ` Ville Syrjälä
[not found] ` <20180511165402.GU23723-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-05-11 17:12 ` Boris Brezillon
2018-05-11 17:29 ` Ville Syrjälä
[not found] ` <20180511172948.GV23723-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-05-11 19:47 ` Boris Brezillon
2018-05-11 20:46 ` Ville Syrjälä
[not found] ` <20180511204643.GW23723-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2018-05-14 7:05 ` Eric Anholt
2018-05-11 20:11 ` Eric Anholt
2018-05-11 14:59 ` [PATCH v2 4/4] drm/nouveau: Switch to the generic underscan props Boris Brezillon
2018-05-11 14:59 ` [PATCH v2 3/4] 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=20180511175256.53a3966a@bbrezillon \
--to=boris.brezillon-ldxbnhwyfcjbdgjk7y7tuq@public.gmane.org \
--cc=airlied-cv59FeDIM0c@public.gmane.org \
--cc=alexander.deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@public.gmane.org \
--cc=daniel-/w4YWyX8dFk@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=ville.syrjala-VuQAYsv1563Yd54FQh9/CA@public.gmane.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