[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <793a88b8-148e-c9a0-3c21-4f15380e1085@linaro.org>
Date: Sat, 2 Apr 2022 22:19:05 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: LABBE Corentin <clabbe@...libre.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: heiko@...ech.de, herbert@...dor.apana.org.au, krzk+dt@...nel.org,
robh+dt@...nel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH v4 28/33] dt-bindings: crypto: rockchip: convert to new
driver bindings
On 02/04/2022 22:10, LABBE Corentin wrote:
> Le Sat, Apr 02, 2022 at 01:53:58PM +0200, Krzysztof Kozlowski a écrit :
>> On 01/04/2022 22:17, Corentin Labbe wrote:
>>> The latest addition to the rockchip crypto driver need to update the
>>> driver bindings.
>>>
>>>
>>> reset-names:
>>> - maxItems: 1
>>> + deprecated: true
>>
>> Why reset-names are being deprecated? Did we talk about this?
>>
>
> Since I use the devm_reset_control_array_get_exclusive, there is no need to have reset-names.
The reset-names are not only for Linux driver. In any case, Linux driver
could get always reset/clock/gpio by index, not by name.
Additionally, there can be different implementation in different
system/user of bindings.
Therefore the driver implementation does not matter (or matters little)
for the bindings, so for multi entries the reset-names are needed.
Best regards,
Krzysztof
Powered by blists - more mailing lists