Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chen-Yu Tsai" <wenst@chromium.org>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v7 15/16] arm64: dts: mediatek: mt8195-cherry: Add M.2 E-key slot
Date: Fri, 24 Jul 2026 09:03:55 +0000	[thread overview]
Message-ID: <20260724090355.C9F111F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260724084328.3943997-16-wenst@chromium.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Removal of the `wifi@0` device tree node silently breaks Wake-on-WLAN (WoWLAN) capability for the MT7921 WiFi device.
--

--- Patch [15]: [PATCH v7 15/16] arm64: dts: mediatek: mt8195-cherry: Add M.2 E-key slot ---
commit f3cf400c3b922d9936d6cc4d1a7c83d4b85941b6
Author: Chen-Yu Tsai <wenst@chromium.org>

arm64: dts: mediatek: mt8195-cherry: Add M.2 E-key slot

The Mt8195 Cherry design features an M.2 E-key slot for WiFi/BT combo cards.
This patch adds the proper representation for it, replacing the PCIe wifi node
and supply properties under the PCIe controller and xhci3 nodes.

> diff --git a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> --- a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi

[ ... ]

> @@ -791,14 +832,14 @@ pcie@0 {
>  		reg = <0 0 0 0 0>;
>  		device_type = "pci";
>  		num-lanes = <1>;
> -		vpcie3v3-supply = <&pp3300_wlan>;
>  		#address-cells = <3>;
>  		#size-cells = <2>;
>  		ranges;
>  
> -		wifi@0 {
> -			reg = <0 0 0 0 0>;
> -			wakeup-source;
> +		port {
> +			pcie1_ep: endpoint {
> +				remote-endpoint = <&wifi_ep>;
> +			};
>  		};

[Severity: Medium]
Does removing the wifi@0 node silently break Wake-on-WLAN capability for the
MT7921 WiFi device?

Looking at the driver in mt7921/pci.c, it probes the device and explicitly
checks for the wakeup-source property on its associated device tree node.

Since the wifi@0 node is completely replaced by the OF graph port node here,
which does not represent a PCI device and has no reg property, it appears
the PCI core will no longer assign an OF node to the MT7921 device. Will
this cause the wakeup-source check to fail and leave WoWLAN permanently
disabled?

>  	};
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260724084328.3943997-1-wenst@chromium.org?part=15

  reply	other threads:[~2026-07-24  9:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  8:43 [PATCH v7 00/16] arm64: mediatek: Add M.2 E-key slot on Chromebooks Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 01/16] device property: Add fwnode_graph_get_port_by_id() Chen-Yu Tsai
2026-07-24  9:01   ` sashiko-bot
2026-07-24  8:43 ` [PATCH v7 02/16] device property: Add fwnode_graph_get_next_port_endpoint() Chen-Yu Tsai
2026-07-24  9:03   ` sashiko-bot
2026-07-24  8:43 ` [PATCH v7 03/16] power: sequencing: Add pwrseq_get_state() Chen-Yu Tsai
2026-07-24 11:09   ` Bartosz Golaszewski
2026-07-24  8:43 ` [PATCH v7 04/16] usb: hub: Use assign_bit() in usb_hub_set_port_power() Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 05/16] usb: hub: Return actual error from hub_configure() in hub_probe() Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 06/16] usb: hub: Associate port@ fwnode with USB port device Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 07/16] usb: core: Move struct usb_port and related APIs to port.h Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 08/16] usb: hub: Pass |struct usb_port*| to usb_port_is_power_on() Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 09/16] usb: hub: Use usb_hub_set_port_power() to control port power everywhere Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 10/16] usb: hub: Power on connected M.2 E-key connectors with power sequencing API Chen-Yu Tsai
2026-07-24  9:02   ` sashiko-bot
2026-07-24  8:43 ` [PATCH v7 11/16] dt-bindings: usb: mediatek,mtk-xhci: Switch to ports for USB connections Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 12/16] power: sequencing: pcie-m2: support matching on remote "port" node Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 13/16] power: sequencing: pcie-m2: Add usb and sdio targets for E-key connector Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 14/16] power: sequencing: pcie-m2: Split Bluetooth unit based on interface Chen-Yu Tsai
2026-07-24  8:43 ` [PATCH v7 15/16] arm64: dts: mediatek: mt8195-cherry: Add M.2 E-key slot Chen-Yu Tsai
2026-07-24  9:03   ` sashiko-bot [this message]
2026-07-24  8:43 ` [PATCH v7 16/16] arm64: dts: mediatek: mt8188-geralt: Add WiFi/BT as " Chen-Yu Tsai

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=20260724090355.C9F111F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wenst@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox