From: sashiko-bot@kernel.org
To: "Sebastian Reichel" <sre@kernel.org>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: mediatek: Use DP AltMode defines
Date: Wed, 14 Oct 2026 21:38:03 +0000 [thread overview]
Message-ID: <sashiko-outbox-171930@kernel.org> (raw)
In-Reply-To: <20261014-dp-altmode-dt-defines-v1-3-b657c9b6e4c3@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dts: Build failure due to undefined macro USB_DISPLAYPORT_SVID
--
commit 7a56cd1e07f3feb11fcda2188bbcfaa9db984f17
Author: Sebastian Reichel <sebastian.reichel@collabora.com>
arm64: dts: mediatek: Use DP AltMode defines
Use the new USB-C DP AltMode defines for the SVID and the capabilities
VDO to make the DTs more readable. This also fixes up mt8390 Genio
platform incorrectly announcing UFP_D (upwards facing) support.
> diff --git a/arch/arm64/boot/dts/mediatek/mt8390-genio-common.dtsi b/arch/arm64/boot/dts/mediatek/mt8390-genio-common.dtsi
> index 669eaec662f33..02f8b33d64ac7 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8390-genio-common.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8390-genio-common.dtsi
> @@ -527,8 +527,12 @@ PDO_FIXED_DUAL_ROLE |
>
> altmodes {
> displayport {
> - svid = /bits/ 16 <0xff01>;
> - vdo = <0x001c1c47>;
> + svid = /bits/ 16 <USB_DISPLAYPORT_SVID>;
[Severity: Low]
Is USB_DISPLAYPORT_SVID defined anywhere in the tree?
It appears this macro is undeclared, which will cause a build failure when
the Device Tree Compiler (dtc) attempts to process this file since the
preprocessor will leave the undeclared macro as a string literal.
Was the intended macro USB_SVID_DP_ALTMODE from include/dt-bindings/usb/pd.h?
> + vdo = <VDO_DP(DP_CAP_DPAM_V2_0, DP_CAP_CABLE_TYPE_PASSIVE,
> + DP_CAP_UHBR_13_5_UNSUPPORTED,
> + DP_PIN_UFP_NONE, DP_PIN_DFP_C_D_E,
> + DP_CAP_USB2_USED, DP_CAP_RECEPTACLE,
> + DP_CAP_SIGNALLING_HBR3, DP_CAP_DFP_D)>;
> };
> };
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8395-genio-common.dtsi b/arch/arm64/boot/dts/mediatek/mt8395-genio-common.dtsi
> index aef908df530ec..3f7d57dfcf939 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8395-genio-common.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8395-genio-common.dtsi
> @@ -597,8 +597,14 @@ PDO_FIXED_DUAL_ROLE |
>
> altmodes {
> displayport {
> - svid = /bits/ 16 <0xff01>;
> - vdo = <0x00001c46>;
> + svid = /bits/ 16 <USB_DISPLAYPORT_SVID>;
[Severity: Low]
Does this also need to be updated to USB_SVID_DP_ALTMODE to avoid breaking
the build for the mt8395 platform?
> + vdo = <VDO_DP(DP_CAP_DPAM_V2_0,
> + DP_CAP_CABLE_TYPE_PASSIVE,
> + DP_CAP_UHBR_13_5_UNSUPPORTED,
> + DP_PIN_UFP_NONE, DP_PIN_DFP_C_D_E,
> + DP_CAP_USB2_USED, DP_CAP_RECEPTACLE,
> + DP_CAP_SIGNALLING_HBR3,
> + DP_CAP_DFP_D)>;
> };
> };
>
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261014-dp-altmode-dt-defines-v1-0-b657c9b6e4c3@collabora.com?part=3
next prev parent reply other threads:[~2026-10-14 21:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 21:31 [PATCH 0/4] Add DP AltMode VDO definitions for DT usage Sebastian Reichel
2026-10-14 21:31 ` Sebastian Reichel
2026-10-14 21:31 ` [PATCH 1/4] dt-bindings: connector: Add DP AltMode VDO definitions Sebastian Reichel
2026-10-14 21:31 ` Sebastian Reichel
2026-10-14 21:41 ` sashiko-bot
2026-10-14 23:46 ` Dmitry Baryshkov
2026-10-14 23:46 ` Dmitry Baryshkov
2026-10-14 21:31 ` [PATCH 2/4] arm64: dts: rockchip: Use DP AltMode defines Sebastian Reichel
2026-10-14 21:31 ` Sebastian Reichel
2026-10-14 21:36 ` sashiko-bot
2026-10-14 23:46 ` Dmitry Baryshkov
2026-10-14 23:46 ` Dmitry Baryshkov
2026-10-14 21:31 ` [PATCH 3/4] arm64: dts: mediatek: " Sebastian Reichel
2026-10-14 21:31 ` Sebastian Reichel
2026-10-14 21:38 ` sashiko-bot [this message]
2026-10-14 23:46 ` Dmitry Baryshkov
2026-10-14 23:46 ` Dmitry Baryshkov
2026-10-14 23:47 ` Dmitry Baryshkov
2026-10-14 23:47 ` Dmitry Baryshkov
2026-10-14 21:31 ` [PATCH 4/4] arm64: dts: qcom: " Sebastian Reichel
2026-10-14 21:31 ` Sebastian Reichel
2026-10-14 21:35 ` sashiko-bot
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=sashiko-outbox-171930@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sre@kernel.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.