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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 29 Jan 2022 17:52:35 -0300
From:   Luiz Angelo Daros de Luca <>
To:     Arınç ÜNAL <>
Cc:     Rob Herring <>,
        Alvin Šipraga <>,
        Linus Walleij <>,, Arnd Bergmann <>,
        Olof Johansson <>,
        Florian Fainelli <>,
        Stephen Rothwell <>,
        Andrew Lunn <>,
        Vivien Didelot <>,
        Vladimir Oltean <>,
        "David S . Miller" <>,
        Jakub Kicinski <>,
        "open list:NETWORKING DRIVERS" <>,
        open list <>
Subject: Re: [PATCH] dt-bindings: net: dsa: realtek-smi: convert to YAML schema

> Why not turn realtek-smi.yaml into realtek.yaml which would also contain
> information for the mdio interface? The things different with using MDIO
> are that we don't use the [mdc,mdio,reset]-gpios properties and don't
> handle the PHYs to the DSA ports. Couldn't you present these differences
> on a single YAML file?

Hello, Arinç

realtek-mdio is an mdio driver with a couple of less properties. They
do share a lot of stuff. But I don't know if I can fit the schema
validation into a single file.
YAML files are not simply documentation. They are used to validate DTS
files. But that's still off-topic. Let's finish SMI version first and
then discuss
if the MDIO version should be standalone or merged with SMI.


Powered by blists - more mailing lists