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] drm/panel: novatek-nt36672a: Convert to mipi_dsi_*_multi() helpers
Date: Mon, 23 Feb 2026 20:38:23 -0800 [thread overview]
Message-ID: <bda58fc8-0c59-48b4-8a8d-fb05f72b49f5@gmail.com> (raw)
In-Reply-To: <CAD=FV=WtjW5WWmjeb2zwF2PjiJeZv1jZS_UKZ0bT1658=CkwVA@mail.gmail.com>
>
> I won't insist since it's a matter of opinion, but IMO get rid of the
> `err` local variable and consistently use `dsi_ctx.accum_err` to store
> the error code in this function. Yeah, it's a bit awkward, but having
> the separate `err` variable just makes it too easy to mess up and use
> it. As one example of where that happened, see commit 61ce50fd8196
> ("drm/panel: jdi-lpm102a188a: Fix error code in jdi_panel_prepare()").
>
> Also: instead of returning right away, I think you want to make sure
> that the GPIO gets set to 0 like the old code did, don't you? I'd be a
> little hesitant changing this unless we can truly prove that the GPIO
> set is not needed or unless we're certain that the GPIO set was
> incorrect (in which case we should fix it in a separate patch).
>
> ...nicely, if you use `dsi_ctx.accum_err` you don't even need a
> "goto". You can just let the "_multi" functions all run and be
> no-ops...
>
> -Doug
Thank you Doug! Those were good points! Will work on v2.
prev parent reply other threads:[~2026-02-24 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 4:34 Chintan Patel
2026-02-23 21:33 ` Doug Anderson
2026-02-24 4:38 ` Chintan Patel [this message]
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=bda58fc8-0c59-48b4-8a8d-fb05f72b49f5@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®