[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85d9b8c3-6ddf-9b4c-76a2-8e9761eacc96@linaro.org>
Date: Fri, 17 Mar 2023 17:03:12 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Jacky Huang <ychuang570808@...il.com>, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, lee@...nel.org,
mturquette@...libre.com, sboyd@...nel.org, p.zabel@...gutronix.de,
gregkh@...uxfoundation.org, jirislaby@...nel.org
Cc: devicetree@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
schung@...oton.com, Jacky Huang <ychuang3@...oton.com>
Subject: Re: [PATCH 08/15] dt-bindings: clock: Document ma35d1 clock
controller bindings
On 17/03/2023 10:52, Jacky Huang wrote:
> Dear Krzysztof,
>
> Thanks for your advice.
>
> On 2023/3/17 下午 05:13, Krzysztof Kozlowski wrote:
>> On 17/03/2023 04:47, Jacky Huang wrote:
>>>>> +
>>>>> + nuvoton,pll-mode:
>>>>> + description:
>>>>> + A list of PLL operation mode corresponding to CAPLL, DDRPLL, APLL,
>>>>> + EPLL, and VPLL in sequential. The operation mode value 0 is for
>>>>> + integer mode, 1 is for fractional mode, and 2 is for spread
>>>>> + spectrum mode.
>>>>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>>>>> + maxItems: 5
>>>>> + items:
>>>>> + minimum: 0
>>>>> + maximum: 2
>>>> Why exactly this is suitable for DT?
>>> I will use strings instead.
>> I have doubts why PLL mode is a property of DT. Is this a board-specific
>> property?
>
> CA-PLL has mode 0 only.
> DDRPLL, APLL, EPLL, and VPLL have the same PLL design that supports
> integer mode, fractional mode, and spread spctrum mode. The PLL mode
> is controlled by clock controller register. I think it's not board-specific.
You described the feature but that does not answer why this is suitable
in DT. If this is not board-specific, then it is implied by compatible,
right? Or it does not have to be in DT at all.
Best regards,
Krzysztof
Powered by blists - more mailing lists