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: Tue, 19 May 2026 13:43:24 +0200 [thread overview]
Message-ID: <DIMMKNT9RHYM.1BRF1S1V5SIKI@bootlin.com> (raw)
In-Reply-To: <e88af0b7-388d-4b0a-8eb2-a367e24e84fb@gmail.com>
Hello,
On Tue May 19, 2026 at 10:48 AM CEST, tessolveupstream wrote:
>
>
> On 24-04-2026 13:55, Luca Ceresoli wrote:
>> Hello,
>>
>> On Thu Apr 23, 2026 at 11:16 AM CEST, tessolveupstream wrote:
>>
>>>> I had reached out to TI for clarification and any related documentation
>>>> updates, but I have not received any response so far.Given this, it is
>>>> uncertain whether we will be able to obtain further details or official
>>>> confirmation from TI in the near term.
>>>>
>>>> I would appreciate your guidance on how you would prefer us to proceed
>>>> from here.
>>>
>>> I followed up with TI, and they pointed us to the relevant sections in the
>>> SN65DSI83/84/86 datasheets covering DSI video transmission specifications.
>>
>> Thanks for keeping on! I'm also trying to get info from TI, I'm keeping you
>> up to date if that will happen.
>>
>>>> https://www.ti.com/lit/ds/symlink/sn65dsi84.pdf?ts=1776924088430&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FSN65DSI84
>>>
>>> As per datasheet Section 7.4.7, the device operates in DSI video mode with
>>> fixed horizontal timing, where HBP, and HFP are explicitly defined and expected
>>> to be present as part of the video line structure. The timing description in
>>> this section assumes standard non‑burst video transmission with all horizontal
>>> blanking intervals accounted for.
>>>
>>> The datasheet does not document support for DSI video burst mode,
>>
>> This sentence seems incorrect. Section 7.4.7 starts with this sentence:
>> "The SN65DSI84 supports burst video mode and non-burst video mode ...".
>>
>> Even though asa matter of fact it looks like many users have issues that
>> get solved by disabling burst mode.
>>
>>> nor does it
>>> mention support for omitting horizontal front or back porch intervals. In
>>> particular, there is no indication that the device can operate with collapsed
>>> or suppressed horizontal blanking, as enabled by MIPI_DSI_MODE_VIDEO_BURST,
>>> MIPI_DSI_MODE_VIDEO_NO_HFP, or MIPI_DSI_MODE_VIDEO_NO_HBP.
>>
>> This is correct.
>>
>> We can still try to get TI feedback, but it that won't happen in, say, a
>> few weeks then I think we should apply this patch.
>>
>
> 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.
I understand this is painful and taking time, but it's important to ensure
as much as possible that the change won't introduce regressions on existing
hardware.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-05-19 11:43 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 [this message]
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-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=DIMMKNT9RHYM.1BRF1S1V5SIKI@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