From: sashiko-bot@kernel.org
To: "Janne Grunau" <j@jannau.net>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/7] arm64: dts: apple: t8122: Keep ps_apcie_phy_sw always-on
Date: Thu, 05 Nov 2026 11:40:23 +0000 [thread overview]
Message-ID: <sashiko-outbox-198966@kernel.org> (raw)
In-Reply-To: <20261105-apple-m3-pcie-v1-1-e00a72a604f8@jannau.net>
> The APCIE_PHY_SW power state is in Apple's device tree a child of the
> virtual storage and general purpose PCIe power-states. MacOS however
> keeps it always powered on. Mirror this behaviour like the M2 Pro/Max
> device trees already do in t602x-pgmr.dtsi.
>
> Fixes: c65ab4905e58 ("arm64: dts: apple: Initial t8122 (M3) device trees")
> Signed-off-by: Janne Grunau <j@jannau.net>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105-apple-m3-pcie-v1-0-e00a72a604f8@jannau.net?part=1
next prev parent reply other threads:[~2026-11-05 11:40 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 [this message]
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
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-198966@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=j@jannau.net \
--cc=linux-pci@vger.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.