From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Frieder Schrempf <frieder@fris.de>,
Jagan Teki <jagan@amarulasolutions.com>,
Adam Ford <aford173@gmail.com>,
Tim Harvey <tharvey@gateworks.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org, Inki Dae <inki.dae@samsung.com>,
linux-kernel@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>, Marek Vasut <marex@denx.de>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Jonas Karlman <jonas@kwiboo.se>
Subject: Re: [PATCH v2 1/2] drm: bridge: samsung-dsim: Fix i.MX8M enable flow to meet spec
Date: Thu, 13 Jul 2023 08:22:03 +0200 [thread overview]
Message-ID: <15446320.O9o76ZdvQC@steina-w> (raw)
In-Reply-To: <CAJ+vNU2d969V1kTHpH+tPK1fm=Z2DUdKSOjwyzRO=9j43HhKgg@mail.gmail.com>
Hi,
Am Donnerstag, 13. Juli 2023, 00:34:47 CEST schrieb Tim Harvey:
> On Wed, May 3, 2023 at 9:33 AM Frieder Schrempf <frieder@fris.de> wrote:
> > From: Frieder Schrempf <frieder.schrempf@kontron.de>
> >
> > According to the documentation [1] the proper enable flow is:
> >
> > 1. Enable DSI link and keep data lanes in LP-11 (stop state)
> > 2. Disable stop state to bring data lanes into HS mode
> >
> > Currently we do this all at once within enable(), which doesn't
> > allow to meet the requirements of some downstream bridges.
> >
> > To fix this we now enable the DSI in pre_enable() and force it
> > into stop state using the FORCE_STOP_STATE bit in the ESCMODE
> > register until enable() is called where we reset the bit.
> >
> > We currently do this only for i.MX8M as Exynos uses a different
> > init flow where samsung_dsim_init() is called from
> > samsung_dsim_host_transfer().
> >
> > [1]
> > https://docs.kernel.org/gpu/drm-kms-helpers.html#mipi-dsi-bridge-operatio
> > n
> >
> > Signed-off-by: Frieder Schrempf <frieder.schrempf@kontron.de>
> > ---
> > Changes for v2:
> > * Drop RFC
> > ---
> >
> > drivers/gpu/drm/bridge/samsung-dsim.c | 25 +++++++++++++++++++++++--
> > 1 file changed, 23 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/bridge/samsung-dsim.c
> > b/drivers/gpu/drm/bridge/samsung-dsim.c index e0a402a85787..9775779721d9
> > 100644
> > --- a/drivers/gpu/drm/bridge/samsung-dsim.c
> > +++ b/drivers/gpu/drm/bridge/samsung-dsim.c
> > @@ -859,6 +859,10 @@ static int samsung_dsim_init_link(struct samsung_dsim
> > *dsi)>
> > reg = samsung_dsim_read(dsi, DSIM_ESCMODE_REG);
> > reg &= ~DSIM_STOP_STATE_CNT_MASK;
> > reg |=
> > DSIM_STOP_STATE_CNT(driver_data->reg_values[STOP_STATE_CNT]);
> >
> > +
> > + if (!samsung_dsim_hw_is_exynos(dsi->plat_data->hw_type))
> > + reg |= DSIM_FORCE_STOP_STATE;
> > +
> >
> > samsung_dsim_write(dsi, DSIM_ESCMODE_REG, reg);
> >
> > reg = DSIM_BTA_TIMEOUT(0xff) | DSIM_LPDR_TIMEOUT(0xffff);
> >
> > @@ -1340,6 +1344,9 @@ static void samsung_dsim_atomic_pre_enable(struct
> > drm_bridge *bridge,>
> > ret = samsung_dsim_init(dsi);
> > if (ret)
> >
> > return;
> >
> > +
> > + samsung_dsim_set_display_mode(dsi);
> > + samsung_dsim_set_display_enable(dsi, true);
> >
> > }
> >
> > }
> >
> > @@ -1347,9 +1354,16 @@ static void samsung_dsim_atomic_enable(struct
> > drm_bridge *bridge,>
> > struct drm_bridge_state
> > *old_bridge_state)
> >
> > {
> >
> > struct samsung_dsim *dsi = bridge_to_dsi(bridge);
> >
> > + u32 reg;
> >
> > - samsung_dsim_set_display_mode(dsi);
> > - samsung_dsim_set_display_enable(dsi, true);
> > + if (samsung_dsim_hw_is_exynos(dsi->plat_data->hw_type)) {
> > + samsung_dsim_set_display_mode(dsi);
> > + samsung_dsim_set_display_enable(dsi, true);
> > + } else {
> > + reg = samsung_dsim_read(dsi, DSIM_ESCMODE_REG);
> > + reg &= ~DSIM_FORCE_STOP_STATE;
> > + samsung_dsim_write(dsi, DSIM_ESCMODE_REG, reg);
> > + }
> >
> > dsi->state |= DSIM_STATE_VIDOUT_AVAILABLE;
> >
> > }
> >
> > @@ -1358,10 +1372,17 @@ static void samsung_dsim_atomic_disable(struct
> > drm_bridge *bridge,>
> > struct drm_bridge_state
> > *old_bridge_state)
> >
> > {
> >
> > struct samsung_dsim *dsi = bridge_to_dsi(bridge);
> >
> > + u32 reg;
> >
> > if (!(dsi->state & DSIM_STATE_ENABLED))
> >
> > return;
> >
> > + if (!samsung_dsim_hw_is_exynos(dsi->plat_data->hw_type)) {
> > + reg = samsung_dsim_read(dsi, DSIM_ESCMODE_REG);
> > + reg |= DSIM_FORCE_STOP_STATE;
> > + samsung_dsim_write(dsi, DSIM_ESCMODE_REG, reg);
> > + }
> > +
> >
> > dsi->state &= ~DSIM_STATE_VIDOUT_AVAILABLE;
> >
> > }
> >
> > --
> > 2.40.0
>
> Hi Frieder,
>
> I found this patch to break mipi-dsi display on my board which has:
> - FocalTech FT5406 10pt touch controller (with no interrupt)
> - Powertip PH800480T013-IDF02 compatible panel
> - Toshiba TC358762 compatible DSI to DBI bridge
> - ATTINY based regulator used for backlight controller and panel enable
>
> I enable this via a dt overlay in a pending patch
> imx8mm-venice-gw72xx-0x-rpidsi.dtso [1] which works on 6.4 but not
> 6.5-rc1 which has this patch.
>
> The issue appears as:
> [ 6.110585] samsung-dsim 32e60000.dsi: xfer timed out: 29 06 00 00
> 64 01 05 00 00 00
> [ 6.326588] tc358762 32e60000.dsi.0: error initializing bridge (-110)
>
> Instead of
> [ 1.011729] samsung-dsim 32e10000.dsi: supply vddcore not found,
> using dummy regulator
> [ 1.019829] samsung-dsim 32e10000.dsi: supply vddio not found,
> using dummy regulator
> [ 5.649928] samsung-dsim 32e10000.dsi:
> [drm:samsung_dsim_host_attach] Attached tc358762 device
>
> I'm curious what board/panel were you needing this for and do you have
> any ideas why it broke my setup?
>
> I'm also curious what board/panel Alexander tested this with and if
> Adam or Jagan (or others) have tested this with their hardware?
I tested this with imx8mm and ti,sn65dsi83 DSI-LVDS bridge [1]. I don't know
anything about tc358762, but I was trying to get tc9595 (DSI-DP bridge)
running on a imx8mp based board. One of my problems was that the bridge
requires LP-11 before reset release, which is currently not given using
samsung-dsim and tc358767 driver. Maybe this is the case for you as well.
AFAICS there is a lot more to do to get this running properly.
Best regards,
Alexander
[1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/
arch/arm64/boot/dts/freescale/imx8mp-tqma8mpql-mba8mpxl-lvds.dtso
> best regards,
>
> Tim
> [1]
> https://patchwork.kernel.org/project/linux-arm-kernel/patch/20230711221124.
> 2127186-1-tharvey@gateworks.com/
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-07-13 6:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 16:33 [PATCH v2 0/2] Init flow fixes for Samsung DSIM and TI SN65DSI84 Frieder Schrempf
2023-05-03 16:33 ` [PATCH v2 1/2] drm: bridge: samsung-dsim: Fix i.MX8M enable flow to meet spec Frieder Schrempf
2023-05-04 9:07 ` Alexander Stein
2023-05-16 7:33 ` Neil Armstrong
2023-07-12 22:34 ` Tim Harvey
2023-07-13 0:37 ` Adam Ford
2023-07-13 6:22 ` Alexander Stein [this message]
2023-07-13 7:18 ` Frieder Schrempf
2023-07-13 10:01 ` Frieder Schrempf
2023-07-18 23:03 ` Tim Harvey
2023-07-19 7:05 ` Frieder Schrempf
2023-07-19 16:34 ` Tim Harvey
2023-07-20 6:37 ` Frieder Schrempf
2023-05-03 16:33 ` [PATCH v2 2/2] drm/bridge: ti-sn65dsi83: Fix enable/disable " Frieder Schrempf
2023-05-04 9:11 ` Alexander Stein
2023-05-16 22:22 ` Fabio Estevam
2023-05-22 13:29 ` Frieder Schrempf
2023-05-16 7:33 ` Neil Armstrong
2023-05-25 16:19 ` [PATCH v2 0/2] Init flow fixes for Samsung DSIM and TI SN65DSI84 Neil Armstrong
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=15446320.O9o76ZdvQC@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=aford173@gmail.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=frieder.schrempf@kontron.de \
--cc=frieder@fris.de \
--cc=inki.dae@samsung.com \
--cc=jagan@amarulasolutions.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=marex@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=tharvey@gateworks.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
all inboxes | Powered by JetHome®