[U-Boot] [PATCH 1/7] net: mvpp2x: fix traffic stuck after PHY start error

2019-08-02 Thread nhed+uboot
From: Stefan Chulski Issue: - Network stuck if autonegotion fails Issue root cause: - During port open procedure if autonegotion fails, configuration of packet processor won't be finished and open procedure exits with error. - However this won't prevent u-boot network framework from calling

[U-Boot] [PATCH 7/7] net: mvpp2: use new MVMDIO driver

2019-08-02 Thread nhed+uboot
From: Nevo Hed An eralier commit in this changeset is taken from Marvells repos but was based on an MVMDIO implementation that never made it into U-Boot. With this patch the mvpp2 driver switches to use the new MVMDIO driver that is based on a more universal mdio-uclass implementation.

[U-Boot] [PATCH 6/7] arm64: mvebu: armada-cp110-*dtsi: add xmdio nodes

2019-08-02 Thread nhed+uboot
From: Nevo Hed Based on upstream-linux See https://github.com/torvalds/linux/commit/f66b2aff. However made the XSMI register window 0x16 (22) bytes per my reading of the functional spec. Similar commits in Marvels own repo bump it to 0x200 (512) bytes but I did not see the reasoning for that.

[U-Boot] Switch MVPP2 to use new MVMDIO

2019-08-02 Thread nhed+uboot
This patchset includes several commits form Marvell's downstream repo including Ken Ma's patch to replace the SMI implementation with his own Marvell MDIO impolementation. That MVMDIO implementation never made it to upstream and has since been re-implemented by Alex Marginean and seems to be in

[U-Boot] [PATCH 2/7] net: mvpp2: Replace SMI implementation with marvell MDIO API

2019-08-02 Thread nhed+uboot
From: Ken Ma Since marvell MDIO driver is added, SMI function implementation in mvpp2 driver can be removed and NETA driver can use marvell MDIO API directly. This replacement also fixes 2 old issues: 1. Each pp2 port device should have its own mdio bus field member since some pp2 ports may

[U-Boot] [PATCH 4/7] net: mvpp2: no deref null

2019-08-02 Thread nhed+uboot
From: Nevo Hed phy_dev ptr is set from return of phy_connect() and is used before test to see if NULL. Obviously since the test already sxists someoen made the determination that this NULL is possible. Signed-off-by: Nevo Hed --- drivers/net/mvpp2.c | 3 ++- 1 file changed, 2 insertions(+),

[U-Boot] [PATCH 5/7] net: mvpp2: allow MDIO registration for fixed links

2019-08-02 Thread nhed+uboot
From: Igal Liberman Currently, there are 2 valid cases for interface, PHY and mdio relation: - If an interface has PHY handler, it'll call mdio_mii_bus_get_from_phy(), which will register MDIO bus. - If we want to use fixed-link for an interface, PHY handle is not defined in the

[U-Boot] [PATCH 3/7] net: mvpp2: mark phy as invalid in case of missing appropriate driver

