summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide/binfmt-misc.rst
diff options
context:
space:
mode:
authorVladimir Oltean <vladimir.oltean@nxp.com>2022-08-18 14:54:52 +0300
committerJakub Kicinski <kuba@kernel.org>2022-08-23 03:45:45 +0300
commitb975b73425cde436f3e66e4cd992f6e6fb0998e5 (patch)
tree037e38a9554e42f3a13aec37da858ebcd19ddd42 /Documentation/admin-guide/binfmt-misc.rst
parentb237676039d9f5f3a2a75bc258c3723940f697df (diff)
downloadlinux-b975b73425cde436f3e66e4cd992f6e6fb0998e5.tar.xz
dt-bindings: net: dsa: hellcreek: add missing CPU port phy-mode/fixed-link to example
Looking at hellcreek_phylink_get_caps(), I see that depending on whether is_100_mbits is set, speeds of 1G or of 100M will be advertised. The de1soc_r1_pdata sets is_100_mbits to true. The PHY modes declared in the capabilities are MII, RGMII and GMII. GMII doesn't support 100Mbps, and as for RGMII, it would be a bit implausible to me to support this PHY mode but limit it to only 25 MHz. So I've settled on MII as a phy-mode in the example, and a fixed-link of 100Mbps. As a side note, there exists such a thing as "rev-mii", because the MII protocol is asymmetric, and "mii" is the designation for the MAC side (expected to be connected to a PHY), and "rev-mii" is the designation for the PHY side (expected to be connected to a MAC). I wonder whether "mii" or "rev-mii" should actually be used here, since this is a CPU port and presumably connected to another MAC. Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com> Acked-by: Rob Herring <robh@kernel.org> Reviewed-by: Kurt Kanzenbach <kurt@linutronix.de> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'Documentation/admin-guide/binfmt-misc.rst')
0 files changed, 0 insertions, 0 deletions