[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <228a0b1b-68ec-40d2-b379-e9894a34cb57@kernel.org>
Date: Thu, 16 Jan 2025 10:15:59 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Sergio Paracuellos <sergio.paracuellos@...il.com>,
linux-clk@...r.kernel.org
Cc: sboyd@...nel.org, mturquette@...libre.com, tsbogend@...ha.franken.de,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com,
p.zabel@...gutronix.de, linux-mips@...r.kernel.org,
devicetree@...r.kernel.org, yangshiji66@...look.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/6] dt-bindings: clock: add clock and reset definitions
for Ralink SoCs
On 15/01/2025 16:30, Sergio Paracuellos wrote:
> Add clock and reset missing definitions for RT2880, RT305X, RT3352, RT3383,
> RT5350, MT7620 and MT76X8 Ralink SoCs. Update bindings to clarify clock and
> reset cells depending on these new introduced constants so consumer nodes
> can easily use the correct one in DTS files.
I asked to explain why these should be in the bindings. Usage by DTS
alone, if driver does not use them, is not the reason as I explained
last time. The reason is that your driver actually depends on these
specific numbers because how it is written.
Or I understood it wrong and this is purely for DTS?
Best regards,
Krzysztof
Powered by blists - more mailing lists