[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2490f7dd-9b6b-2865-4e44-37808b167c11@linaro.org>
Date: Thu, 4 May 2023 16:39:27 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Heiko Stuebner <heiko@...ech.de>,
Philipp Zabel <p.zabel@...gutronix.de>,
Sebastian Reichel <sebastian.reichel@...labora.com>,
Shreeya Patel <shreeya.patel@...labora.com>,
Kever Yang <kever.yang@...k-chips.com>,
Finley Xiao <finley.xiao@...k-chips.com>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel@...labora.com
Subject: Re: [PATCH 2/8] dt-bindings: nvmem: rockchip-otp: Add compatible for
RK3588
On 04/05/2023 16:14, Cristian Ciocaltea wrote:
>>> + reset-names:
>>> + items:
>>> + - const: phy
>>> +
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - rockchip,rk3588-otp
>>> + then:
>>> + properties:
>>> + clocks:
>>> + minItems: 4
>>> + maxItems: 4
>>> + clock-names:
>>> + items:
>>> + - const: otpc
>>> + - const: apb
>>> + - const: arb
>>> + - const: phy
>>
>> Keep the same order of clocks as in older variants, so you can keep the
>> list in top-level place and here only minItems: 4.
>>
>>> + resets:
>>> + minItems: 1
>>> + maxItems: 3
>>> + reset-names:
>>> + items:
>>> + - const: otpc
>>
>> Shouldn't this be phy?
>
> It seems there is no reset for PHY, or at least I couldn't find any
> reference in the RK3588 TRM, nor in the downstream driver implementation.
OK, just to be sure that this is not the same reset as rk3308 just
differently named in consumer.
Best regards,
Krzysztof
Powered by blists - more mailing lists