From: Krzysztof Kozlowski <krzk@kernel.org>
To: Janne Grunau <j@jannau.net>, Sven Peter <sven@kernel.org>,
Neal Gompa <neal@gompa.dev>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: apple: Fix style issues for t6031 multi die .dtsi
Date: Fri, 4 Sep 2026 08:23:00 +0200 [thread overview]
Message-ID: <3c8c1465-4b4a-40d4-a247-27218623ecb5@kernel.org> (raw)
In-Reply-To: <20260903-apple-soc-multi-die-style-v1-3-eeb05ea0c187@jannau.net>
On 03/09/2026 15:59, Janne Grunau wrote:
> The M3 Max/Ultra .dtsi files containing most MMIO nodes are a collection
> of nodes without parent. The proper embedding inside a "simple-bus"
> parent only happens in t6031.dtsi and t6032.dtsi.
> Fix these dt style issue by using a define for their parent soc node and
> bracket those MMIO nodes inside it.
>
> Link: https://lore.kernel.org/asahi/e2365307-32d6-4ef9-9919-55ba69786741@kernel.org/
> Suggested-by: Krzysztof Kozlowski <krzk@kernel.org>
> Signed-off-by: Janne Grunau <j@jannau.net>
> ---
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-09-04 6:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 13:59 [PATCH 0/3] Fix dt-style-check issues in Apple silicon multi die .dtsi Janne Grunau
2026-09-03 13:59 ` [PATCH 1/3] arm64: dts: apple: Fix style issues for t600x " Janne Grunau
2026-09-04 6:22 ` Krzysztof Kozlowski
2026-09-03 13:59 ` [PATCH 2/3] arm64: dts: apple: Fix style issues for t602x " Janne Grunau
2026-09-03 14:13 ` sashiko-bot
2026-09-04 6:22 ` Krzysztof Kozlowski
2026-09-03 13:59 ` [PATCH 3/3] arm64: dts: apple: Fix style issues for t6031 " Janne Grunau
2026-09-04 6:23 ` Krzysztof Kozlowski [this message]
2026-09-04 15:08 ` [PATCH 0/3] Fix dt-style-check issues in Apple silicon " Sven Peter
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=3c8c1465-4b4a-40d4-a247-27218623ecb5@kernel.org \
--to=krzk@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neal@gompa.dev \
--cc=robh@kernel.org \
--cc=sven@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.