[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <75c27bf0-4cc1-41ec-86ed-5c7f3d38f5d8@kernel.org>
Date: Wed, 5 Jun 2024 10:12:01 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Pengfei Li <pengfei.li_1@....com>, Rob Herring <robh@...nel.org>
Cc: krzk+dt@...nel.org, conor+dt@...nel.org, abelvesa@...nel.org,
mturquette@...libre.com, sboyd@...nel.org, shawnguo@...nel.org,
s.hauer@...gutronix.de, kernel@...gutronix.de, festevam@...il.com,
ping.bai@....com, ye.li@....com, peng.fan@....com, aisheng.dong@....com,
frank.li@....com, tharvey@...eworks.com, alexander.stein@...tq-group.com,
gregor.herburger@...tq-group.com, hiago.franco@...adex.com,
joao.goncalves@...adex.com, hvilleneuve@...onoff.com,
Markus.Niebel@...tq-group.com, m.felsch@...gutronix.de,
m.othacehe@...il.com, bhelgaas@...gle.com, leoyang.li@....com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org, imx@...ts.linux.dev,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 1/5] dt-bindings: clock: Add i.MX91 clock support
On 06/06/2024 01:59, Pengfei Li wrote:
> On Tue, Jun 04, 2024 at 10:03:06AM -0500, Rob Herring wrote:
>> On Wed, May 29, 2024 at 07:26:30PM -0700, Pengfei Li wrote:
>>> i.MX91 has similar Clock Control Module(CCM) design as i.MX93.
>>> Add a new compatible string for i.MX91.
>>>
>>> Signed-off-by: Pengfei Li <pengfei.li_1@....com>
>>> Reviewed-by: Frank Li <Frank.Li@....com>
>>> ---
>>> Documentation/devicetree/bindings/clock/imx93-clock.yaml | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/clock/imx93-clock.yaml b/Documentation/devicetree/bindings/clock/imx93-clock.yaml
>>> index ccb53c6b96c1..98c0800732ef 100644
>>> --- a/Documentation/devicetree/bindings/clock/imx93-clock.yaml
>>> +++ b/Documentation/devicetree/bindings/clock/imx93-clock.yaml
>>> @@ -16,6 +16,7 @@ description: |
>>> properties:
>>> compatible:
>>> enum:
>>> + - fsl,imx91-ccm
>>> - fsl,imx93-ccm
>>
>> Should fallback to fsl,imx93-ccm? Being a superset should be ok because
>> your DT should never use the non-existent clocks. If not, where is the
>> driver change?
>>
>> Rob
>>
>
> Hi Rob Herring,
>
> Due to the different maintainers of the CCM framework and DTS, I have separated
> the CCM driver patch and plan to send the DTS patch first before sending the
> CCM driver patch. If that's possible, could you help merge this patch first? If
> this is not allowed, I can also send out the CCM driver patch at the same time.
Binding goes with the driver, not DTS.
Best regards,
Krzysztof
Powered by blists - more mailing lists