From: sashiko-bot@kernel.org
To: "Damon Ding" <damon.ding@rock-chips.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v9 10/10] drm/rockchip: analogix_dp: Add support for RK3576
Date: Wed, 27 May 2026 03:37:15 +0000 [thread overview]
Message-ID: <20260527033716.549091F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260527024336.191433-11-damon.ding@rock-chips.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Incomplete hardware configuration or mandatory syscon lookup failure for RK3576 eDP.
--
commit dba937ab560aacd4dd5f156770d047256a5462b7
Author: Damon Ding <damon.ding@rock-chips.com>
drm/rockchip: analogix_dp: Add support for RK3576
This commit adds Analogix eDP support for the RK3576 platform.
It introduces a new chip data table and device tree matching entry
for basic eDP functionality.
> diff --git a/drivers/gpu/drm/rockchip/analogix_dp-rockchip.c b/drivers/gpu/drm/rockchip/analogix_dp-rockchip.c
> index d2af5eb29dbb5..d4c5dd61e95bb 100644
> --- a/drivers/gpu/drm/rockchip/analogix_dp-rockchip.c
> +++ b/drivers/gpu/drm/rockchip/analogix_dp-rockchip.c
[ ... ]
> @@ -522,6 +522,14 @@ static const struct rockchip_dp_chip_data rk3288_dp[] = {
> { /* sentinel */ }
> };
>
> +static const struct rockchip_dp_chip_data rk3576_edp[] = {
> + {
> + .chip_type = RK3576_EDP,
> + .reg = 0x27dc0000,
[Severity: High]
The commit message states RK3576 fully matches the RK3588 design. RK3588 uses
the .edp_mode GRF field to switch the combo PHY into eDP mode during
rockchip_dp_poweron(). Is the .edp_mode field intentionally omitted here? If
RK3576 requires this bit like RK3588, will the hardware fail to power on
correctly without it?
Additionally, if RK3576 genuinely does not use the GRF for this and it is
intentionally omitted, does rockchip_dp_of_probe() still unconditionally call
syscon_regmap_lookup_by_phandle(np, "rockchip,grf")? If so, will omitting the
property from the device tree cause an immediate probe failure?
> + },
> + { /* sentinel */ }
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260527024336.191433-1-damon.ding@rock-chips.com?part=10
prev parent reply other threads:[~2026-05-27 3:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 2:43 [PATCH v9 00/10] Add eDP support for RK3576 Damon Ding
2026-05-27 2:43 ` [PATCH v9 01/10] dt-bindings: display: rockchip: analogix-dp: Fix hclk as third clock for RK3588 Damon Ding
2026-05-27 2:43 ` [PATCH v9 02/10] dt-bindings: display: rockchip: analogix-dp: Add per-clock descriptions Damon Ding
2026-05-27 2:43 ` [PATCH v9 03/10] arm64: dts: rockchip: Add missing hclk for RK3588 eDP0 Damon Ding
2026-05-27 2:43 ` [PATCH v9 04/10] arm64: dts: rockchip: Add missing hclk for RK3588 eDP1 Damon Ding
2026-05-27 2:43 ` [PATCH v9 05/10] drm/rockchip: analogix_dp: Enable hclk for RK3588 Damon Ding
2026-05-27 3:11 ` sashiko-bot
2026-05-27 2:43 ` [PATCH v9 06/10] dt-bindings: display: rockchip: analogix-dp: Add support for RK3576 Damon Ding
2026-05-27 2:43 ` [PATCH v9 07/10] arm64: dts: rockchip: Add eDP node " Damon Ding
2026-05-27 2:43 ` [PATCH v9 08/10] drm/bridge: analogix_dp: Rename and simplify is_rockchip() Damon Ding
2026-05-27 2:54 ` sashiko-bot
2026-05-27 2:43 ` [PATCH v9 09/10] drm/bridge: analogix_dp: Add support for RK3576 Damon Ding
2026-05-27 2:43 ` [PATCH v9 10/10] drm/rockchip: " Damon Ding
2026-05-27 3:37 ` 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=20260527033716.549091F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=damon.ding@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--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