2019-08-02 Thread nhed+uboot
From: Grzegorz Jaszczyk If the phy doesn't match with any existing u-boot drivers the phy framework will connect it to generic one which uid == 0x. In this case act as if the phy wouldn't be declared in dts. Otherwise in case of 3310 (for which the driver doesn't exist) the link will be

[U-Boot] [PATCH v2 5/6] arm64: mvebu: armada-cp110-*dtsi: add xmdio nodes

2019-08-02 Thread nhed+uboot
From: Nevo Hed Based on upstream-linux See https://github.com/torvalds/linux/commit/f66b2aff. However made the XSMI register window 0x16 (22) bytes per my reading of the functional spec. Similar commits in Marvels own repo bump it to 0x200 (512) bytes but I did not see the reasoning for that.

[U-Boot] [PATCH v2 1/6] net: mvpp2x: fix traffic stuck after PHY start error

2019-08-02 Thread nhed+uboot
From: Stefan Chulski Issue: - Network stuck if autonegotion fails Issue root cause: - During port open procedure if autonegotion fails, configuration of packet processor won't be finished and open procedure exits with error. - However this won't prevent u-boot network framework from calling

[U-Boot] [PATCH v2 2/6] net: mvpp2: Replace SMI implementation with marvell MDIO API

2019-08-02 Thread nhed+uboot
From: Ken Ma Since marvell MDIO driver is added, SMI function implementation in mvpp2 driver can be removed and NETA driver can use marvell MDIO API directly. This replacement also fixes 2 old issues: 1. Each pp2 port device should have its own mdio bus field member since some pp2 ports may

[U-Boot] [PATCH v2 3/6] net: mvpp2: mark phy as invalid in case of missing appropriate driver

2019-08-02 Thread nhed+uboot
From: Grzegorz Jaszczyk If the phy doesn't match with any existing u-boot drivers the phy framework will connect it to generic one which uid == 0x. In this case act as if the phy wouldn't be declared in dts. Otherwise in case of 3310 (for which the driver doesn't exist) the link will be

[U-Boot] [PATCH v2 4/6] net: mvpp2: no deref null

2019-08-02 Thread nhed+uboot
From: Nevo Hed phy_dev ptr is set from return of phy_connect() and is used before test to see if NULL. Obviously since the test already sxists someoen made the determination that this NULL is possible. Signed-off-by: Nevo Hed --- drivers/net/mvpp2.c | 3 ++- 1 file changed, 2 insertions(+),

[U-Boot] [PATCH v2 6/6] net: mvpp2: use new MVMDIO driver

2019-08-02 Thread nhed+uboot
From: Nevo Hed An eralier commit in this changeset is taken from Marvells repos but was based on an MVMDIO implementation that never made it into U-Boot. With this patch the mvpp2 driver switches to use the new MVMDIO driver that is based on a more universal mdio-uclass implementation.

[U-Boot] [PATCH v2 0/6] Switch MVPP2 to use new MVMDIO

2019-08-02 Thread nhed+uboot
From: Nevo Hed This patchset includes several commits form Marvell's downstream repo including Ken Ma's patch to replace the SMI implementation with his own Marvell MDIO impolementation. That MVMDIO implementation never made it to upstream and has since been re-implemented by Alex Marginean and

[U-Boot] [PATCH v4 1/5] net: mvpp2x: fix traffic stuck after PHY start error

2019-08-15 Thread nhed+uboot
From: Stefan Chulski Issue: - Network stuck if autonegotion fails. Issue root cause: - When autonegotiation fails during port open procedure, the packet processor configuration does not finish and open procedure exits with error. - However, this doesn't prevent u-boot network framework

[U-Boot] [PATCH v4 4/5] net: mvpp2: use new MVMDIO driver

2019-08-15 Thread nhed+uboot
From: Nevo Hed This commit ports mvpp2 to use the recently introduced Marvell MDIO (MVMDIO) driver. It removes direct interaction with the SMI & XSMI busses. This commit is based in part on earlier work by Ken Ma in Marvell's own downstream repo:

[U-Boot] [PATCH v4 3/5] arm: dts: armada-cp110-*dtsi: add xmdio nodes

2019-08-15 Thread nhed+uboot
From: Nevo Hed Based on upstream-linux See https://github.com/torvalds/linux/commit/f66b2aff. However made the XSMI register window 0x16 (22) bytes per my reading of the functional spec. Similar commits in Marvels own repo bump it to 0x200 (512) bytes but I did not see the reasoning for that.

[U-Boot] [PATCH v4 2/5] net: mvpp2: mark phy as invalid in case of missing appropriate driver

2019-08-15 Thread nhed+uboot
From: Grzegorz Jaszczyk If the phy doesn't match with any existing u-boot drivers, the phy framework will connect it to the generic one which uid == 0x. In this case, act as if the phy wouldn't be declared in dts. Otherwise, in case of 3310 (for which the driver doesn't exist) the link

[U-Boot] [PATCH v4 0/5] Switch MVPP2 to use new MVMDIO

2019-08-15 Thread nhed+uboot
From: Nevo Hed This patchset includes a couple of commits form Marvell's downstream repo and a change to replace mvpp2's SMI implementation with the new MVMDIO driver. The mvpp2 change is based partially on Ken Ma's mods against an earlier (his) version of MVMDIO that never made it to upstream

[U-Boot] [PATCH v4 5/5] net: mvpp2: MVPP2 now needs MVMDIO

2019-08-15 Thread nhed+uboot
From: Nevo Hed Changes to mvpp2.c require the MVMDIO module which in turn uses DM_MDIO. Signed-off-by: Nevo Hed --- drivers/net/Kconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig index 5fd31b03cf..81f39d0928 100644 --- a/drivers/net/Kconfig

[U-Boot] [PATCH v3 0/7] Switch MVPP2 to use new MVMDIO

2019-08-06 Thread nhed+uboot
From: Nevo Hed This patchset includes several commits form Marvell's downstream repo including Ken Ma's patch to replace the SMI implementation with his own Marvell MDIO impolementation. That MVMDIO implementation never made it to upstream and has since been re-implemented by Alex Marginean and

[U-Boot] [PATCH v3 1/7] net: mvpp2x: fix traffic stuck after PHY start error

2019-08-06 Thread nhed+uboot
From: Stefan Chulski Issue: - Network stuck if autonegotion fails. Issue root cause: - When autonegotiation fails during port open procedure, the packet processor configuration does not finish and open procedure exits with error. - However, this doesn't prevent u-boot network framework

[U-Boot] [PATCH v3 2/7] net: mvpp2: Replace SMI implementation with marvell MDIO API

2019-08-06 Thread nhed+uboot
From: Ken Ma The availability of the marvell MDIO driver enables us to eliminate the SMI function implementation within the mvpp2 driver. This replacement also fixes 2 old issues: 1. Each pp2 port device now has its own mdio bus field member since some pp2 ports may use SMI mdio bus while

[U-Boot] [PATCH v3 7/7] net: mvpp2: MVPP2 now needs MVMDIO

2019-08-06 Thread nhed+uboot
From: Nevo Hed Changes to mvpp2.c require the MVMDIO module which in turn uses DM_MDIO. Signed-off-by: Nevo Hed --- drivers/net/Kconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig index 5fd31b03cf..81f39d0928 100644 --- a/drivers/net/Kconfig

[U-Boot] [PATCH v3 6/7] net: mvpp2: use new MVMDIO driver

2019-08-06 Thread nhed+uboot
From: Nevo Hed An earlier commit in this changeset is taken from Marvells repos but was based on an MVMDIO implementation that never made it into U-Boot. With this patch the mvpp2 driver switches to use the new MVMDIO driver that is based on a more universal mdio-uclass implementation.

[U-Boot] [PATCH v3 3/7] net: mvpp2: mark phy as invalid in case of missing appropriate driver

2019-08-06 Thread nhed+uboot
From: Grzegorz Jaszczyk If the phy doesn't match with any existing u-boot drivers, the phy framework will connect it to the generic one which uid == 0x. In this case, act as if the phy wouldn't be declared in dts. Otherwise, in case of 3310 (for which the driver doesn't exist) the link

[U-Boot] [PATCH v3 5/7] arm: dts: armada-cp110-*dtsi: add xmdio nodes

2019-08-06 Thread nhed+uboot
From: Nevo Hed Based on upstream-linux See https://github.com/torvalds/linux/commit/f66b2aff. However made the XSMI register window 0x16 (22) bytes per my reading of the functional spec. Similar commits in Marvels own repo bump it to 0x200 (512) bytes but I did not see the reasoning for that.

[U-Boot] [PATCH v3 4/7] net: mvpp2: no deref null

2019-08-06 Thread nhed+uboot
From: Nevo Hed phy_dev ptr is set from return of phy_connect() and is used before test to see if NULL. Obviously since the test already sxists someone made the determination that this NULL is possible. Signed-off-by: Nevo Hed --- drivers/net/mvpp2.c | 3 ++- 1 file changed, 2 insertions(+),