From: sashiko-bot@kernel.org
To: "Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>
Cc: linux-sunxi@lists.linux.dev, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/8] drm/bridge: ite-it6263: Advertise HDMI 1.3 capabilities
Date: Thu, 01 Oct 2026 01:23:12 +0000 [thread overview]
Message-ID: <20261001012313.3C82B1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261001-bridge-advert-hdmi-caps-v1-4-f8806570e243@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Unused macro MAX_HDMI_TMDS_CHAR_RATE_HZ left as dead code
--
commit 4c0965b876d8cee6ad2805996d389a95afff88cf
Author: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
drm/bridge: ite-it6263: Advertise HDMI 1.3 capabilities
This commit advertises HDMI 1.3 support for the IT6263 bridge and sets the
maximum TMDS character rate. It also removes the now-redundant
it6263_hdmi_tmds_char_rate_valid() hook, as the core DRM helper handles
these checks before invoking the driver's hook.
> diff --git a/drivers/gpu/drm/bridge/ite-it6263.c b/drivers/gpu/drm/bridge/ite-it6263.c
> index 550999491086e..e8e0197171e10 100644
> --- a/drivers/gpu/drm/bridge/ite-it6263.c
> +++ b/drivers/gpu/drm/bridge/ite-it6263.c
> @@ -738,20 +738,6 @@ it6263_bridge_atomic_get_input_bus_fmts(struct drm_bridge *bridge,
> return input_fmts;
> }
>
> -static enum drm_mode_status
> -it6263_hdmi_tmds_char_rate_valid(const struct drm_bridge *bridge,
> - const struct drm_display_mode *mode,
> - unsigned long long tmds_rate)
> -{
> - if (mode->clock > MAX_PIXEL_CLOCK_KHZ)
> - return MODE_CLOCK_HIGH;
> -
> - if (tmds_rate > MAX_HDMI_TMDS_CHAR_RATE_HZ)
[Severity: Low]
With the removal of the it6263_hdmi_tmds_char_rate_valid() hook, the macro
MAX_HDMI_TMDS_CHAR_RATE_HZ in drivers/gpu/drm/bridge/ite-it6263.c is no
longer referenced anywhere. Should this unused macro also be removed to
prevent leaving dead code behind?
> - return MODE_CLOCK_HIGH;
> -
> - return MODE_OK;
> -}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261001-bridge-advert-hdmi-caps-v1-0-f8806570e243@collabora.com?part=4
next prev parent reply other threads:[~2026-10-01 1:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 1:14 [PATCH 0/8] drm: Advertise supported HDMI version in HDMI drivers Cristian Ciocaltea
2026-10-01 1:14 ` [PATCH 1/8] drm/bridge: adv7511: Advertise HDMI 1.2 capabilities Cristian Ciocaltea
2026-10-01 1:14 ` [PATCH 2/8] drm/bridge: inno-hdmi: " Cristian Ciocaltea
2026-10-01 1:14 ` [PATCH 3/8] drm/bridge: ite-it6263: Drop redundant .mode_valid hook Cristian Ciocaltea
2026-10-01 1:14 ` [PATCH 4/8] drm/bridge: ite-it6263: Advertise HDMI 1.3 capabilities Cristian Ciocaltea
2026-10-01 1:23 ` sashiko-bot [this message]
2026-10-01 1:14 ` [PATCH 5/8] drm/bridge: ite-it66121: Advertise HDMI 1.2 capabilities Cristian Ciocaltea
2026-10-01 1:14 ` [PATCH 6/8] drm/bridge: lontium-lt9611: Advertise HDMI 1.4 capabilities Cristian Ciocaltea
2026-10-01 1:14 ` [PATCH 7/8] drm/rockchip: rk3066_hdmi: " Cristian Ciocaltea
2026-10-01 1:14 ` [PATCH 8/8] drm/sun4i: hdmi: Convert to drmm_connector_hdmi_init() Cristian Ciocaltea
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=20261001012313.3C82B1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-sunxi@lists.linux.dev \
--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