mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2026-08-09 06:14:34 +02:00
Convert lan9303.txt to yaml format to fix below CHECK_DTBS warnings: arch/arm/boot/dts/nxp/imx/imx53-kp-hsc.dtb: /soc/bus@50000000/i2c@53fec000/switch@a: failed to match any schema with compatible: ['smsc,lan9303-i2c'] Additional changes: - rename switch-phy to switch in example. Reviewed-by: Rob Herring (Arm) <robh@kernel.org> Signed-off-by: Frank Li <Frank.Li@nxp.com> Link: https://patch.msgid.link/20260610150533.515914-1-Frank.Li@oss.nxp.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
38 lines
1.3 KiB
ReStructuredText
38 lines
1.3 KiB
ReStructuredText
==============================
|
|
LAN9303 Ethernet switch driver
|
|
==============================
|
|
|
|
The LAN9303 is a three port 10/100 Mbps ethernet switch with integrated phys for
|
|
the two external ethernet ports. The third port is an RMII/MII interface to a
|
|
host conduit network interface (e.g. fixed link).
|
|
|
|
|
|
Driver details
|
|
==============
|
|
|
|
The driver is implemented as a DSA driver, see ``Documentation/networking/dsa/dsa.rst``.
|
|
|
|
See ``Documentation/devicetree/bindings/net/dsa/smsc,lan9303.yaml`` for device tree
|
|
binding.
|
|
|
|
The LAN9303 can be managed both via MDIO and I2C, both supported by this driver.
|
|
|
|
At startup the driver configures the device to provide two separate network
|
|
interfaces (which is the default state of a DSA device). Due to HW limitations,
|
|
no HW MAC learning takes place in this mode.
|
|
|
|
When both user ports are joined to the same bridge, the normal HW MAC learning
|
|
is enabled. This means that unicast traffic is forwarded in HW. Broadcast and
|
|
multicast is flooded in HW. STP is also supported in this mode. The driver
|
|
support fdb/mdb operations as well, meaning IGMP snooping is supported.
|
|
|
|
If one of the user ports leave the bridge, the ports goes back to the initial
|
|
separated operation.
|
|
|
|
|
|
Driver limitations
|
|
==================
|
|
|
|
- Support for VLAN filtering is not implemented
|
|
- The HW does not support VLAN-specific fdb entries
|