-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'mscc-ocelot-add-support-for-SerDes-muxing-configuration'
Quentin Schulz says: ==================== mscc: ocelot: add support for SerDes muxing configuration The Ocelot switch has currently an hardcoded SerDes muxing that suits only a particular use case. Any other board setup will fail to work. To prepare for upcoming boards' support that do not have the same muxing, create a PHY driver that will handle all possible cases. A SerDes can work in SGMII, QSGMII or PCIe and is also muxed to use a given port depending on the selected mode or board design. The SerDes configuration is in the middle of an address space (HSIO) that is used to configure some parts in the MAC controller driver, that is why we need to use a syscon so that we can write to the same address space from different drivers safely using regmap. This breaks backward compatibility but it's fine because there's only one board at the moment that is using what's modified in this patch series. This will break git bisect. Even though this patch series is about SerDes __muxing__ configuration, the DT node is named serdes for the simple reason that I couldn't find any mention to SerDes anywhere else from the address space handled by this driver. v4: - add reviewed-by, - format the patch series with -M for identifying renamed files, - add parent info in DT binding of the SerDes IP, - move to macros SERDES[16]G(X) instead of multiple SERDES[16]G_[012345] constants, - move to SERDES[16]G_MAX being the last VALID macro of a type, so migrate to <= conditions instead of < when iterating, - create a SERDES_MUX_SGMII and SERDES_MUX_QSGMII macro so the muxing configurations are a tad more readable, - use a bunch of unsigned int instead of int, - return -EOPNOTSUPP for SERDES6G/PCIe until it's supported, - simplify condition when there is an error code returned by devm_of_phy_get, v3: - add Paul Burton's Acked-By on MIPS patches so that the patch series can be merged in the net tree in its entirety, v2: - use a switch case for setting the phy_mode in the SerDes driver as suggested by Andrew, - stop replacing the value of the error pointer in the SerDes driver, - use a dev_dbg for the deferring of the probe in the SerDes driver, - use constants in the Device Tree to select the SerDes macro in use with a port, - adapt the SerDes driver to use those constants, - add a header file in include/dt-bindings for the constants, - fix space/tab issue, ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
- Loading branch information
Showing
17 changed files
with
559 additions
and
180 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
43 changes: 43 additions & 0 deletions
43
Documentation/devicetree/bindings/phy/phy-ocelot-serdes.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
Microsemi Ocelot SerDes muxing driver | ||
------------------------------------- | ||
|
||
On Microsemi Ocelot, there is a handful of registers in HSIO address | ||
space for setting up the SerDes to switch port muxing. | ||
|
||
A SerDes X can be "muxed" to work with switch port Y or Z for example. | ||
One specific SerDes can also be used as a PCIe interface. | ||
|
||
Hence, a SerDes represents an interface, be it an Ethernet or a PCIe one. | ||
|
||
There are two kinds of SerDes: SERDES1G supports 10/100Mbps in | ||
half/full-duplex and 1000Mbps in full-duplex mode while SERDES6G supports | ||
10/100Mbps in half/full-duplex and 1000/2500Mbps in full-duplex mode. | ||
|
||
Also, SERDES6G number (aka "macro") 0 is the only interface supporting | ||
QSGMII. | ||
|
||
This is a child of the HSIO syscon ("mscc,ocelot-hsio", see | ||
Documentation/devicetree/bindings/mips/mscc.txt) on the Microsemi Ocelot. | ||
|
||
Required properties: | ||
|
||
- compatible: should be "mscc,vsc7514-serdes" | ||
- #phy-cells : from the generic phy bindings, must be 2. | ||
The first number defines the input port to use for a given | ||
SerDes macro. The second defines the macro to use. They are | ||
defined in dt-bindings/phy/phy-ocelot-serdes.h | ||
|
||
Example: | ||
|
||
serdes: serdes { | ||
compatible = "mscc,vsc7514-serdes"; | ||
#phy-cells = <2>; | ||
}; | ||
|
||
ethernet { | ||
port1 { | ||
phy-handle = <&phy_foo>; | ||
/* Link SERDES1G_5 to port1 */ | ||
phys = <&serdes 1 SERDES1G_5>; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.