From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Douglas Anderson" <dianders@chromium.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>
Cc: linux-samsung-soc@vger.kernel.org, Roy Luo <royluo@google.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Chen-Yu Tsai <wenst@chromium.org>,
Julius Werner <jwerner@chromium.org>,
William McVicker <willmcvicker@google.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Drew Fustini <fustini@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, soc@lists.linux.dev
Subject: Re: [PATCH 3/4] arm64: dts: google: Add dts directory for Google-designed silicon
Date: Wed, 12 Nov 2025 09:10:07 +0100 [thread overview]
Message-ID: <b55d94f2-6b79-407f-af58-b9847db3c9a2@kernel.org> (raw)
In-Reply-To: <20251111112158.3.I35b9e835ac49ab408e5ca3e0983930a1f1395814@changeid>
On 11/11/2025 20:22, Douglas Anderson wrote:
> The first four Google Tensor SoCs were offshoots of Samsung Exynos
> SoCs and their device trees were organized under the "exynos/google"
> directory. Starting with the Google Tensor G5 SoC in Pixel 10 phones,
> Google Tensor SoCs are now of Google's own design. Add a location in
> the tree to store these device tree files.
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
>
> MAINTAINERS | 1 +
> arch/arm64/Kconfig.platforms | 6 ++++++
> arch/arm64/boot/dts/Makefile | 1 +
> arch/arm64/boot/dts/google/Makefile | 1 +
> 4 files changed, 9 insertions(+)
> create mode 100644 arch/arm64/boot/dts/google/Makefile
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ddecf1ef3bed..f73a247ec61c 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10606,6 +10606,7 @@ C: irc://irc.oftc.net/pixel6-kernel-dev
> F: Documentation/devicetree/bindings/clock/google,gs101-clock.yaml
> F: Documentation/devicetree/bindings/soc/google/google,gs101-pmu-intr-gen.yaml
> F: arch/arm64/boot/dts/exynos/google/
> +F: arch/arm64/boot/dts/google/
> F: drivers/clk/samsung/clk-gs101.c
> F: drivers/phy/samsung/phy-gs101-ufs.c
> F: include/dt-bindings/clock/google,gs101.h
I am fine with this but also please consider having separate maintainers
entry, because, as you said, this is a completely different SoC.
In any case, up to you folks.
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 13173795c43d..044af9a3b45f 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -138,6 +138,12 @@ config ARCH_EXYNOS
> help
> This enables support for ARMv8 based Samsung Exynos SoC family.
>
> +config ARCH_GOOGLE
> + bool "Google-Designed SoC family"
> + help
> + This enables support for Google Tensor chips starting at the
> + Google Tensor G5.
> +
> config ARCH_K3
> bool "Texas Instruments Inc. K3 multicore SoC architecture"
> select SOC_TI
> diff --git a/arch/arm64/boot/dts/Makefile b/arch/arm64/boot/dts/Makefile
> index b0844404eda1..b4b5023d61d2 100644
> --- a/arch/arm64/boot/dts/Makefile
> +++ b/arch/arm64/boot/dts/Makefile
> @@ -17,6 +17,7 @@ subdir-y += cavium
> subdir-y += cix
> subdir-y += exynos
> subdir-y += freescale
> +subdir-y += google
> subdir-y += hisilicon
> subdir-y += intel
> subdir-y += lg
> diff --git a/arch/arm64/boot/dts/google/Makefile b/arch/arm64/boot/dts/google/Makefile
> new file mode 100644
> index 000000000000..a6b187e2d631
> --- /dev/null
> +++ b/arch/arm64/boot/dts/google/Makefile
> @@ -0,0 +1 @@
> +# SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
Drop the '+' in GPL license.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-12 8:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 19:22 [PATCH 0/4] arm64: google: Introduce frankel, blazer, and mustang boards Douglas Anderson
2025-11-11 19:22 ` [PATCH 1/4] dt-bindings: arm: google: Add bindings for frankel/blazer/mustang Douglas Anderson
2025-11-12 7:58 ` Krzysztof Kozlowski
2025-11-12 19:19 ` Doug Anderson
2025-11-13 7:23 ` Krzysztof Kozlowski
2025-11-13 16:23 ` Doug Anderson
2025-11-13 16:34 ` Krzysztof Kozlowski
2025-11-13 17:16 ` Doug Anderson
2025-11-13 17:43 ` Krzysztof Kozlowski
2025-11-13 18:04 ` Doug Anderson
2025-11-13 18:41 ` Doug Anderson
2025-11-14 9:26 ` Krzysztof Kozlowski
2025-11-14 15:54 ` Rob Herring
2025-11-13 2:27 ` Rob Herring
2025-11-13 3:29 ` Doug Anderson
2025-11-14 15:20 ` Rob Herring
2025-11-14 18:53 ` Doug Anderson
2025-11-18 22:47 ` Doug Anderson
2025-11-11 19:22 ` [PATCH 2/4] dt-bindings: serial: snps-dw-apb-uart: Add "google,lga-uart" Douglas Anderson
2025-11-12 7:59 ` Krzysztof Kozlowski
2025-11-11 19:22 ` [PATCH 3/4] arm64: dts: google: Add dts directory for Google-designed silicon Douglas Anderson
2025-11-12 8:10 ` Krzysztof Kozlowski [this message]
2025-11-12 12:26 ` Peter Griffin
2025-11-12 12:36 ` Linus Walleij
2025-11-12 12:43 ` Peter Griffin
2025-11-11 19:22 ` [PATCH 4/4] arm64: dts: google: Add initial dts for frankel, blazer, and mustang Douglas Anderson
2025-11-12 8:14 ` Krzysztof Kozlowski
2025-11-12 9:35 ` Chen-Yu Tsai
2025-11-12 9:48 ` Krzysztof Kozlowski
2025-11-12 20:59 ` Doug Anderson
2025-11-17 6:43 ` Chen-Yu Tsai
2025-11-17 6:55 ` Krzysztof Kozlowski
2025-11-17 7:01 ` Chen-Yu Tsai
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=b55d94f2-6b79-407f-af58-b9847db3c9a2@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andre.draszik@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=fustini@kernel.org \
--cc=jwerner@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=royluo@google.com \
--cc=soc@lists.linux.dev \
--cc=tudor.ambarus@linaro.org \
--cc=wenst@chromium.org \
--cc=will@kernel.org \
--cc=willmcvicker@google.com \
/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;
as well as URLs for NNTP newsgroup(s).