From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] drm/pl111: Replace custom connector with panel bridge
Date: Thu, 31 Aug 2017 10:38:20 -0700 [thread overview]
Message-ID: <87h8wnzlgz.fsf@anholt.net> (raw)
In-Reply-To: <20170830180711.2791-4-linus.walleij@linaro.org>
Linus Walleij <linus.walleij@linaro.org> writes:
> This replaces the custom connector in the PL111 with the
> panel bridge helper.
>
> This works nicely for all standard panels, but since there
> are several PL11x-based systems that will need to use the dumb
> VGA connector bridge we use drm_of_find_panel_or_bridge()
> and make some headroom for dealing with bridges that are
> not panels as well, and drop a TODO in the code.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> diff --git a/drivers/gpu/drm/pl111/pl111_display.c b/drivers/gpu/drm/pl111/pl111_display.c
> index c6ca4f1bbd49..ef86ef60aed1 100644
> --- a/drivers/gpu/drm/pl111/pl111_display.c
> +++ b/drivers/gpu/drm/pl111/pl111_display.c
> @@ -93,7 +93,7 @@ static void pl111_display_enable(struct drm_simple_display_pipe *pipe,
> struct pl111_drm_dev_private *priv = drm->dev_private;
> const struct drm_display_mode *mode = &cstate->mode;
> struct drm_framebuffer *fb = plane->state->fb;
> - struct drm_connector *connector = &priv->connector.connector;
> + struct drm_connector *connector = priv->connector;
> u32 cntl;
> u32 ppl, hsw, hfp, hbp;
> u32 lpp, vsw, vfp, vbp;
> @@ -155,7 +155,7 @@ static void pl111_display_enable(struct drm_simple_display_pipe *pipe,
>
> writel(0, priv->regs + CLCD_TIM3);
>
> - drm_panel_prepare(priv->connector.panel);
> + drm_panel_prepare(priv->panel);
If we're moving to panel-bridge, then we should drop our manual panel
prepare/enable/disable calls -- the panel-bridge will have already
panel_prepare()d before our encoder's enable, and will panel_enable()
after we finish.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170831/a301ad01/attachment.sig>
next prev parent reply other threads:[~2017-08-31 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 18:07 [PATCH 0/7] First set of PL111 enhancements Linus Walleij
2017-08-30 18:07 ` [PATCH 1/7] drm/pl111: Cleanup local header file Linus Walleij
2017-08-30 18:07 ` [PATCH 2/7] drm/pl111: Add all registers to debugfs Linus Walleij
2017-08-31 17:40 ` Eric Anholt
2017-08-30 18:07 ` [PATCH 3/7] drm/pl111: Replace custom connector with panel bridge Linus Walleij
2017-08-31 17:38 ` Eric Anholt [this message]
2017-08-30 18:07 ` [PATCH 4/7] drm/pl111: Enable PL110 variant Linus Walleij
2017-08-31 10:19 ` Eric Engestrom
2017-09-01 8:23 ` Emil Velikov
2017-09-01 9:22 ` Linus Walleij
2017-08-31 17:46 ` Eric Anholt
2017-08-30 18:07 ` [PATCH 5/7] drm/pl111: Insert delay before powering up PL11x Linus Walleij
2017-08-30 18:07 ` [PATCH 6/7] drm/pl111: Add optional variant display en/disable callbacks Linus Walleij
2017-08-30 18:07 ` [PATCH 7/7] drm/pl111: Add handling of Versatile platforms Linus Walleij
2017-08-31 17:58 ` Eric Anholt
2017-09-01 9:27 ` Linus Walleij
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=87h8wnzlgz.fsf@anholt.net \
--to=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).