From: Janne Grunau <j@jannau.net>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: 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>,
asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: arm: apple: Add M3 (t8112 and t603x) devices
Date: Fri, 20 Mar 2026 13:19:23 +0100 [thread overview]
Message-ID: <20260320121923.GA355325@robin.jannau.net> (raw)
In-Reply-To: <21f2e3a2-ae8b-4997-a3c4-bb77663c04e8@kernel.org>
On Thu, Mar 19, 2026 at 09:11:52PM +0100, Krzysztof Kozlowski wrote:
> On 19/03/2026 15:57, Janne Grunau wrote:
> > The Apple M3 based devices follow the pattern of their M1 and M2
> > predecessors. One notable difference is that the M3 Max SoC has two
> > variants: t6031 and t6034.
> > t6034 has 14 CPU cores, 30 GPU cores and a combined 384-bit LPPDR5
> > memory bus while t6031 comes with 16 CPU cores, 40 GPU cores and a
> > 512-bit wide LPPDR5 interface. These are the only apparent
> > differences between those two SoCs.
>
> There is no user of this in this patchset and your commit msg or
> changelog must explain that. We don't take bindings without users.
I have a series adding M3 device trees for these devices. I
misremembered your feedback from the M2 Pro/Max/Utra submission and was
planning to send dt-binding updates and the device trees using them
separately.
I'll send them as single series instead.
Janne
prev parent reply other threads:[~2026-03-20 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 14:57 [PATCH] dt-bindings: arm: apple: Add M3 (t8112 and t603x) devices Janne Grunau
2026-03-19 20:11 ` Krzysztof Kozlowski
2026-03-20 12:19 ` Janne Grunau [this message]
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=20260320121923.GA355325@robin.jannau.net \
--to=j@jannau.net \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox