linux-hardening - Re: [PATCH 16/28] dt-bindings: dpll: Add support for Microchip Azurite chip family

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <b65daab2-8184-45f4-af18-8499e80fbc04@kernel.org>
Date: Thu, 10 Apr 2025 09:01:12 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ivan Vecera <ivecera@...hat.com>, netdev@...r.kernel.org
Cc: Michal Schmidt <mschmidt@...hat.com>,
 Vadim Fedorenko <vadim.fedorenko@...ux.dev>,
 Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>,
 Jiri Pirko <jiri@...nulli.us>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Prathosh Satish <Prathosh.Satish@...rochip.com>,
 Lee Jones <lee@...nel.org>, Kees Cook <kees@...nel.org>,
 Andy Shevchenko <andy@...nel.org>, Andrew Morton
 <akpm@...ux-foundation.org>, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH 16/28] dt-bindings: dpll: Add support for Microchip
 Azurite chip family

On 09/04/2025 09:19, Ivan Vecera wrote:
>>> +
>>> +maintainers:
>>> +  - Ivan Vecera <ivecera@...hat.com>
>>> +
>>> +properties:
>>> +  compatible:
>>> +    enum:
>>> +      - microchip,zl3073x-i2c
>>> +      - microchip,zl3073x-spi
>>
>> 1. No, you do not get two compatibles. Only one.
> 
> Will split to two files, one for i2c and one for spi.

No. One device, one compatible.

> 
>> 2. What is 'x'? Wildcard? If so, drop and use specific compatibles.
> 
> Microchip refers to the ZL3073x as a family of compatible DPLL chips 
> with the same features. There is no need to introduce separate 
> compatible string for each of them.

So a wildcard, thus drop. Use full product names. Google search gives me
no products for ZL3073x but gives me ZL30735.

> 
>>> +
>>> +  reg:
>>> +    maxItems: 1
>>> +
>>> +required:
>>> +  - compatible
>>> +  - reg
>>> +
>>> +allOf:
>>> +  - $ref: /schemas/dpll/dpll-device.yaml
>>> +
>>> +unevaluatedProperties: false
>>> +
>>> +examples:
>>> +  - |
>>> +    i2c {
>>> +      #address-cells = <1>;
>>> +      #size-cells = <0>;
>>> +
>>> +      dpll@70 {
>>> +        compatible = "microchip,zl3073x-i2c";
>>
>>> +        #address-cells = <0>;
>>> +        #size-cells = <0>;
>>
>> Again, why do you need them if you are not using these two?
> 
> The dpll-device.yaml defines them as required. Shouldn't they be 
> specified explicitly?

But you do not use them. Where is any child node?

> 
>>> +        reg = <0x70>;
>>> +        status = "okay";
>>
>> Drop
Best regards,
Krzysztof