From: sashiko-bot@kernel.org
To: "Nickolay Goppen" <setotau@mainlining.org>
Cc: dri-devel@lists.freedesktop.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 2/3] drivers: gpu: drm: panel: Add BOE NT51021 driver
Date: Sun, 13 Sep 2026 14:56:57 +0000 [thread overview]
Message-ID: <20260913145657.B9EB71F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260913-qcom-novatek-nt51021-panels-v3-2-266bc5d7e8c9@mainlining.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Unconditional execution of CABC off sequence overwrites untouched state for boe_tv101wum_nm0 variant.
--
commit 80218d28f8a5f485ff9423dca654f2257664a78b
Author: Nickolay Goppen <setotau@mainlining.org>
drivers: gpu: drm: panel: Add BOE NT51021 driver
Add driver for BOE NT51021-based 8-inch and 10-inch DSI video mode
panels used in Xiaomi Mi Pad 4, Mi Pad 4 Plus and Amazon Fire HD 10 tablets.
> diff --git a/drivers/gpu/drm/panel/panel-novatek-nt51021.c b/drivers/gpu/drm/panel/panel-novatek-nt51021.c
> new file mode 100644
> index 0000000000000..fc99908917868
> --- /dev/null
> +++ b/drivers/gpu/drm/panel/panel-novatek-nt51021.c
[ ... ]
> +static int nt51021_novatek_off(struct novatek_nt51021_desc *ctx)
> +{
> + struct mipi_dsi_multi_context dsi_ctx = { .dsi = ctx->dsi };
> +
> + nt51021_cabc_off(&dsi_ctx);
[Severity: Medium]
The commit message mentions that for the boe_tv101wum_nm0 variant, CABC is
untouched because the vendor drives it over I2C from the backlight path. While
the initialization sequence for the nm0 variant correctly omits turning CABC
on, this teardown sequence appears to unconditionally call nt51021_cabc_off()
for all variants.
When nt51021_cabc_off() is called, it executes:
mipi_dsi_generic_write_seq_multi(dsi_ctx, 0x90, 0xc0);
Could this unconditional write cause unexpected hardware states or DSI/I2C
collisions during the display teardown for the nm0 variant, since the register
was intended to be left alone?
> +
> + mipi_dsi_generic_write_seq_multi(&dsi_ctx, 0x8f, 0xa5);
> + mipi_dsi_msleep(&dsi_ctx, 20);
> + mipi_dsi_dcs_set_display_off_multi(&dsi_ctx);
> + mipi_dsi_msleep(&dsi_ctx, 130);
> + mipi_dsi_dcs_enter_sleep_mode_multi(&dsi_ctx);
> + mipi_dsi_msleep(&dsi_ctx, 70);
> + mipi_dsi_generic_write_seq_multi(&dsi_ctx, 0x8f, 0x00);
> + mipi_dsi_usleep_range(&dsi_ctx, 4000, 5000);
> +
> + return dsi_ctx.accum_err;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260913-qcom-novatek-nt51021-panels-v3-0-266bc5d7e8c9@mainlining.org?part=2
next prev parent reply other threads:[~2026-09-13 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 14:50 [PATCH v3 0/3] Novatek NT51021 DSI panel IC driver Nickolay Goppen
2026-09-13 14:50 ` [PATCH v3 1/3] dt-bindings: display: panel: Add Novatek NT51021 Nickolay Goppen
2026-09-13 14:50 ` [PATCH v3 2/3] drivers: gpu: drm: panel: Add BOE NT51021 driver Nickolay Goppen
2026-09-13 14:56 ` sashiko-bot [this message]
2026-09-13 14:50 ` [PATCH v3 3/3] MAINTAINERS: Add myself and Ryan Brue as maintainers of NT51021 panel driver Nickolay Goppen
2026-09-13 17:23 ` [PATCH v3 0/3] Novatek NT51021 DSI panel IC driver Ryan Brue
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=20260913145657.B9EB71F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=setotau@mainlining.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.