All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Janne Grunau" <j@jannau.net>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 6/7] arm64: dts: apple: t603x-j514-j516: Add PCIe device nodes
Date: Thu, 05 Nov 2026 11:42:55 +0000	[thread overview]
Message-ID: <sashiko-outbox-198970@kernel.org> (raw)
In-Reply-To: <20261105-apple-m3-pcie-v1-6-e00a72a604f8@jannau.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] arm64: dts: apple: wrong wifi0/bluetooth0 PCI IDs in t603x-j514-j516.dtsi
--

commit 93b064f5082472a65526181caee83a837e8be25d
Author: Yureka Lilian <yureka@cyberchaos.dev>

arm64: dts: apple: t603x-j514-j516: Add PCIe device nodes

This commit adds PCIe device nodes for Wi-Fi, Bluetooth, and the SD-card
reader to the M3 Pro and M3 Max MacBook Pro device trees, along with
board-specific brcm,board-type properties.

> diff --git a/arch/arm64/boot/dts/apple/t603x-j514-j516.dtsi b/arch/arm64/boot/dts/apple/t603x-j514-j516.dtsi
> index bbee373044f94..403a9cb3979c7 100644
> --- a/arch/arm64/boot/dts/apple/t603x-j514-j516.dtsi
> +++ b/arch/arm64/boot/dts/apple/t603x-j514-j516.dtsi
[ ... ]
> @@ -67,3 +69,42 @@ &serial0 {
>  &fpwm0 {
>  	status = "okay";
>  };
> +
> +/* PCIe devices */
> +
> +/*
> + * Force the bus number assignments so that we can declare some of the
> + * on-board devices and properties that are populated by the bootloader
> + * (such as MAC addresses).
> + */
> +&port00 {
> +	/* WLAN */
> +	bus-range = <1 1>;
> +
> +	wifi0: wifi@0,0 {
> +		compatible = "pci14e4,4433";
> +		reg = <0x10000 0x0 0x0 0x0 0x0>;
> +		/* To be filled by the loader */
> +		local-mac-address = [00 10 18 00 00 10];
> +		apple,antenna-sku = "XX";
> +	};
> +
> +	bluetooth0: bluetooth@0,1 {
> +		compatible = "pci14e4,5f71";
> +		reg = <0x10100 0x0 0x0 0x0 0x0>;
> +		/* To be filled by the loader */
> +		local-bd-address = [00 00 00 00 00 00];
> +	};
> +};

[Severity: Medium]
Should wifi0 and bluetooth0 under port00 in
arch/arm64/boot/dts/apple/t603x-j514-j516.dtsi use the Broadcom BCM4388
PCIe IDs ("pci14e4,4434" and "pci14e4,5f72") instead of the BCM4387 IDs
("pci14e4,4433" and "pci14e4,5f71")?

In arch/arm64/boot/dts/apple/t600x-j314-j316.dtsi (M1 Pro/Max), wifi0 and
bluetooth0 use "pci14e4,4433" and "pci14e4,5f71", which
arch/arm64/boot/dts/apple/t602x-j414-j416.dtsi (M2 Pro/Max) then
overrides for BCM4388:

&wifi0 {
	compatible = "pci14e4,4434";
};

&bluetooth0 {
	compatible = "pci14e4,5f72";
};

The base M3 MacBook Pro J504 in arch/arm64/boot/dts/apple/t8122-jxxx.dtsi
also uses "pci14e4,4434" and "pci14e4,5f72" for wifi0 and bluetooth0. It
looks like when the port00 node was copied from t600x-j314-j316.dtsi into
t603x-j514-j516.dtsi, the overrides from t602x-j414-j416.dtsi were missed,
leaving all six M3 Pro and M3 Max MacBook Pro device trees with the older
BCM4387 compatible strings.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261105-apple-m3-pcie-v1-0-e00a72a604f8@jannau.net?part=6

  reply	other threads:[~2026-11-05 11:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 11:35 [PATCH 0/7] Apple M3, M3 Pro/Max/Ultra PCIe device trees Janne Grunau
2026-11-05 11:35 ` [PATCH 1/7] arm64: dts: apple: t8122: Keep ps_apcie_phy_sw always-on Janne Grunau
2026-11-05 11:40   ` sashiko-bot
2026-11-05 11:35 ` [PATCH 2/7] dt-bindings: pci: apple,pcie: Add compatibles for M3 SoCs Janne Grunau
2026-11-05 11:39   ` sashiko-bot
2026-11-05 19:33   ` Bjorn Helgaas
2026-11-05 11:36 ` [PATCH 3/7] arm64: dts: apple: t6030: Add PCIe nodes Janne Grunau
2026-11-05 11:40   ` sashiko-bot
2026-11-05 11:36 ` [PATCH 4/7] arm64: dts: apple: t6031: " Janne Grunau
2026-11-05 11:40   ` sashiko-bot
2026-11-05 11:36 ` [PATCH 5/7] arm64: dts: apple: t8122: Add PCIe device nodes Janne Grunau
2026-11-05 11:41   ` sashiko-bot
2026-11-05 11:36 ` [PATCH 6/7] arm64: dts: apple: t603x-j514-j516: " Janne Grunau
2026-11-05 11:42   ` sashiko-bot [this message]
2026-11-05 11:36 ` [PATCH 7/7] arm64: dts: apple: t6032-j575d: " Janne Grunau
2026-11-05 11:46   ` 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-198970@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j@jannau.net \
    --cc=linux-pci@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 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.