Re: [PATCH 0/2] Add chip ID for Exynos7870 SoC
From: Krzysztof Kozlowski <krzk@kernel.org>
Date: 2025-02-05 07:49:05
Also in:
linux-devicetree, linux-samsung-soc, lkml
From: Krzysztof Kozlowski <krzk@kernel.org>
Date: 2025-02-05 07:49:05
Also in:
linux-devicetree, linux-samsung-soc, lkml
On 04/02/2025 20:29, Kaustabh Chakraborty wrote:
On 2025-02-04 07:53, Krzysztof Kozlowski wrote:quoted
On 03/02/2025 21:32, Kaustabh Chakraborty wrote:quoted
This patch series is a part of Exynos7870 upstreaming. Signed-off-by: Kaustabh Chakraborty <redacted> --- Kaustabh Chakraborty (2): dt-bindings: hwinfo: samsung,exynos-chipid: add exynos7870-chipid compatible soc: samsung: exynos-chipid: add support for exynos7870 Documentation/devicetree/bindings/hwinfo/samsung,exynos-chipid.yaml | 1 + drivers/soc/samsung/exynos-chipid.c | 1 + 2 files changed, 2 insertions(+)When I asked to split, I said per subsystem. Soc is one subsystem. Everything targeting SoC should be in one patchset. get_maintainers.pl tells the name of the subsystem and its maintainers. If there is going to be resend/new version, combine patchsets for soc into one patchset (just like the example I gave last time).Alright, so I'll move these patches to the one which has the devicetrees. There's also a Documentation/devicetree/bindings/soc/ patch in exynos7870-pmu-clocks [1]. The CLKOUT driver uses the compatible declared in there, i.e., the CLKOUT driver depends on that commit. So, should it stay there? Or...?
The binding stays with the driver. Best regards, Krzysztof