From: sashiko-bot@kernel.org
To: "Julian Braha" <julianbraha@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/panel: fix unmet dependency bug for DRM_PANEL_HIMAX_HX83121A
Date: Sat, 11 Jul 2026 23:48:42 +0000 [thread overview]
Message-ID: <20260711234842.9ACFD1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260711234230.2236041-1-julianbraha@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [Medium] The commit fixes an unmet dependency warning for `DRM_PANEL_HIMAX_HX83121A` by adding `select DRM_DISPLAY_HELPER`, but fails to apply the same fix to `DRM_PANEL_ILITEK_ILI9882T` and `DRM_PANEL_SAMSUNG_S6E3HA8`. Both of these configs also select `DRM_DISPLAY_DSC_HELPER` without selecting its dependency `DRM_DISPLAY_HELPER`. Notably, `DRM_PANEL_ILITEK_ILI9882T` is explicitly listed in the Kconfig warning output cited in the commit message itself.
--
--- Patch [1]: [PATCH] drm/panel: fix unmet dependency bug for DRM_PANEL_HIMAX_HX83121A ---
commit 0826a9c22686833fa118df0f402fe8308a98fa6d
Author: Julian Braha <julianbraha@gmail.com>
drm/panel: fix unmet dependency bug for DRM_PANEL_HIMAX_HX83121A
This commit fixes an unmet dependency warning for DRM_PANEL_HIMAX_HX83121A
by selecting DRM_DISPLAY_HELPER. It addresses a warning where
DRM_DISPLAY_DSC_HELPER was selected without its dependencies being met.
> WARNING: unmet direct dependencies detected for DRM_DISPLAY_DSC_HELPER
> Depends on [n]: HAS_IOMEM [=y] && DRM [=m] && DRM_DISPLAY_HELPER [=n]
> Selected by [m]:
> - DRM_PANEL_HIMAX_HX83121A [=m] && HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && DRM_MIPI_DSI [=y] && BACKLIGHT_CLASS_DEVICE [=m]
> - DRM_PANEL_ILITEK_ILI9882T [=m] && HAS_IOMEM [=y] && DRM [=m] && DRM_PANEL [=y] && OF [=y] && DRM_MIPI_DSI [=y] && BACKLIGHT_CLASS_DEVICE [=m]
[Severity: Medium]
This is a pre-existing issue, but should this patch also add the select
DRM_DISPLAY_HELPER statement for DRM_PANEL_ILITEK_ILI9882T?
The warning message above indicates that DRM_PANEL_ILITEK_ILI9882T suffers
from the exact same unmet dependency.
Additionally, looking at drivers/gpu/drm/panel/Kconfig, it appears
DRM_PANEL_SAMSUNG_S6E3HA8 has the same issue:
config DRM_PANEL_SAMSUNG_S6E3HA8
tristate "Samsung S6E3HA8 DSI video mode panel"
...
select DRM_DISPLAY_DSC_HELPER
Could we apply the same fix to both of these Kconfig options to completely
resolve the unmet dependency warnings across the panel drivers?
> diff --git a/drivers/gpu/drm/panel/Kconfig b/drivers/gpu/drm/panel/Kconfig
> index cfbfb371bc67e..06bfcef35a72e 100644
> --- a/drivers/gpu/drm/panel/Kconfig
> +++ b/drivers/gpu/drm/panel/Kconfig
> @@ -253,6 +253,7 @@ config DRM_PANEL_HIMAX_HX83121A
> depends on OF
> depends on DRM_MIPI_DSI
> depends on BACKLIGHT_CLASS_DEVICE
> + select DRM_DISPLAY_HELPER
> select DRM_DISPLAY_DSC_HELPER
> select DRM_KMS_HELPER
> help
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260711234230.2236041-1-julianbraha@gmail.com?part=1
prev parent reply other threads:[~2026-07-11 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 23:42 [PATCH] drm/panel: fix unmet dependency bug for DRM_PANEL_HIMAX_HX83121A Julian Braha
2026-07-11 23:48 ` 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=20260711234842.9ACFD1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=julianbraha@gmail.com \
--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