From: Chintan Patel <chintanlike@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: sumit.semwal@linaro.org, neil.armstrong@linaro.org,
jesszhan0024@gmail.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] drm/panel: novatek-nt36672a: Convert to mipi_dsi_*_multi() helpers
Date: Wed, 18 Mar 2026 19:40:32 -0700 [thread overview]
Message-ID: <18f74625-5f97-425b-8389-17d1bbecd4ac@gmail.com> (raw)
In-Reply-To: <CAD=FV=WMKjA3eRhZyHd820BFBYUMfz_=F4ppNYPWDEHKwiORXA@mail.gmail.com>
On 3/6/26 09:40, Doug Anderson wrote:
> Hi,
>
> On Wed, Mar 4, 2026 at 8:49 PM Chintan Patel <chintanlike@gmail.com> wrote:
>>
>> Convert the driver to use the non-deprecated mipi_dsi_*_multi() helpers and
>> mipi_dsi_msleep().
>>
>> Switch DCS command sequences to the multi context API and
>> accumulate errors via struct mipi_dsi_multi_context. Replace
>> open-coded error handling with the multi helpers and convert
>> nt36672a_send_cmds() and power sequencing accordingly.
>>
>> This patch is intended to functionally be a no-op, though there is one
>> slight change. Previously a failure in regulator_bulk_disable() would
>> have caused nt36672a_panel_unprepare() to return an error. Now it
>> won't. No other errors in nt36672a_panel_unprepare() were propagated,
>> so this makes things consistent.
>>
>> Signed-off-by: Chintan Patel <chintanlike@gmail.com>
>> ---
>> Changes in v3:
>> - Keep local ret variable in nt36672a_panel_power_off() to preserve error code in logging.
>> - Change mipi_dsi_msleep() back to regular msleep(60) in power-down sequence to preserve behavior.
>> - Reset dsi_ctx.accum_err before set_display_off_multi() and before power-down to preserve original error-tolerant shutdown behavior.
>>
>> Changes in v2:
>> - Address alignment feedback from Doug.
>> - Restore original power-down ordering.
>> - Drop return value from nt36672a_panel_power_off().
>> - Consolidate error handling around dsi_ctx.accum_err.
>>
>> .../gpu/drm/panel/panel-novatek-nt36672a.c | 94 ++++++-------------
>> 1 file changed, 30 insertions(+), 64 deletions(-)
>
> Looks good to me now. I'll plan to apply in ~1 week if there is no
> further feedback.
>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
>
> As per my response in v1 [1], someone could still do additional
> cleanup to move away from the table-based initialization, but it
> doesn't make sense to block this patch on that. :-)
>
Agree - I have plan to address as separate patch.
> [1] https://lore.kernel.org/r/CAD=FV=WtjW5WWmjeb2zwF2PjiJeZv1jZS_UKZ0bT1658=CkwVA@mail.gmail.com
>
> -Doug
next prev parent reply other threads:[~2026-03-19 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 4:49 Chintan Patel
2026-03-06 17:40 ` Doug Anderson
2026-03-19 2:40 ` Chintan Patel [this message]
2026-03-13 15:46 ` Doug Anderson
2026-03-19 2:37 ` Chintan Patel
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=18f74625-5f97-425b-8389-17d1bbecd4ac@gmail.com \
--to=chintanlike@gmail.com \
--cc=airlied@gmail.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesszhan0024@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--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®