netdev - Re: [PATCH v3 01/15] include: dt-bindings: add LAN969x clock bindings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <756ead5d-8c9b-480d-8ae5-71667575ab7c@kernel.org>
Date: Mon, 29 Dec 2025 13:46:06 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Robert Marko <robert.marko@...tura.hr>
Cc: Alexandre Belloni <alexandre.belloni@...tlin.com>, robh@...nel.org,
 krzk+dt@...nel.org, conor+dt@...nel.org, nicolas.ferre@...rochip.com,
 claudiu.beznea@...on.dev, herbert@...dor.apana.org.au, davem@...emloft.net,
 vkoul@...nel.org, andi.shyti@...nel.org, lee@...nel.org,
 andrew+netdev@...n.ch, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, linusw@...nel.org, Steen.Hegelund@...rochip.com,
 daniel.machon@...rochip.com, UNGLinuxDriver@...rochip.com,
 olivia@...enic.com, radu_nicolae.pirea@....ro, richard.genoud@...tlin.com,
 gregkh@...uxfoundation.org, jirislaby@...nel.org, broonie@...nel.org,
 mturquette@...libre.com, sboyd@...nel.org, lars.povlsen@...rochip.com,
 devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, linux-crypto@...r.kernel.org,
 dmaengine@...r.kernel.org, linux-i2c@...r.kernel.org,
 netdev@...r.kernel.org, linux-gpio@...r.kernel.org,
 linux-spi@...r.kernel.org, linux-serial@...r.kernel.org,
 linux-usb@...r.kernel.org, linux-clk@...r.kernel.org, luka.perkov@...tura.hr
Subject: Re: [PATCH v3 01/15] include: dt-bindings: add LAN969x clock bindings

On 29/12/2025 13:07, Robert Marko wrote:
>>>>>> I understand as not used by drivers? Then no ABI and there is no point
>>>>>> in putting them into bindings.
>>>>>
>>>>> It is not included by the driver directly, but it requires these exact
>>>>> indexes to be passed
>>>>> so its effectively ABI.
>>>>
>>>> How it requires the exact index? In what way? I do not see anything in
>>>> the gck driver using/relying on these values. Nothing. Please point me
>>>> to the line which directly uses these values.... or how many times I
>>>> will need to write this is not ABI?
>>>>
>>>
>>> The index here is the exact id that needs to be set in the PMC_PCR
>>> register and so it is dictated by the hardware.
>>
>> So not a binding between Linux and DTS.
>>
> 
> What would be your suggestion on moving forwarding regarding the clock
> HW indexes?

The same as for every other hardware constant, like interrupts,
registers and addresses - you use the value directly.

If you want nicer names, we moved them to DTS headers for several
platforms (see several commits in the past).

Best regards,
Krzysztof