Re: [PATCH 0/2] Add chip ID for Exynos7870 SoC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/02/2025 20:29, Kaustabh Chakraborty wrote:
> On 2025-02-04 07:53, Krzysztof Kozlowski wrote:
>> On 03/02/2025 21:32, Kaustabh Chakraborty wrote:
>>> This patch series is a part of Exynos7870 upstreaming.
>>>
>>> Signed-off-by: Kaustabh Chakraborty <kauschluss@xxxxxxxxxxx>
>>> ---
>>> 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




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux