Cleanup mvebu_v7_defconfig and then add support for the Netgear
GS110EMX which is an 8 port Gigabit switch with two additional
Multi-Gig ports. An 88E6390X switch sits at its core connecting to two
88X3310P 10G PHYs while the control plane is handled by an 88F6811
Armada 381 SoC.
Marcel Ziswiler (4):
dt-bindings: net: dsa: marvell: fix compatible in example
ARM: mvebu_v7_defconfig: enable mtd physmap
ARM: mvebu_v7_defconfig: rebuild default configuration
ARM: dts: mvebu: add device tree for netgear gs110emx switch
.../devicetree/bindings/net/dsa/marvell.txt | 2 +-
arch/arm/boot/dts/Makefile | 1 +
.../boot/dts/armada-381-netgear-gs110emx.dts | 293 ++++++++++++++++++
arch/arm/configs/mvebu_v7_defconfig | 18 +-
4 files changed, 303 insertions(+), 11 deletions(-)
create mode 100644 arch/arm/boot/dts/armada-381-netgear-gs110emx.dts
--
2.26.2
While the MV88E6390 switch chip exists, one is supposed to use a
compatible of "marvell,mv88e6190" for it. Fix this in the given example.
Signed-off-by: Marcel Ziswiler <redacted>
---
Documentation/devicetree/bindings/net/dsa/marvell.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Run "make mvebu_v7_defconfig; make savedefconfig" to rebuild
mvebu_v7_defconfig
This re-ordered the following configuration options:
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_PCI=y
CONFIG_PCI_MVEBU=y
CONFIG_CRYPTO_DEV_MARVELL_CESA=y
And dropped the following nowadays obsolete configuration options:
CONFIG_ZBOOT_ROM_TEXT=0x0 (default now anyway since commit 39c3e304567a
("ARM: 8984/1: Kconfig: set default ZBOOT_ROM_TEXT/BSS value to 0x0"))
CONFIG_ZBOOT_ROM_BSS=0x0 (ditto)
CONFIG_MTD_M25P80=y (got integrated into MTD_SPI_NOR)
Signed-off-by: Marcel Ziswiler <redacted>
---
arch/arm/configs/mvebu_v7_defconfig | 17 +++++++----------
1 file changed, 7 insertions(+), 10 deletions(-)
@@ -14,13 +12,8 @@ CONFIG_MACH_ARMADA_38X=y CONFIG_MACH_ARMADA_39X=y CONFIG_MACH_ARMADA_XP=y CONFIG_MACH_DOVE=y-CONFIG_PCI=y-CONFIG_PCI_MVEBU=y CONFIG_SMP=y CONFIG_HIGHMEM=y-# CONFIG_COMPACTION is not set-CONFIG_ZBOOT_ROM_TEXT=0x0-CONFIG_ZBOOT_ROM_BSS=0x0 CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_CPU_FREQ=y
@@ -29,6 +22,9 @@ CONFIG_CPU_IDLE=y CONFIG_ARM_MVEBU_V7_CPUIDLE=y CONFIG_VFP=y CONFIG_NEON=y+CONFIG_MODULES=y+CONFIG_MODULE_UNLOAD=y+# CONFIG_COMPACTION is not set CONFIG_NET=y CONFIG_PACKET=y CONFIG_UNIX=y
@@ -147,10 +144,10 @@ CONFIG_NLS_CODEPAGE_850=y CONFIG_NLS_ISO8859_1=y CONFIG_NLS_ISO8859_2=y CONFIG_NLS_UTF8=y+CONFIG_CRYPTO_DEV_MARVELL_CESA=y CONFIG_PRINTK_TIME=y+# CONFIG_DEBUG_BUGVERBOSE is not set CONFIG_DEBUG_INFO=y CONFIG_MAGIC_SYSRQ=y # CONFIG_SCHED_DEBUG is not set-# CONFIG_DEBUG_BUGVERBOSE is not set CONFIG_DEBUG_USER=y-CONFIG_CRYPTO_DEV_MARVELL_CESA=y
Add the device tree for a Netgear GS110EMX switch featuring 8 Gigabit
ports and 2 Multi-Gig ports (100M/1G/2.5G/5G/10G). An 88E6390X switch
sits at its core connecting to two 88X3310P 10G PHYs. The control plane
is handled by an 88F6811 Armada 381 SoC.
The following functionality is tested:
- 8 gigabit Ethernet ports connecting via 88E6390X to the 88F6811
- serial console UART
- 128 MB commercial grade DDR3L SDRAM
- 16 MB serial SPI NOR flash
The two 88X3310P 10G PHYs while detected during boot seem neither to
detect any link nor pass any traffic.
Signed-off-by: Marcel Ziswiler <redacted>
---
arch/arm/boot/dts/Makefile | 1 +
.../boot/dts/armada-381-netgear-gs110emx.dts | 293 ++++++++++++++++++
2 files changed, 294 insertions(+)
create mode 100644 arch/arm/boot/dts/armada-381-netgear-gs110emx.dts
From: Andrew Lunn <andrew@lunn.ch> Date: 2021-10-05 12:49:14
On Tue, Oct 05, 2021 at 08:03:31AM +0200, Marcel Ziswiler wrote:
While the MV88E6390 switch chip exists, one is supposed to use a
compatible of "marvell,mv88e6190" for it. Fix this in the given example.
Signed-off-by: Marcel Ziswiler <redacted>
Fixes: a3c53be55c95 ("net: dsa: mv88e6xxx: Support multiple MDIO busses")
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Hi Marcel
Since this is a fix, it should be sent separately, and for net, not
net-next.
Thanks
Andrew
From: Andrew Lunn <andrew@lunn.ch> Date: 2021-10-05 12:54:59
On Tue, Oct 05, 2021 at 02:48:55PM +0200, Andrew Lunn wrote:
On Tue, Oct 05, 2021 at 08:03:31AM +0200, Marcel Ziswiler wrote:
quoted
While the MV88E6390 switch chip exists, one is supposed to use a
compatible of "marvell,mv88e6190" for it. Fix this in the given example.
Signed-off-by: Marcel Ziswiler <redacted>
Fixes: a3c53be55c95 ("net: dsa: mv88e6xxx: Support multiple MDIO busses")
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Hi Marcel
Since this is a fix, it should be sent separately, and for net, not
net-next.
From: Andrew Lunn <andrew@lunn.ch> Date: 2021-10-05 12:56:33
On Tue, Oct 05, 2021 at 08:03:33AM +0200, Marcel Ziswiler wrote:
Run "make mvebu_v7_defconfig; make savedefconfig" to rebuild
mvebu_v7_defconfig
This re-ordered the following configuration options:
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_PCI=y
CONFIG_PCI_MVEBU=y
CONFIG_CRYPTO_DEV_MARVELL_CESA=y
And dropped the following nowadays obsolete configuration options:
CONFIG_ZBOOT_ROM_TEXT=0x0 (default now anyway since commit 39c3e304567a
("ARM: 8984/1: Kconfig: set default ZBOOT_ROM_TEXT/BSS value to 0x0"))
CONFIG_ZBOOT_ROM_BSS=0x0 (ditto)
CONFIG_MTD_M25P80=y (got integrated into MTD_SPI_NOR)
Signed-off-by: Marcel Ziswiler <redacted>
You numbering of the phy labels is a bit confusing here. Both the port
and the PHY use reg=<1>. So i would use the label
switch0phy1: switch0phy1@1
Andrew