Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Steffen Trumtrar" <s.trumtrar@pengutronix.de>
Cc: conor+dt@kernel.org, krzk+dt@kernel.org,
	devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 2/2] drm/panel: simple: add NEC NL6448BC33-70C
Date: Fri, 15 May 2026 12:09:46 +0000	[thread overview]
Message-ID: <20260515120947.155A2C2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260515-v7-1-topic-panel-simple-nl6448bc33-v2-2-74ab0baa1817@pengutronix.de>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Hardware configuration mismatch causing WARN_ON stack traces and display failure.
--

commit ed55c8f29ffdce716c41311e39a5db4fabaf9549
Author: Steffen Trumtrar <s.trumtrar@pengutronix.de>

drm/panel: simple: add NEC NL6448BC33-70C

This commit adds support for the NEC NL6448BC33-70C 10.4" 640x480 LCD module
to the simple panel driver.

> diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c
> index 236bd56208ccf..dca6cbc41bd9f 100644
> --- a/drivers/gpu/drm/panel/panel-simple.c
> +++ b/drivers/gpu/drm/panel/panel-simple.c
[ ... ]
> +static const struct panel_desc nec_nl6448bc33_70c = {
> +	.modes = &nec_nl6448bc33_70c_mode,
> +	.num_modes = 1,
> +	.bpc = 6,
> +	.size = {
> +		.width = 211,
> +		.height = 158,
> +	},
> +	.bus_format = MEDIA_BUS_FMT_RGB666_1X18,
> +	.bus_flags = DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE,
> +	.connector_type = DRM_MODE_CONNECTOR_LVDS,

Are this bus_format and bus_flags compatible with an LVDS connector type?

In panel_simple_probe(), there are WARN_ON() checks that enforce strict
configuration rules for LVDS panels.

MEDIA_BUS_FMT_RGB666_1X18 is a parallel RGB (DPI) format, not an LVDS format
(like MEDIA_BUS_FMT_RGB666_1X7X3_SPWG). Because it is missing from the LVDS
format whitelist, it looks like this will trigger a warning during probe.

Similarly, DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE is not in the whitelist of
allowed LVDS flags, which guarantees the bus flag WARN_ON() will also trigger.

Could this mix of parallel RGB format settings with an LVDS connector type
cause hardware configuration issues or a corrupted display?

> +};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260515-v7-1-topic-panel-simple-nl6448bc33-v2-0-74ab0baa1817@pengutronix.de?part=2

      reply	other threads:[~2026-05-15 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 11:46 [PATCH v2 0/2] Add NEC LCD Technologies NL6448BC33-70C Panel Support Steffen Trumtrar
2026-05-15 11:46 ` [PATCH v2 1/2] dt-bindings: display: simple: Add NEC NL6448BC33-70C panel Steffen Trumtrar
2026-05-15 11:46 ` [PATCH v2 2/2] drm/panel: simple: add NEC NL6448BC33-70C Steffen Trumtrar
2026-05-15 12:09   ` sashiko-bot [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=20260515120947.155A2C2BCB7@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.trumtrar@pengutronix.de \
    --cc=sashiko-reviews@lists.linux.dev \
    /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