From: Hugo Villeneuve <hugo@hugovil.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: biju.das.au <biju.das.au@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Chris Brandt <Chris.Brandt@renesas.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Sam Ravnborg <sam@ravnborg.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v2 4/4] drm: renesas: rzg2l_mipi_dsi: Increase reset deassertion delay to 1 msec
Date: Mon, 23 Mar 2026 13:41:06 -0400 [thread overview]
Message-ID: <20260323134106.a439ffad5d1ff6927e0c549f@hugovil.com> (raw)
In-Reply-To: <TY3PR01MB113460833AFD4BE4422E5E737864BA@TY3PR01MB11346.jpnprd01.prod.outlook.com>
Hi Biju,
On Mon, 23 Mar 2026 15:19:27 +0000
Biju Das <biju.das.jz@bp.renesas.com> wrote:
> Hi Hugo,
>
> > -----Original Message-----
> > From: Hugo Villeneuve <hugo@hugovil.com>
> > Sent: 23 March 2026 14:20
> > Subject: Re: [PATCH v2 4/4] drm: renesas: rzg2l_mipi_dsi: Increase reset deassertion delay to 1 msec
> >
> > Hi Biju,
> >
> > On Thu, 19 Mar 2026 16:48:28 +0000
> > Biju <biju.das.au@gmail.com> wrote:
> >
> > > From: Biju Das <biju.das.jz@bp.renesas.com>
> > >
> > > The RZ/G2L hardware manual (Rev. 1.50, May 2025), Section 34.4.2.1,
> > > requires waiting more than 1 msec after deasserting the CMN_RSTB
> > > signal before the DSI-Tx module is ready. Increase the delay from 1
> > > usec to
> > > 1 msec by replacing udelay(1) with fsleep(1000).
> > >
> > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> >
> > In your first submission, I commented that "...this should be backported to stable branches (missing
> > Fixes / Cc: stable tags)?" and you answered with "Agreed, will add fixes/stable tags".
> >
> > If you still agree, this patch should be #3 in your list, so that it is easier/straightforward to
> > backport to stable branches.
>
> The patch order is changed. that is the reason I have not added any fixes/stable tags.
This is not a logical nor valid justification if the change
merits to be backported to stable branches as you indicated in
series 1. Why have you changed your mind?
> The if check in patch#3 makes it is not backportable to stable branches.
If you put the delay patch before that "if check", then it is
irrelevant, no?
> If I reorder this to patch#3 it is fixing just the delay mentioned in the hardware manual.
Yes, and that is also exactly what this current version does, no?
For me, it is simply changing a delay from 1us to 1ms. Whether you
change it before or after another patch isn't supposed to matter in the
end, unless I am missing something?
--
Hugo Villeneuve
next prev parent reply other threads:[~2026-03-23 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:48 [PATCH v2 0/4] Improvements on RZ/G2L MIPI DSI driver Biju
2026-03-19 16:48 ` [PATCH v2 1/4] drm: renesas: rzg2l_mipi_dsi: Move rzg2l_mipi_dsi_set_display_timing() Biju
2026-03-19 16:48 ` [PATCH v2 2/4] drm: renesas: rzg2l_mipi_dsi: Fix assert of CMN_RSTB signal Biju
2026-03-19 16:48 ` [PATCH v2 3/4] drm: renesas: rzg2l_mipi_dsi: Fix deassert " Biju
2026-03-19 16:48 ` [PATCH v2 4/4] drm: renesas: rzg2l_mipi_dsi: Increase reset deassertion delay to 1 msec Biju
2026-03-23 14:20 ` Hugo Villeneuve
2026-03-23 15:19 ` Biju Das
2026-03-23 17:41 ` Hugo Villeneuve [this message]
2026-03-25 13:31 ` Biju Das
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=20260323134106.a439ffad5d1ff6927e0c549f@hugovil.com \
--to=hugo@hugovil.com \
--cc=Chris.Brandt@renesas.com \
--cc=airlied@gmail.com \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sam@ravnborg.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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®