[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bf438af8-5969-73e4-009d-cb7d93095a5e@kernel.org>
Date: Fri, 25 Mar 2022 08:31:25 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Stephen Boyd <sboyd@...nel.org>, Johan Jonker <jbx6244@...il.com>,
heiko@...ech.de
Cc: robh+dt@...nel.org, krzk+dt@...nel.org, mturquette@...libre.com,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] dt-bindings: clock: convert rockchip,rk3188-cru.txt to
YAML
On 25/03/2022 01:51, Stephen Boyd wrote:
> Quoting Johan Jonker (2022-03-24 12:51:36)
>> Hi Heiko, Krzysztof,
>>
>> Question for the Rockchip clock maintainer:
>> What clock should be used here and other SoCs with several clock parents
>> in the tree?
>>
>> The clock.yaml produces a lot off notifications like:
>>
>> /arch/arm/boot/dts/rk3036-evb.dtb: clock-controller@...00000: 'clocks'
>> is a dependency of 'assigned-clocks'
>
> 'clocks' is not a dependency of 'assigned-clocks'. The dt-schema should
> be fixed to remove that requirement.
If the driver does not have any clock inputs ("clocks" property), why
does it care about some clock frequencies and parents?
The clocks is the logical dependency of assigned-clocks, because
otherwise hardware description is not complete.
What should be here for Rockhip? We had similar cases like this for many
drivers, I was fixing some of Exynos as well. In my case usually the
root/external clock was missing, so I supplied is as input clock to the
clock controller.
Best regards,
Krzysztof
Powered by blists - more mailing lists