[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180730133448.GD13198@lunn.ch>
Date: Mon, 30 Jul 2018 15:34:48 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Quentin Schulz <quentin.schulz@...tlin.com>
Cc: alexandre.belloni@...tlin.com, ralf@...ux-mips.org,
paul.burton@...s.com, jhogan@...nel.org, robh+dt@...nel.org,
mark.rutland@....com, davem@...emloft.net, kishon@...com,
f.fainelli@...il.com, linux-mips@...ux-mips.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, allan.nielsen@...rosemi.com,
thomas.petazzoni@...tlin.com
Subject: Re: [PATCH 07/10] dt-bindings: phy: add DT binding for Microsemi
Ocelot SerDes muxing
> +Required properties:
> +
> +- compatible: should be "mscc,vsc7514-serdes"
> +- #phy-cells : from the generic phy bindings, must be 3. The first number
> + defines the kind of Serdes (1 for SERDES1G_X, 6 for
> + SERDES6G_X), the second defines the macros in the specified
> + kind of Serdes (X for SERDES1G_X or SERDES6G_X) and the
> + last one defines the input port to use for a given SerDes
> + macro,
It looks like there are some space vs tab issues here.
> +
> +Example:
> +
> + serdes: serdes {
Maybe this should be serdes-mux? The SERDES itself should have some
registers somewhere. If you ever decide to make use of phylink,
e.g. to support SFP, you are going to need to know if the SERDES is
up. So you might need to add the actual SERDES device, in addition to
the mux for the SERDES.
> + compatible = "mscc,vsc7514-serdes";
> + #phy-cells = <3>;
> + };
Powered by blists - more mailing lists