From: Francesco Dolcini <francesco@dolcini.it>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Ernest Van Hoecke <ernestvanhoecke@gmail.com>
Cc: tessolveupstream@gmail.com, andrzej.hajda@intel.com,
neil.armstrong@linaro.org, rfoss@kernel.org,
Laurent.pinchart@ideasonboard.com, jonas@kwiboo.se,
jernej.skrabec@gmail.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, marex@denx.de, valentin@compulab.co.il,
philippe.schenker@toradex.com, alexander.stein@ew.tq-group.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] drm: bridge: ti-sn65dsi83: Fix DSI mode flags for stable LVDS output
Date: Sat, 24 Oct 2026 11:54:05 +0200 [thread overview]
Message-ID: <20261024095405.GA5692@francesco-nb> (raw)
In-Reply-To: <DLATMIFKDMHV.24XNMCRI2ZKBI@bootlin.com>
Hello Luca, Ernest,
On Wed, Sep 09, 2026 at 03:30:53PM +0200, Luca Ceresoli wrote:
> On Fri Sep 4, 2026 at 2:02 PM CEST, Ernest Van Hoecke wrote:
> >> > Also, from our testing, when using:
> >> >
> >> > dsi->mode_flags = MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_BURST |
> >> > MIPI_DSI_MODE_VIDEO_NO_HSA | MIPI_DSI_MODE_NO_EOT_PACKET;
> >> >
> >> > we are not able to get display output.
> >>
> >> This is the case for the panel I worked on as well. In the practice we both
> >> observe that non-burst mode is what fixes the panel, but there is no clear
> >> explanation of the reason in the docs (that's what I hope to discover from
> >> TI).
> >>
> > I am testing a DSI panel on our Verdin iMX8MP module, and noticed that
> > this caused a regression.
[...]
> > I think we'll need to either revert this and later apply both together
> > when ready, or apply the second patch now as well. Right now, it broke
> > the DSI panel behind a TI sn65dsi83 bridge on v7.3-rc1.
>
> Reverting is surely the last resort. If you can answer the above questions
> it would be good, maybe we find out reverting is not necessary, and worst
> case we'll revert with better understanding on what went wrong, and maybe
> come up with a new fix that doesn't regress.
What's the status of this regression?
Francesco
next prev parent reply other threads:[~2026-10-24 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 5:38 [PATCH v3 0/1] " Sudarshan Shetty
2026-04-12 5:38 ` [PATCH v3 1/1] " Sudarshan Shetty
2026-04-15 7:13 ` Luca Ceresoli
2026-04-15 8:07 ` Luca Ceresoli
2026-04-16 9:10 ` tessolveupstream
2026-04-21 6:01 ` tessolveupstream
2026-04-23 9:16 ` tessolveupstream
2026-04-24 8:25 ` Luca Ceresoli
2026-05-19 8:48 ` tessolveupstream
2026-05-19 11:43 ` Luca Ceresoli
2026-05-20 9:04 ` tessolveupstream
2026-05-20 11:38 ` Luca Ceresoli
2026-05-20 12:29 ` tessolveupstream
2026-05-20 17:48 ` Luca Ceresoli
2026-05-21 6:30 ` tessolveupstream
2026-09-04 12:02 ` Ernest Van Hoecke
2026-09-09 13:30 ` Luca Ceresoli
2026-10-24 9:54 ` Francesco Dolcini [this message]
2026-04-15 13:51 ` Alexander Stein
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=20261024095405.GA5692@francesco-nb \
--to=francesco@dolcini.it \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ernestvanhoecke@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=philippe.schenker@toradex.com \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tessolveupstream@gmail.com \
--cc=tzimmermann@suse.de \
--cc=valentin@compulab.co.il \
/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®