Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour,
specifically:
* accessing switch register space;
* accessing per-PHY registers (for switches that actually expose PHYs);
* basic vlan group support, which applies for the rtl8366 driver but not
for the atheros switches.
This also includes initial support for:
* rtl8366rb support - which is a 10/100/1000 switch which supports
vlan groups;
* Initial Atheros AR8316 switch support - which is a 10/100/1000 switch
which supports an alternate vlan configuration (so the vlan group
methods are stubbed.)
The general idea here is that the switch driver may speak to a variety of
backend busses (mdio, i2c, spi, whatever) and expose:
* If applicable, one or more MDIO busses which ethernet interfaces can
then attach PHYs to via miiproxy/mdioproxy;
* exposes miibusses, one for each port at the moment, so ..
* .. a PHY can be exposed on each miibus, for each switch port, with all
of the existing MII/ifnet framework.
However:
* The ifnet is manually created for now, and it isn't linked into the
interface list, nor can you (currently) send/receive frames on this ifnet.
At some point in the future there may be _some_ support for this, for
switches with a multi-port, isolated mode.
* I'm still in the process of sorting out correct(er) locking.
TODO:
* ray's switch code in zrouter (zrouter.org) includes a much more developed
newbus API that covers the various switch methods, as well as a
capability API so drivers, the switch layer and the userland utility
can properly control the subset of supported features.
The plan is to sort that out later, once the rest of ray's switch drivers
are brought over and extended to export MII busses and PHYs.
Submitted by: Stefan Bethke <stb@lassitu.de>
Reviewed by: ray
2012-05-11 20:53:20 +00:00
|
|
|
/*
|
|
|
|
|
* $FreeBSD$
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef __SYS_DEV_ETHERSWITCH_ETHERSWITCH_H
|
|
|
|
|
#define __SYS_DEV_ETHERSWITCH_ETHERSWITCH_H
|
|
|
|
|
|
|
|
|
|
#include <sys/ioccom.h>
|
|
|
|
|
|
|
|
|
|
#ifdef _KERNEL
|
|
|
|
|
extern devclass_t etherswitch_devclass;
|
|
|
|
|
extern driver_t etherswitch_driver;
|
|
|
|
|
#endif /* _KERNEL */
|
|
|
|
|
|
|
|
|
|
struct etherswitch_reg {
|
|
|
|
|
uint16_t reg;
|
2016-08-04 17:45:35 +00:00
|
|
|
uint32_t val;
|
Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour,
specifically:
* accessing switch register space;
* accessing per-PHY registers (for switches that actually expose PHYs);
* basic vlan group support, which applies for the rtl8366 driver but not
for the atheros switches.
This also includes initial support for:
* rtl8366rb support - which is a 10/100/1000 switch which supports
vlan groups;
* Initial Atheros AR8316 switch support - which is a 10/100/1000 switch
which supports an alternate vlan configuration (so the vlan group
methods are stubbed.)
The general idea here is that the switch driver may speak to a variety of
backend busses (mdio, i2c, spi, whatever) and expose:
* If applicable, one or more MDIO busses which ethernet interfaces can
then attach PHYs to via miiproxy/mdioproxy;
* exposes miibusses, one for each port at the moment, so ..
* .. a PHY can be exposed on each miibus, for each switch port, with all
of the existing MII/ifnet framework.
However:
* The ifnet is manually created for now, and it isn't linked into the
interface list, nor can you (currently) send/receive frames on this ifnet.
At some point in the future there may be _some_ support for this, for
switches with a multi-port, isolated mode.
* I'm still in the process of sorting out correct(er) locking.
TODO:
* ray's switch code in zrouter (zrouter.org) includes a much more developed
newbus API that covers the various switch methods, as well as a
capability API so drivers, the switch layer and the userland utility
can properly control the subset of supported features.
The plan is to sort that out later, once the rest of ray's switch drivers
are brought over and extended to export MII busses and PHYs.
Submitted by: Stefan Bethke <stb@lassitu.de>
Reviewed by: ray
2012-05-11 20:53:20 +00:00
|
|
|
};
|
|
|
|
|
typedef struct etherswitch_reg etherswitch_reg_t;
|
|
|
|
|
|
|
|
|
|
struct etherswitch_phyreg {
|
|
|
|
|
uint16_t phy;
|
|
|
|
|
uint16_t reg;
|
|
|
|
|
uint16_t val;
|
|
|
|
|
};
|
|
|
|
|
typedef struct etherswitch_phyreg etherswitch_phyreg_t;
|
|
|
|
|
|
2013-05-08 20:46:54 +00:00
|
|
|
#define ETHERSWITCH_NAMEMAX 64
|
2013-07-23 13:56:38 +00:00
|
|
|
#define ETHERSWITCH_VID_MASK 0xfff
|
|
|
|
|
#define ETHERSWITCH_VID_VALID (1 << 12)
|
2013-05-08 20:46:54 +00:00
|
|
|
#define ETHERSWITCH_VLAN_ISL (1 << 0) /* ISL */
|
|
|
|
|
#define ETHERSWITCH_VLAN_PORT (1 << 1) /* Port based vlan */
|
|
|
|
|
#define ETHERSWITCH_VLAN_DOT1Q (1 << 2) /* 802.1q */
|
|
|
|
|
#define ETHERSWITCH_VLAN_DOT1Q_4K (1 << 3) /* 4k support on 802.1q */
|
|
|
|
|
#define ETHERSWITCH_VLAN_DOUBLE_TAG (1 << 4) /* Q-in-Q */
|
|
|
|
|
#define ETHERSWITCH_VLAN_CAPS_BITS \
|
|
|
|
|
"\020\1ISL\2PORT\3DOT1Q\4DOT1Q4K\5QinQ"
|
Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour,
specifically:
* accessing switch register space;
* accessing per-PHY registers (for switches that actually expose PHYs);
* basic vlan group support, which applies for the rtl8366 driver but not
for the atheros switches.
This also includes initial support for:
* rtl8366rb support - which is a 10/100/1000 switch which supports
vlan groups;
* Initial Atheros AR8316 switch support - which is a 10/100/1000 switch
which supports an alternate vlan configuration (so the vlan group
methods are stubbed.)
The general idea here is that the switch driver may speak to a variety of
backend busses (mdio, i2c, spi, whatever) and expose:
* If applicable, one or more MDIO busses which ethernet interfaces can
then attach PHYs to via miiproxy/mdioproxy;
* exposes miibusses, one for each port at the moment, so ..
* .. a PHY can be exposed on each miibus, for each switch port, with all
of the existing MII/ifnet framework.
However:
* The ifnet is manually created for now, and it isn't linked into the
interface list, nor can you (currently) send/receive frames on this ifnet.
At some point in the future there may be _some_ support for this, for
switches with a multi-port, isolated mode.
* I'm still in the process of sorting out correct(er) locking.
TODO:
* ray's switch code in zrouter (zrouter.org) includes a much more developed
newbus API that covers the various switch methods, as well as a
capability API so drivers, the switch layer and the userland utility
can properly control the subset of supported features.
The plan is to sort that out later, once the rest of ray's switch drivers
are brought over and extended to export MII busses and PHYs.
Submitted by: Stefan Bethke <stb@lassitu.de>
Reviewed by: ray
2012-05-11 20:53:20 +00:00
|
|
|
|
|
|
|
|
struct etherswitch_info {
|
|
|
|
|
int es_nports;
|
|
|
|
|
int es_nvlangroups;
|
|
|
|
|
char es_name[ETHERSWITCH_NAMEMAX];
|
2013-05-08 20:46:54 +00:00
|
|
|
uint32_t es_vlan_caps;
|
Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour,
specifically:
* accessing switch register space;
* accessing per-PHY registers (for switches that actually expose PHYs);
* basic vlan group support, which applies for the rtl8366 driver but not
for the atheros switches.
This also includes initial support for:
* rtl8366rb support - which is a 10/100/1000 switch which supports
vlan groups;
* Initial Atheros AR8316 switch support - which is a 10/100/1000 switch
which supports an alternate vlan configuration (so the vlan group
methods are stubbed.)
The general idea here is that the switch driver may speak to a variety of
backend busses (mdio, i2c, spi, whatever) and expose:
* If applicable, one or more MDIO busses which ethernet interfaces can
then attach PHYs to via miiproxy/mdioproxy;
* exposes miibusses, one for each port at the moment, so ..
* .. a PHY can be exposed on each miibus, for each switch port, with all
of the existing MII/ifnet framework.
However:
* The ifnet is manually created for now, and it isn't linked into the
interface list, nor can you (currently) send/receive frames on this ifnet.
At some point in the future there may be _some_ support for this, for
switches with a multi-port, isolated mode.
* I'm still in the process of sorting out correct(er) locking.
TODO:
* ray's switch code in zrouter (zrouter.org) includes a much more developed
newbus API that covers the various switch methods, as well as a
capability API so drivers, the switch layer and the userland utility
can properly control the subset of supported features.
The plan is to sort that out later, once the rest of ray's switch drivers
are brought over and extended to export MII busses and PHYs.
Submitted by: Stefan Bethke <stb@lassitu.de>
Reviewed by: ray
2012-05-11 20:53:20 +00:00
|
|
|
};
|
|
|
|
|
typedef struct etherswitch_info etherswitch_info_t;
|
|
|
|
|
|
2013-05-08 20:46:54 +00:00
|
|
|
#define ETHERSWITCH_CONF_FLAGS (1 << 0)
|
|
|
|
|
#define ETHERSWITCH_CONF_MIRROR (1 << 1)
|
|
|
|
|
#define ETHERSWITCH_CONF_VLAN_MODE (1 << 2)
|
|
|
|
|
|
|
|
|
|
struct etherswitch_conf {
|
|
|
|
|
uint32_t cmd; /* What to configure */
|
|
|
|
|
uint32_t vlan_mode; /* Switch VLAN mode */
|
|
|
|
|
};
|
|
|
|
|
typedef struct etherswitch_conf etherswitch_conf_t;
|
|
|
|
|
|
|
|
|
|
#define ETHERSWITCH_PORT_CPU (1 << 0)
|
|
|
|
|
#define ETHERSWITCH_PORT_STRIPTAG (1 << 1)
|
|
|
|
|
#define ETHERSWITCH_PORT_ADDTAG (1 << 2)
|
|
|
|
|
#define ETHERSWITCH_PORT_FIRSTLOCK (1 << 3)
|
|
|
|
|
#define ETHERSWITCH_PORT_DROPUNTAGGED (1 << 4)
|
|
|
|
|
#define ETHERSWITCH_PORT_DOUBLE_TAG (1 << 5)
|
|
|
|
|
#define ETHERSWITCH_PORT_INGRESS (1 << 6)
|
|
|
|
|
#define ETHERSWITCH_PORT_FLAGS_BITS \
|
|
|
|
|
"\020\1CPUPORT\2STRIPTAG\3ADDTAG\4FIRSTLOCK\5DROPUNTAGGED\6QinQ\7INGRESS"
|
|
|
|
|
|
2016-08-04 17:45:35 +00:00
|
|
|
#define ETHERSWITCH_PORT_MAX_LEDS 3
|
|
|
|
|
|
|
|
|
|
enum etherswitch_port_led {
|
|
|
|
|
ETHERSWITCH_PORT_LED_DEFAULT,
|
|
|
|
|
ETHERSWITCH_PORT_LED_ON,
|
|
|
|
|
ETHERSWITCH_PORT_LED_OFF,
|
|
|
|
|
ETHERSWITCH_PORT_LED_BLINK,
|
|
|
|
|
ETHERSWITCH_PORT_LED_MAX
|
|
|
|
|
};
|
|
|
|
|
typedef enum etherswitch_port_led etherswitch_port_led_t;
|
|
|
|
|
|
Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour,
specifically:
* accessing switch register space;
* accessing per-PHY registers (for switches that actually expose PHYs);
* basic vlan group support, which applies for the rtl8366 driver but not
for the atheros switches.
This also includes initial support for:
* rtl8366rb support - which is a 10/100/1000 switch which supports
vlan groups;
* Initial Atheros AR8316 switch support - which is a 10/100/1000 switch
which supports an alternate vlan configuration (so the vlan group
methods are stubbed.)
The general idea here is that the switch driver may speak to a variety of
backend busses (mdio, i2c, spi, whatever) and expose:
* If applicable, one or more MDIO busses which ethernet interfaces can
then attach PHYs to via miiproxy/mdioproxy;
* exposes miibusses, one for each port at the moment, so ..
* .. a PHY can be exposed on each miibus, for each switch port, with all
of the existing MII/ifnet framework.
However:
* The ifnet is manually created for now, and it isn't linked into the
interface list, nor can you (currently) send/receive frames on this ifnet.
At some point in the future there may be _some_ support for this, for
switches with a multi-port, isolated mode.
* I'm still in the process of sorting out correct(er) locking.
TODO:
* ray's switch code in zrouter (zrouter.org) includes a much more developed
newbus API that covers the various switch methods, as well as a
capability API so drivers, the switch layer and the userland utility
can properly control the subset of supported features.
The plan is to sort that out later, once the rest of ray's switch drivers
are brought over and extended to export MII busses and PHYs.
Submitted by: Stefan Bethke <stb@lassitu.de>
Reviewed by: ray
2012-05-11 20:53:20 +00:00
|
|
|
struct etherswitch_port {
|
|
|
|
|
int es_port;
|
2013-04-22 05:52:18 +00:00
|
|
|
int es_pvid;
|
2016-08-04 17:45:35 +00:00
|
|
|
int es_nleds;
|
2013-05-08 20:46:54 +00:00
|
|
|
uint32_t es_flags;
|
2016-08-04 17:45:35 +00:00
|
|
|
etherswitch_port_led_t es_led[ETHERSWITCH_PORT_MAX_LEDS];
|
Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour,
specifically:
* accessing switch register space;
* accessing per-PHY registers (for switches that actually expose PHYs);
* basic vlan group support, which applies for the rtl8366 driver but not
for the atheros switches.
This also includes initial support for:
* rtl8366rb support - which is a 10/100/1000 switch which supports
vlan groups;
* Initial Atheros AR8316 switch support - which is a 10/100/1000 switch
which supports an alternate vlan configuration (so the vlan group
methods are stubbed.)
The general idea here is that the switch driver may speak to a variety of
backend busses (mdio, i2c, spi, whatever) and expose:
* If applicable, one or more MDIO busses which ethernet interfaces can
then attach PHYs to via miiproxy/mdioproxy;
* exposes miibusses, one for each port at the moment, so ..
* .. a PHY can be exposed on each miibus, for each switch port, with all
of the existing MII/ifnet framework.
However:
* The ifnet is manually created for now, and it isn't linked into the
interface list, nor can you (currently) send/receive frames on this ifnet.
At some point in the future there may be _some_ support for this, for
switches with a multi-port, isolated mode.
* I'm still in the process of sorting out correct(er) locking.
TODO:
* ray's switch code in zrouter (zrouter.org) includes a much more developed
newbus API that covers the various switch methods, as well as a
capability API so drivers, the switch layer and the userland utility
can properly control the subset of supported features.
The plan is to sort that out later, once the rest of ray's switch drivers
are brought over and extended to export MII busses and PHYs.
Submitted by: Stefan Bethke <stb@lassitu.de>
Reviewed by: ray
2012-05-11 20:53:20 +00:00
|
|
|
union {
|
|
|
|
|
struct ifreq es_uifr;
|
|
|
|
|
struct ifmediareq es_uifmr;
|
|
|
|
|
} es_ifu;
|
|
|
|
|
#define es_ifr es_ifu.es_uifr
|
|
|
|
|
#define es_ifmr es_ifu.es_uifmr
|
|
|
|
|
};
|
|
|
|
|
typedef struct etherswitch_port etherswitch_port_t;
|
|
|
|
|
|
|
|
|
|
struct etherswitch_vlangroup {
|
|
|
|
|
int es_vlangroup;
|
|
|
|
|
int es_vid;
|
|
|
|
|
int es_member_ports;
|
|
|
|
|
int es_untagged_ports;
|
|
|
|
|
int es_fid;
|
|
|
|
|
};
|
|
|
|
|
typedef struct etherswitch_vlangroup etherswitch_vlangroup_t;
|
|
|
|
|
|
|
|
|
|
#define ETHERSWITCH_PORTMASK(_port) (1 << (_port))
|
|
|
|
|
|
|
|
|
|
#define IOETHERSWITCHGETINFO _IOR('i', 1, etherswitch_info_t)
|
|
|
|
|
#define IOETHERSWITCHGETREG _IOWR('i', 2, etherswitch_reg_t)
|
|
|
|
|
#define IOETHERSWITCHSETREG _IOW('i', 3, etherswitch_reg_t)
|
|
|
|
|
#define IOETHERSWITCHGETPORT _IOWR('i', 4, etherswitch_port_t)
|
|
|
|
|
#define IOETHERSWITCHSETPORT _IOW('i', 5, etherswitch_port_t)
|
|
|
|
|
#define IOETHERSWITCHGETVLANGROUP _IOWR('i', 6, etherswitch_vlangroup_t)
|
|
|
|
|
#define IOETHERSWITCHSETVLANGROUP _IOW('i', 7, etherswitch_vlangroup_t)
|
|
|
|
|
#define IOETHERSWITCHGETPHYREG _IOWR('i', 8, etherswitch_phyreg_t)
|
|
|
|
|
#define IOETHERSWITCHSETPHYREG _IOW('i', 9, etherswitch_phyreg_t)
|
2013-05-08 20:46:54 +00:00
|
|
|
#define IOETHERSWITCHGETCONF _IOR('i', 10, etherswitch_conf_t)
|
|
|
|
|
#define IOETHERSWITCHSETCONF _IOW('i', 11, etherswitch_conf_t)
|
Commit the first pass of the etherswitch support.
This is designed to support the very basic ethernet switch chip behaviour,
specifically:
* accessing switch register space;
* accessing per-PHY registers (for switches that actually expose PHYs);
* basic vlan group support, which applies for the rtl8366 driver but not
for the atheros switches.
This also includes initial support for:
* rtl8366rb support - which is a 10/100/1000 switch which supports
vlan groups;
* Initial Atheros AR8316 switch support - which is a 10/100/1000 switch
which supports an alternate vlan configuration (so the vlan group
methods are stubbed.)
The general idea here is that the switch driver may speak to a variety of
backend busses (mdio, i2c, spi, whatever) and expose:
* If applicable, one or more MDIO busses which ethernet interfaces can
then attach PHYs to via miiproxy/mdioproxy;
* exposes miibusses, one for each port at the moment, so ..
* .. a PHY can be exposed on each miibus, for each switch port, with all
of the existing MII/ifnet framework.
However:
* The ifnet is manually created for now, and it isn't linked into the
interface list, nor can you (currently) send/receive frames on this ifnet.
At some point in the future there may be _some_ support for this, for
switches with a multi-port, isolated mode.
* I'm still in the process of sorting out correct(er) locking.
TODO:
* ray's switch code in zrouter (zrouter.org) includes a much more developed
newbus API that covers the various switch methods, as well as a
capability API so drivers, the switch layer and the userland utility
can properly control the subset of supported features.
The plan is to sort that out later, once the rest of ray's switch drivers
are brought over and extended to export MII busses and PHYs.
Submitted by: Stefan Bethke <stb@lassitu.de>
Reviewed by: ray
2012-05-11 20:53:20 +00:00
|
|
|
|
|
|
|
|
#endif
|
