From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: <tessolveupstream@gmail.com>, <andrzej.hajda@intel.com>,
<neil.armstrong@linaro.org>, <rfoss@kernel.org>
Cc: <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: Wed, 20 May 2026 13:38:36 +0200 [thread overview]
Message-ID: <DINH3J2SM26P.3KE6GE9VPB1OC@bootlin.com> (raw)
In-Reply-To: <1716be56-ac43-440b-a5df-58cbf571ba95@gmail.com>
Hello,
On Wed May 20, 2026 at 11:04 AM CEST, tessolveupstream wrote:
[...]
>>> We have not received any further updates from TI regarding this issue, and
>>> at this point, we are not sure if we will get additional feedback from them.
>>> As you had mentioned earlier that the patch could be considered after
>>> waiting for some time, could you please let us know how we can proceed
>>> further from here?
>>
>> I am getting some feedback from TI, but it is taking some time.
>>
>> For the time being I think it is clear that HBP and HFP are required, and
>> so removing the MIPI_DSI_MODE_VIDEO_NO_HFP and MIPI_DSI_MODE_VIDEO_NO_HBP
>> in your patch seems to be fully correct, even though this had no effect on
>> the panel I tested.
>>
>> I'm still trying to get some better info to ensure that switching from
>> burst mode to non-burst mode is not expected to have side effects.
>>
>> For thi reason, I think it would be great if you could send a new version
>> with two separate patches: the first one enabling HFP and HBP and which can
>> be applied right away, the second to disable burst mode for which I'd wait
>> a bit longer for TI feedback. You can keep the Tested-by lines.
>>
>
> Thanks for the clarification. I just wanted to confirm my understanding
> regarding the patch split you suggested.
>
> From your comments, my understanding is that the first patch would only
> enable HFP and HBP by removing MIPI_DSI_MODE_VIDEO_NO_HFP and
> MIPI_DSI_MODE_VIDEO_NO_HBP, while keeping burst mode enabled, so the mode
> flags would become:
>
> dsi->mode_flags = MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_BURST |
> MIPI_DSI_MODE_VIDEO_NO_HSA | MIPI_DSI_MODE_NO_EOT_PACKET;
>
> Then, the second patch would only disable burst mode, resulting in:
>
> dsi->mode_flags = MIPI_DSI_MODE_VIDEO | MIPI_DSI_MODE_VIDEO_NO_HSA |
> MIPI_DSI_MODE_NO_EOT_PACKET;
>
> Could you please confirm whether my understanding is correct?
Yes, correct.
> 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).
On the other hand the HBP and HFP are clearly required by the docs, so it
should be fine to enable those without waiting for further info from
TI. This is not fixing your and my panel, but it's a fix, no doubt.
> I just wanted to mention this
> observation in case it is relevant to the patch split discussion.
>
> Additionally, regarding the Tested-by tags you mentioned earlier,
> should I carry them forward to both patches, or would you prefer them
> only on the applicable patch?
I'd say yes. People who sent these tags have tested a patch that is the sum
of the two future patches, so I'd say it's OK to keep the R-by on both
patches.
Thanks for your patience. We'll get to the bottom of this issue! :)
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-05-20 11:48 UTC|newest]
Thread overview: 16+ 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 [this message]
2026-05-20 12:29 ` tessolveupstream
2026-05-20 17:48 ` Luca Ceresoli
2026-05-21 6:30 ` tessolveupstream
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=DINH3J2SM26P.3KE6GE9VPB1OC@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--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=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome