From: sashiko-bot@kernel.org
To: "Chen-Yu Tsai" <wenst@chromium.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v9 14/15] arm64: dts: mediatek: mt8195-cherry: Add M.2 E-key slot
Date: Wed, 16 Sep 2026 08:23:19 +0000 [thread overview]
Message-ID: <20260916082320.09AA51F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916075745.3549953-15-wenst@chromium.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] pci: implicit loss of WoWLAN support due to wifi@0 node removal
--
commit 5f7e95ba7e04fe3e98237e1ef5a8952a18138c2e
Author: Chen-Yu Tsai <wenst@chromium.org>
arm64: dts: mediatek: mt8195-cherry: Add M.2 E-key slot
This commit adds the proper representation for the M.2 E-key slot on the Mt8195
Cherry design, which is used for WiFi/BT combo cards. It replaces the existing
PCIe wifi node and moves the associated supply properties.
> diff --git a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
> index ef7afc436aefc..8d4cc30d91e44 100644
> --- 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 and its wakeup-source property silently disable
Wake-on-WLAN support for the MT7921 PCIe driver?
The MT7921 PCIe driver (drivers/net/wireless/mediatek/mt76/mt7921/pci.c)
relies on dev->mt76.dev->of_node to check for this property and enable
Wake-on-WLAN via device_init_wakeup().
Because the PCI device node is removed and replaced only with an OF graph
port inside the root port pcie@0, the PCI core (pci_set_of_node) will no
longer find a matching child node to assign to pdev->dev.of_node.
Consequently, it appears the driver will fail to read wakeup-source, which
could cause a functional regression in power management.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260916075745.3549953-1-wenst@chromium.org?part=14
next prev parent reply other threads:[~2026-09-16 8:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 7:57 [PATCH v9 00/15] usb: enable M.2 E-key slot USB with pwrseq Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 01/15] device property: Add fwnode_graph_get_port_by_id() Chen-Yu Tsai
2026-09-16 8:06 ` sashiko-bot
2026-09-16 7:57 ` [PATCH v9 02/15] device property: Add fwnode_graph_get_next_port_endpoint() Chen-Yu Tsai
2026-09-16 8:14 ` sashiko-bot
2026-09-16 7:57 ` [PATCH v9 03/15] power: sequencing: Add pwrseq_get_state() Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 04/15] usb: hub: Use assign_bit() in usb_hub_set_port_power() Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 05/15] usb: hub: Return actual error from hub_configure() in hub_probe() Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 06/15] usb: hub: Associate port@ fwnode with USB port device Chen-Yu Tsai
2026-10-01 10:53 ` Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 07/15] usb: hub: Pass |struct usb_port*| to usb_port_is_power_on() Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 08/15] usb: hub: Use usb_hub_set_port_power() to control port power everywhere Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 09/15] usb: hub: Power on connected M.2 E-key connectors with power sequencing API Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 10/15] dt-bindings: usb: mediatek,mtk-xhci: Switch to ports for USB connections Chen-Yu Tsai
2026-09-16 8:10 ` sashiko-bot
2026-09-16 7:57 ` [PATCH v9 11/15] power: sequencing: pcie-m2: support matching on remote "port" node Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 12/15] power: sequencing: pcie-m2: Add usb and sdio targets for E-key connector Chen-Yu Tsai
2026-09-16 7:57 ` [PATCH v9 13/15] power: sequencing: pcie-m2: Split Bluetooth unit based on interface Chen-Yu Tsai
2026-09-16 8:13 ` sashiko-bot
2026-09-16 7:57 ` [PATCH v9 14/15] arm64: dts: mediatek: mt8195-cherry: Add M.2 E-key slot Chen-Yu Tsai
2026-09-16 8:23 ` sashiko-bot [this message]
2026-09-16 7:57 ` [PATCH v9 15/15] arm64: dts: mediatek: mt8188-geralt: Add WiFi/BT as " Chen-Yu Tsai
2026-09-21 10:51 ` [PATCH v9 00/15] usb: enable M.2 E-key slot USB with pwrseq AngeloGioacchino Del Regno
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=20260916082320.09AA51F000FF@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