From: Philipp Zabel <p.zabel@pengutronix.de>
To: Boris Brezillon <boris.brezillon@collabora.com>,
dri-devel@lists.freedesktop.org
Cc: Lucas Stach <l.stach@pengutronix.de>,
Chris Healy <cphealy@gmail.com>,
Andrey Smirnov <andrew.smirnov@gmail.com>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
kernel@collabora.com, Daniel Vetter <daniel@ffwll.ch>,
Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
intel-gfx-trybot@lists.freedesktop.org
Subject: Re: [PATCH v9 07/12] drm/imx: pd: Use bus format/flags provided by the bridge when available
Date: Mon, 27 Jan 2020 13:57:11 +0100 [thread overview]
Message-ID: <ea2957045774ff714a0cb5cd4fb91660d761ec1e.camel@pengutronix.de> (raw)
In-Reply-To: <20200127110043.2731697-8-boris.brezillon@collabora.com>
Hi Boris,
On Mon, 2020-01-27 at 12:00 +0100, Boris Brezillon wrote:
> Now that bridges can expose the bus format/flags they expect, we can
> use those instead of the relying on the display_info provided by the
> connector (which is only valid if the encoder is directly connected
> to bridge element driving the panel/display).
>
> We also explicitly expose the bus formats supported by our encoder by
> filling encoder->output_bus_caps with proper info.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> ---
> Changes in v7:
> * Add an imx_pd_format_supported() helper (suggested by Philipp)
> * Simplify imx_pd_bridge_atomic_get_output_bus_fmts() (suggested by Philipp)
> * Simplify imx_pd_bridge_atomic_get_input_bus_fmts()
> * Explicitly set the duplicate/destro_state() and reset() hooks
>
> Changes in v3 (all suggested by Philipp):
> * Adjust to match core changes
> * Propagate output format to input format
> * Pick a default value when output_fmt = _FIXED
> * Add missing BGR888 and GBR888 fmts to imx_pd_bus_fmts[]
>
> Changes in v2:
> * Adjust things to match the new bus-format negotiation infra
> ---
> drivers/gpu/drm/imx/parallel-display.c | 176 +++++++++++++++++++++----
> 1 file changed, 151 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/gpu/drm/imx/parallel-display.c b/drivers/gpu/drm/imx/parallel-display.c
> index 3dca424059f7..031579aa7fc2 100644
> --- a/drivers/gpu/drm/imx/parallel-display.c
> +++ b/drivers/gpu/drm/imx/parallel-display.c
> @@ -24,6 +24,7 @@
[...]
> +static u32 *
> +imx_pd_bridge_atomic_get_input_bus_fmts(struct drm_bridge *bridge,
> + struct drm_bridge_state *bridge_state,
> + struct drm_crtc_state *crtc_state,
> + struct drm_connector_state *conn_state,
> + u32 output_fmt,
> + unsigned int *num_input_fmts)
> +{
> + struct imx_parallel_display *imxpd = bridge_to_imxpd(bridge);
> + u32 *input_fmts;
> +
> + /*
> + * If the next bridge does not support bus format negotiation, let's
> + * use the static bus format definition (imxpd->bus_format) if it's
> + * specified, RGB888 when it's not.
> + */
> + if (output_fmt == MEDIA_BUS_FMT_FIXED)
> + output_fmt = imxpd->bus_format ? : MEDIA_BUS_FMT_RGB888_1X24;
> +
> + /* Now make sure the requested output format is supported. */
> + if ((imxpd->bus_format && imxpd->bus_format != output_fmt) ||
> + !imx_pd_format_supported(output_fmt)) {
> + *num_input_fmts = 0;
> + return NULL;
> + }
> +
> + *num_input_fmts = 1;
> + input_fmts = kcalloc(*num_input_fmts, sizeof(*input_fmts),
> + GFP_KERNEL);
You could just use kzalloc() here.
> + if (!input_fmts)
> + return NULL;
> +
> + input_fmts[0] = output_fmt;
> + return input_fmts;
> +}
> +
> +static int imx_pd_bridge_atomic_check(struct drm_bridge *bridge,
> + struct drm_bridge_state *bridge_state,
> + struct drm_crtc_state *crtc_state,
> + struct drm_connector_state *conn_state)
> +{
> + struct imx_crtc_state *imx_crtc_state = to_imx_crtc_state(crtc_state);
> + struct drm_display_info *di = &conn_state->connector->display_info;
> + struct imx_parallel_display *imxpd = bridge_to_imxpd(bridge);
> + struct drm_bridge_state *next_bridge_state = NULL;
> + struct drm_bridge *next_bridge;
> + u32 bus_flags, bus_fmt;
> +
> + next_bridge = drm_bridge_get_next_bridge(bridge);
> + if (next_bridge)
> + next_bridge_state = drm_atomic_get_new_bridge_state(crtc_state->state,
> + next_bridge);
> +
> + if (next_bridge_state)
> + bus_flags = next_bridge_state->input_bus_cfg.flags;
> + else if (!imxpd->bus_format && di->num_bus_formats)
> + bus_flags = di->bus_flags;
> + else
> + bus_flags = imxpd->bus_flags;
> +
> + bus_fmt = bridge_state->input_bus_cfg.format;
> + if (!imx_pd_format_supported(bus_fmt))
> + return -EINVAL;
> +
> + if (bus_flags &
> + ~(DRM_BUS_FLAG_DE_LOW | DRM_BUS_FLAG_DE_HIGH |
> + DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE |
> + DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE))
Maybe add a warning so the first person to hook up a bridge / panel with
unsupported flags knows where to look.
Otherwise this looks fine to me.
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
next prev parent reply other threads:[~2020-01-27 12:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 11:00 [PATCH v9 00/12] drm: Add support for bus-format negotiation Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 01/12] drm/bridge: Add a drm_bridge_state object Boris Brezillon
2020-01-27 17:26 ` Daniel Vetter
2020-01-27 17:49 ` Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 02/12] drm/rcar-du: Plug atomic state hooks to the default implementation Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 03/12] drm/bridge: analogix: " Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 04/12] drm/bridge: Patch atomic hooks to take a drm_bridge_state Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 05/12] drm/bridge: Add an ->atomic_check() hook Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 06/12] drm/bridge: Add the necessary bits to support bus format negotiation Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 07/12] drm/imx: pd: Use bus format/flags provided by the bridge when available Boris Brezillon
2020-01-27 12:57 ` Philipp Zabel [this message]
2020-01-27 11:00 ` [PATCH v9 08/12] drm/bridge: lvds-codec: Implement basic bus format negotiation Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 09/12] dt-bindings: display: bridge: lvds-codec: Add new bus-width prop Boris Brezillon
2020-01-27 15:39 ` Rob Herring
2020-01-27 11:00 ` [PATCH v9 10/12] drm/bridge: panel: Propage bus format/flags Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 11/12] drm/panel: simple: Fix the lt089ac29000 bus_format Boris Brezillon
2020-01-27 11:00 ` [PATCH v9 12/12] ARM: dts: imx: imx51-zii-rdu1: Fix the display pipeline definition 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=ea2957045774ff714a0cb5cd4fb91660d761ec1e.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=andrew.smirnov@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=cphealy@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx-trybot@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=l.stach@pengutronix.de \
--cc=mark.rutland@arm.com \
--cc=narmstrong@baylibre.com \
--cc=nikita.yoush@cogentembedded.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).