Re: [PATCH v2 3/5] arm64: dts: google: Add dts directory for Google-designed silicon
Krzysztof Kozlowski <[email protected]> Fri, 24 Jul 2026 08:46:09 +0200
| Newsgroups | dev.linux.lists.soc,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-samsung-soc,org.kernel.vger.linux-serial |
|---|---|
| Message-ID | <20260724-sly-grinning-pig-86900e@quoll> |
On Wed, Jul 22, 2026 at 10:55:54AM +0100, Peter Griffin wrote: > From: Douglas Anderson <[email protected]> > > 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. > > Changes by Peter Griffin > * update config symbol help with at least 4 lines to avoid checkpatch > warning > > Signed-off-by: Douglas Anderson <[email protected]> > Signed-off-by: Peter Griffin <[email protected]> > --- > MAINTAINERS | 1 + > arch/arm64/Kconfig.platforms | 8 ++++++++ > arch/arm64/boot/dts/Makefile | 1 + > arch/arm64/boot/dts/google/Makefile | 1 + > 4 files changed, 11 insertions(+) > This is not Samsung derivative, but new top-level SoC platform, thus usual way is that you send it after review to soc@ (see maintainer-soc profile). OTOH, the maintainers entry is the same as Google Tensor GS, thus maybe you want me to pick this up via Samsung SoC tree? Both will work, up to you. Patch looks good. Reviewed-by: Krzysztof Kozlowski <[email protected]> Best regards, Krzysztof