Re: [PATCH 0/7] Add support for the Axis ARTPEC-9 SoC

[Krzysztof Kozlowski <krzk@kernel.org>]

On 18/09/2025 12:36, Ravi Patel wrote:
> 
> 
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Sent: 18 September 2025 06:35
>> To: Ravi Patel <ravi.patel@samsung.com>; robh@kernel.org; krzk+dt@kernel.org; conor+dt@kernel.org; jesper.nilsson@axis.com;
>> lars.persson@axis.com; mturquette@baylibre.com; sboyd@kernel.org; alim.akhtar@samsung.com; s.nawrocki@samsung.com;
>> cw00.choi@samsung.com
>> Cc: ksk4725@coasia.com; smn1196@coasia.com; linux-arm-kernel@axis.com; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org;
>> linux-arm-kernel@lists.infradead.org; linux-samsung-soc@vger.kernel.org; linux-clk@vger.kernel.org; pjsin865@coasia.com;
>> gwk1013@coasia.com; bread@coasia.com; jspark@coasia.com; limjh0823@coasia.com; lightwise@coasia.com; hgkim05@coasia.com;
>> mingyoungbo@coasia.com; shradha.t@samsung.com; swathi.ks@samsung.com; kenkim@coasia.com
>> Subject: Re: [PATCH 0/7] Add support for the Axis ARTPEC-9 SoC
>>
>> On 17/09/2025 17:49, Ravi Patel wrote:
>>> Add basic support for the Axis ARTPEC-9 SoC which contains
>>> 6-core Cortex-A55 CPU and other several IPs. This SoC is an
>>> Axis-designed chipset used in surveillance camera products.
>>>
>>> This ARTPEC-9 SoC has a variety of Samsung-specific IP blocks and
>>> Axis-specific IP blocks and SoC is manufactured by Samsung Foundry.
>>>
>>> This patch series includes below changes:
>>> - CMU (Clock Management Unit) driver and its bindings (patch #1 to #3)
>>> - PMU bindings (patch #4)
>>> - Basic Device Tree for ARTPEC-9 SoC and boards (patch #5 to #7)
>>>
>>> The patch series has been tested on the ARTPEC-9 EVB with
>>> Linux Samsung SoC tree (for-next branch) and intended
>>> to be merged via the `arm-soc` tree.
>>>
>>> NOTE: This patch series is dependent on following floating patches:
>>> 1. https://lore.kernel.org/all/20250917070004.87872-1-ravi.patel@samsung.com/T/#t
>>
>> NAK, sorry, DTS cannot depend on the drivers. Please decouple the
>> dependencies.
> 
> Ok, so you want patch #1 - #5 in separate series and #6 - #7 (DTS patches) in another series.

No, I meant above dependencies. You said that these patchset, including
DTS, depends on above. Above are drivers and that's a no go. I said it
multiple times already in various occasions.

Patchset should be organized per maintainers subsystem, but that's
different question.

> Can you please review the patches, I will address review comments in v2 (if any) itself.

As mentioned in other threads, I closed my tree a week ago (if you are
surprised, notice kernel cycles and development process), so review will
happen a bit later.

> 
>>
>> Maybe you wanted to point me where the bindings are, but then say so.
> 
> Yes, these dependencies are for bindings related.
So not really a dependency so again: just provide links to the bindings.

Best regards,
Krzysztof