From: Neil Armstrong <narmstrong@baylibre.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Robert Foss <robert.foss@linaro.org>,
Sam Ravnborg <sam@ravnborg.org>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@googlegroups.com, linux-amarula@amarulasolutions.com
Subject: Re: [PATCH v5 3/7] drm: sun4i: dsi: Convert to bridge driver
Date: Mon, 22 Nov 2021 16:35:40 +0100 [thread overview]
Message-ID: <9aa3d19d-4378-aaf3-6857-c40be5d252c7@baylibre.com> (raw)
In-Reply-To: <CAMty3ZDATTKoJq7aLOe5i=RPo2UHzqnLs8j8sT-EBNdpC7=3DQ@mail.gmail.com>
Hi,
On 22/11/2021 14:16, Jagan Teki wrote:
> Hi Neil,
>
> On Mon, Nov 22, 2021 at 6:22 PM Neil Armstrong <narmstrong@baylibre.com> wrote:
>>
>> On 22/11/2021 07:52, Jagan Teki wrote:
>>> Some display panels would come up with a non-DSI output, those
>>> can have an option to connect the DSI host by means of interface
>>> bridge converter.
>>>
>>> This DSI to non-DSI interface bridge converter would requires
>>> DSI Host to handle drm bridge functionalities in order to DSI
>>> Host to Interface bridge.
>>>
>>> This patch convert the existing to a drm bridge driver with a
>>> built-in encoder support for compatibility with existing
>>> component drivers.
>>>
>>> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
>>> ---
>>> Changes for v5:
>>> - add atomic APIs
>>> - find host and device variant DSI devices.
>>> Changes for v4, v3:
>>> - none
>>>
>>> drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c | 112 ++++++++++++++++++++-----
>>> drivers/gpu/drm/sun4i/sun6i_mipi_dsi.h | 7 ++
>>> 2 files changed, 96 insertions(+), 23 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c b/drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c
>>> index 43d9c9e5198d..a6a272b55f77 100644
>>> --- a/drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c
>>> +++ b/drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c
>>> @@ -21,6 +21,7 @@
>>>
>>> #include <drm/drm_atomic_helper.h>
>>> #include <drm/drm_mipi_dsi.h>
>>> +#include <drm/drm_of.h>
>>> #include <drm/drm_panel.h>
>>> #include <drm/drm_print.h>
>>> #include <drm/drm_probe_helper.h>
>>> @@ -713,10 +714,11 @@ static int sun6i_dsi_start(struct sun6i_dsi *dsi,
>>> return 0;
>>> }
>>>
>>> -static void sun6i_dsi_encoder_enable(struct drm_encoder *encoder)
>>> +static void sun6i_dsi_bridge_atomic_enable(struct drm_bridge *bridge,
>>> + struct drm_bridge_state *old_bridge_state)
>>> {
>>> - struct drm_display_mode *mode = &encoder->crtc->state->adjusted_mode;
>>> - struct sun6i_dsi *dsi = encoder_to_sun6i_dsi(encoder);
>>> + struct sun6i_dsi *dsi = bridge_to_sun6i_dsi(bridge);
>>> + struct drm_display_mode *mode = &bridge->encoder->crtc->state->adjusted_mode;
>>> struct mipi_dsi_device *device = dsi->device;
>>> union phy_configure_opts opts = { };
>>> struct phy_configure_opts_mipi_dphy *cfg = &opts.mipi_dphy;
>>> @@ -772,6 +774,9 @@ static void sun6i_dsi_encoder_enable(struct drm_encoder *encoder)
>>> if (dsi->panel)
>>> drm_panel_prepare(dsi->panel);
>>>
>>> + if (dsi->next_bridge)
>>> + dsi->next_bridge->funcs->atomic_pre_enable(dsi->next_bridge, old_bridge_state);
>>> +
>>> /*
>>> * FIXME: This should be moved after the switch to HS mode.
>>> *
>>> @@ -787,6 +792,9 @@ static void sun6i_dsi_encoder_enable(struct drm_encoder *encoder)
>>> if (dsi->panel)
>>> drm_panel_enable(dsi->panel);
>>>
>>> + if (dsi->next_bridge)
>>> + dsi->next_bridge->funcs->atomic_enable(dsi->next_bridge, old_bridge_state);
>>> +
>>
>>
>> No need to call the next bridge atomic pre_enable/enable/disable/post_disable since they will
>> be called automatically on the bridge chain.
>
> Correct, but the existing bridge chain (stack) is not compatible with
> sun6i DSI start sequence. We cannot send any DCS once we start HS
> mode.
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/gpu/drm/sun4i/sun6i_mipi_dsi.c#n775
It's a classical DSI sequence init issue, look at dw-mipi-dsi:
https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c
We setup the "command-mode" (low-speed) withing mode_set so when the next bridge dsi_pre_enable is called,
low-speed DCS can be sent, then the bridge enable() sets video mode (high-speed).
The disable still needs to call the next_bridge post_disable :
https://elixir.bootlin.com/linux/v5.16-rc2/source/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c#L893
You can send any low-speed DCS once HS mode is started if the HW supports it and the driver handles it, look
at the https://elixir.bootlin.com/linux/v5.16-rc2/source/drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c#L397
The MIPI_DSI_MODE_LPM and MIPI_DSI_MSG_USE_LPM is used for that.
Neil
>
> This specific problem can be fixed only if we change the bridge chain
> from stack to queue. Please check this series
> https://patchwork.kernel.org/project/dri-devel/patch/20210214194102.126146-6-jagan@amarulasolutions.com/
>
> Jagan.
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-11-22 15:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 6:52 [PATCH v5 0/7] drm: sun4i: dsi: Convert drm bridge Jagan Teki
2021-11-22 6:52 ` [PATCH v5 1/7] drm: sun4i: dsi: Drop DRM bind race with bridge attach Jagan Teki
2021-11-22 6:52 ` [PATCH v5 2/7] drm: sun4i: dsi: Add component only once DSI device attached Jagan Teki
2021-11-22 6:52 ` [PATCH v5 3/7] drm: sun4i: dsi: Convert to bridge driver Jagan Teki
2021-11-22 10:07 ` Maxime Ripard
2021-11-22 12:45 ` Laurent Pinchart
2021-11-22 13:48 ` Jagan Teki
2021-11-22 14:04 ` Maxime Ripard
2021-11-22 14:19 ` Jagan Teki
2021-11-22 15:04 ` Maxime Ripard
2021-11-25 16:17 ` Jagan Teki
2021-11-23 18:32 ` Jagan Teki
2021-11-25 14:15 ` Maxime Ripard
2021-11-25 14:25 ` Jagan Teki
2021-11-25 16:10 ` Maxime Ripard
2021-11-25 16:14 ` Jagan Teki
2021-11-26 16:04 ` Maxime Ripard
2021-11-30 7:39 ` Jagan Teki
2021-12-05 17:39 ` Michael Nazzareno Trimarchi
2021-11-22 12:52 ` Neil Armstrong
2021-11-22 13:16 ` Jagan Teki
2021-11-22 15:35 ` Neil Armstrong [this message]
2021-11-22 17:19 ` Dave Stevenson
2021-11-23 8:19 ` Neil Armstrong
2021-11-22 6:52 ` [PATCH v5 4/7] drm: sun4i: dsi: Add mode_set function Jagan Teki
2021-11-22 10:07 ` Maxime Ripard
2021-11-22 13:05 ` Jagan Teki
2021-11-22 13:28 ` Maxime Ripard
2021-11-22 13:51 ` Jagan Teki
2021-11-22 14:09 ` Maxime Ripard
2021-11-22 14:31 ` Jagan Teki
2021-11-22 15:06 ` Maxime Ripard
2021-11-22 15:17 ` Jagan Teki
2021-11-22 6:52 ` [DO NOT MERGE] [PATCH v5 5/7] ARM: dts: sun8i: bananapi-m2m: Enable S070WV20-CT16 Panel Jagan Teki
2021-11-22 6:52 ` [DO NOT MERGE] [PATCH v5 6/7] ARM: dts: sun8i: bananapi-m2m: Enable ICN6211 DSI Bridge Jagan Teki
2021-11-22 6:52 ` [DO NOT MERGE] [PATCH v5 7/7] ARM: dts: sun8i: Enable DLPC3433 Bridge (I2C) Jagan Teki
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=9aa3d19d-4378-aaf3-6857-c40be5d252c7@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jagan@amarulasolutions.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mripard@kernel.org \
--cc=robert.foss@linaro.org \
--cc=sam@ravnborg.org \
--cc=wens@csie.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).