From: Aradhya Bhatia <a-bhatia1@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Jyri Sarha <jyri.sarha@iki.fi>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: DRI Development List <dri-devel@lists.freedesktop.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Dominik Haller <d.haller@phytec.de>,
Sam Ravnborg <sam@ravnborg.org>,
Thierry Reding <treding@nvidia.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Praneeth Bajjuri <praneeth@ti.com>, Udit Kumar <u-kumar1@ti.com>,
Devarsh Thakkar <devarsht@ti.com>,
Jayesh Choudhary <j-choudhary@ti.com>,
Jai Luthra <j-luthra@ti.com>
Subject: Re: [PATCH v4 07/11] drm/bridge: cdns-dsi: Reset the DCS write FIFO
Date: Thu, 11 Jul 2024 13:00:44 +0530 [thread overview]
Message-ID: <3aa27f67-02d5-4bd4-b45e-9d4753a333f8@ti.com> (raw)
In-Reply-To: <11bf22b8-4a5a-4c9b-8c78-0454165ae711@ideasonboard.com>
On 26/06/24 16:33, Tomi Valkeinen wrote:
> On 22/06/2024 14:09, Aradhya Bhatia wrote:
>> If any normal DCS write command has already been transmitted prior to
>> transmitting any Zero-Parameter DCS command, then it is necessary to
>> clear the TX FIFO by resetting it. Otherwise, the FIFO points to another
>> location, and the DCS command transmits unnecessary data causing the
>> panel to not work[0].
>>
>> Allow the DCS Write FIFO in the cdns-dsi controller to reset as a rule,
>> before any DCS packet is transmitted to the DSI peripheral.
>>
>> [0]: Section 12.6.5.7.5.2: "Command Mode Settings" in TDA4VM Technical
>> Reference Manual: https://www.ti.com/lit/zip/spruil1
>
> Hmm so if I read the doc right, it says: if sending zero-parameter dcs
> command, clear the FIFO and write zero to direct_cmd_wrdat.
That's right.
>
> Your patch seems to always clear the FIFO, not only for zero-parameter
> commands. Is that a problem (I don't think so, but...)?
>
My patch does clear the FIFO every time.
While there is no documentation that says its harmless, I have tested
the patches with RPi Panel (which doesn't seem to have any
zero-parameter commands in the driver) - and so far it seems to have
worked fine.
> Also, is the direct_cmd_wrdat written at all when sending zero-parameter
> dcs command?
>
At the moment, no.
Apparently there are 2 types of "Zero parameter" commands.
There is,
a) "MIPI_DSI_GENERIC_SHORT_WRITE_0_PARAM" - which has absolutely no
parameter that needs to be sent, and there is,
b) "MIPI_DSI_DCS_SHORT_WRITE" - which has a 1-byte command value that
needs to be transmitted.
(Macros referred from mipi_display.h)
In the J721E TRM[0], there is a table[1] which classifies the
"MIPI_DSI_DCS_SHORT_WRITE" - the command with 1-byte command parameter -
as a "zero parameter" command.
For a "MIPI_DSI_DCS_SHORT_WRITE" command, we are still writing the
1-byte command data into the FIFO.
However, in the other section which talks about resetting the FIFO[2],
it is mentioned that, for "zero parameter" commands, the FIFO needs to
be reset and then 0x00 needs to be written to the FIFO.
The second step cannot be done for "MIPI_DSI_DCS_SHORT_WRITE" commands
because we want to write the 1 byte command parameter instead of 0x00
into the FIFO.
So, the only logical conclusion is that, the FIFO reset is only required
for _truly_ zero parameter commands, which is the
"MIPI_DSI_GENERIC_SHORT_WRITE_0_PARAM" command.
So, I am planning to change this patch to do 2 things, under the
condition that there are absolutely no data bytes that require
transmission.
a. Reset the FIFO.
b. Write 0x00 to the FIFO.
Regards
Aradhya
[0]: J721E TRM: https://www.ti.com/lit/zip/spruil1
[1]: Table: 12-1933: "DSI Main Settings Register Description".
[2]: Section 12.6.5.7.5.2: "Command Mode Settings"
>
>>
>> Signed-off-by: Aradhya Bhatia <a-bhatia1@ti.com>
>> ---
>> drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c
>> b/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c
>> index 126e4bccd868..cad0c1478ef0 100644
>> --- a/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c
>> +++ b/drivers/gpu/drm/bridge/cadence/cdns-dsi-core.c
>> @@ -1018,6 +1018,9 @@ static ssize_t cdns_dsi_transfer(struct
>> mipi_dsi_host *host,
>> cdns_dsi_init_link(dsi);
>> + /* Reset the DCS Write FIFO */
>> + writel(0x00, dsi->regs + DIRECT_CMD_FIFO_RST);
>> >> ret = mipi_dsi_create_packet(&packet, msg);
>> if (ret)
>> goto out;
>
>
next prev parent reply other threads:[~2024-07-11 7:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 11:09 [PATCH v4 00/11] drm/bridge: cdns-dsi: Fix the color-shift issue Aradhya Bhatia
2024-06-22 11:09 ` [PATCH v4 01/11] drm/bridge: cdns-dsi: Fix OF node pointer Aradhya Bhatia
2024-06-26 10:06 ` Tomi Valkeinen
2024-06-22 11:09 ` [PATCH v4 02/11] drm/bridge: cdns-dsi: Move to devm_drm_of_get_bridge() Aradhya Bhatia
2024-06-26 10:10 ` Tomi Valkeinen
2024-06-22 11:09 ` [PATCH v4 03/11] drm/bridge: cdns-dsi: Fix Phy _init() and _exit() Aradhya Bhatia
2024-06-26 10:25 ` Tomi Valkeinen
2024-06-26 13:30 ` Aradhya Bhatia
2024-06-22 11:09 ` [PATCH v4 04/11] drm/bridge: cdns-dsi: Fix the link and phy init order Aradhya Bhatia
2024-06-26 10:28 ` Tomi Valkeinen
2024-06-22 11:09 ` [PATCH v4 05/11] drm/bridge: cdns-dsi: Fix the clock variable for mode_valid() Aradhya Bhatia
2024-06-26 10:47 ` Tomi Valkeinen
2024-06-26 13:56 ` Aradhya Bhatia
2024-06-22 11:09 ` [PATCH v4 06/11] drm/bridge: cdns-dsi: Wait for Clk and Data Lanes to be ready Aradhya Bhatia
2024-06-26 10:52 ` Tomi Valkeinen
2024-06-22 11:09 ` [PATCH v4 07/11] drm/bridge: cdns-dsi: Reset the DCS write FIFO Aradhya Bhatia
2024-06-26 11:03 ` Tomi Valkeinen
2024-07-11 7:30 ` Aradhya Bhatia [this message]
2024-06-22 11:09 ` [PATCH v4 08/11] drm/mipi-dsi: Add helper to find input format Aradhya Bhatia
2024-06-26 11:06 ` Tomi Valkeinen
2024-06-22 11:09 ` [PATCH v4 09/11] drm/bridge: cdns-dsi: Support atomic bridge APIs Aradhya Bhatia
2024-06-26 11:09 ` Tomi Valkeinen
2024-06-22 11:09 ` [PATCH v4 10/11] drm/atomic-helper: Re-order bridge chain pre-enable and post-disable Aradhya Bhatia
2024-06-26 11:28 ` Tomi Valkeinen
2024-06-26 13:07 ` Maxime Ripard
2024-07-11 7:32 ` Aradhya Bhatia
2024-12-26 14:14 ` Devarsh Thakkar
2024-06-22 11:09 ` [PATCH v4 11/11] drm/bridge: cdns-dsi: Use pre_enable/post_disable to enable/disable Aradhya Bhatia
2024-06-26 11:39 ` Tomi Valkeinen
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=3aa27f67-02d5-4bd4-b45e-9d4753a333f8@ti.com \
--to=a-bhatia1@ti.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=d.haller@phytec.de \
--cc=daniel@ffwll.ch \
--cc=devarsht@ti.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=j-choudhary@ti.com \
--cc=j-luthra@ti.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=jyri.sarha@iki.fi \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=rfoss@kernel.org \
--cc=sam@ravnborg.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=treding@nvidia.com \
--cc=tzimmermann@suse.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).