On 05/12/2019 19:59, Rob Herring wrote:
On Wed, Nov 27, 2019 at 9:39 AM Grygorii Strashko <grygorii.strashko@xxxxxx> wrote:Use non vendor specific compatible string in example, otherwise DT YAML schemas validation may trigger warnings specific to TI ti,davinci_mdio and not to the generic MDIO example. Signed-off-by: Grygorii Strashko <grygorii.strashko@xxxxxx> --- Documentation/devicetree/bindings/net/mdio.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/net/mdio.yaml b/Documentation/devicetree/bindings/net/mdio.yaml index 5d08d2ffd4eb..524f062c6973 100644 --- a/Documentation/devicetree/bindings/net/mdio.yaml +++ b/Documentation/devicetree/bindings/net/mdio.yaml @@ -56,7 +56,7 @@ patternProperties: examples: - | davinci_mdio: mdio@5c030000 { - compatible = "ti,davinci_mdio"; + compatible = "vendor,mdio";The problem with this is eventually 'vendor,mdio' will get flagged as an undocumented compatible. We're a ways off from being able to enable that until we have a majority of bindings converted. Though maybe examples can be enabled sooner rather than later.
May be some generic compatible string be used for all examples, like: "vendor,example-ip". What do you think? -- Best regards, grygorii
