From: Michail Tatas <michail.tatas@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: michael@amarulasolutions.com, 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 v2 2/3] drm/panel: ilitek-ili9805: Use dsi_multi in init
Date: Tue, 21 Jul 2026 20:32:26 +0300 [thread overview]
Message-ID: <al-tKjc-wAzmEOUx@michalis-linux> (raw)
In-Reply-To: <CAD=FV=Wqo8Y=NCH0HVn8diQ2q1qxh0tcYLTKNKxGL2e-He_mNg@mail.gmail.com>
Hello,
Thanks a lot for the review Neil and Doug, I appreciate the feedback
> > +static void gpm1780a0_init(struct mipi_dsi_multi_context *ctx)
> > +{
> > + mipi_dsi_dcs_write_seq_multi(ctx, ILI9805_EXTCMD_CMD_SET_ENABLE_REG, ILI9805_SETEXTC_PARAMETER1,
> > + ILI9805_SETEXTC_PARAMETER2, ILI9805_SETEXTC_PARAMETER3);
>
> nit: the indentation of the 2nd line of your two-line
> mipi_dsi_dcs_write_seq_multi() seems off. checkpatch.sh --strict
> yells:
>
> CHECK: Alignment should match open parenthesis
>
> Strict mode also yells about a few lines that are over 100 characters.
> I'm not quite as picky about that, but it would be nic eto fix too...
>
> > + mipi_dsi_msleep(ctx, 100);
> > + mipi_dsi_dcs_write_seq_multi(ctx, 0xFD, 0x0F, 0x10, 0x44, 0x00);
> > + mipi_dsi_msleep(ctx, 100);
> > + mipi_dsi_dcs_write_seq_multi(ctx, 0xf8, 0x18, 0x02, 0x02, 0x18, 0x02, 0x02, 0x30, 0x00,
> > + 0x00, 0x30, 0x00, 0x00, 0x30, 0x00, 0x00);
>
> Since you're touching these lines anyway, can you also fix these
> functions to consistently use lower case hex instead of (mostly)
> uppercase hex? AKA 0xfd rather than 0xFD.
>
>
> Other than above nits, this looks great to me.
I have sent a new version with these changes
Regards,
Michail
next prev parent reply other threads:[~2026-07-21 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 19:03 [PATCH v2 0/3] drm/panel: ilitek-ili9805: convert to *_multi API Michail Tatas
2026-07-19 19:03 ` [PATCH v2 1/3] drm/panel: ilitek-ili9805: Use _multi variants Michail Tatas
2026-07-20 12:38 ` neil.armstrong
2026-07-20 20:07 ` Doug Anderson
2026-07-19 19:03 ` [PATCH v2 2/3] drm/panel: ilitek-ili9805: Use dsi_multi in init Michail Tatas
2026-07-20 12:39 ` neil.armstrong
2026-07-20 20:08 ` Doug Anderson
2026-07-21 17:32 ` Michail Tatas [this message]
2026-07-19 19:03 ` [PATCH v2 3/3] drm/panel: ilitek-ili9805: make cleanup funcs void Michail Tatas
2026-07-20 12:40 ` neil.armstrong
2026-07-20 20:08 ` Doug Anderson
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=al-tKjc-wAzmEOUx@michalis-linux \
--to=michail.tatas@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=michael@amarulasolutions.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.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®