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
| ||
|
Date: Wed, 3 Jul 2019 23:33:27 +0200 From: Andrew Lunn <andrew@...n.ch> To: Rob Herring <robh+dt@...nel.org> Cc: Matthias Kaehlcke <mka@...omium.org>, "David S . Miller" <davem@...emloft.net>, Mark Rutland <mark.rutland@....com>, Florian Fainelli <f.fainelli@...il.com>, Heiner Kallweit <hkallweit1@...il.com>, netdev <netdev@...r.kernel.org>, devicetree@...r.kernel.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Douglas Anderson <dianders@...omium.org> Subject: Re: [PATCH v2 1/7] dt-bindings: net: Add bindings for Realtek PHYs > I think if we're going to have custom properties for phys, we should > have a compatible string to at least validate whether the custom > properties are even valid for the node. Hi Rob What happens with other enumerable busses where a compatible string is not used? The Ethernet PHY subsystem will ignore the compatible string and load the driver which fits the enumeration data. Using the compatible string only to get the right YAML validator seems wrong. I would prefer adding some other property with a clear name indicates its is selecting the validator, and has nothing to do with loading the correct driver. And it can then be used as well for USB and PCI devices etc. Andrew
Powered by blists - more mailing lists