On 25/09/2021 00:20, Florian Fainelli wrote:
On 9/24/21 2:02 PM, Arınç ÜNAL wrote:
Quoting Documentation/devicetree/bindings/net/dsa/realtek-smi.txt for
further reference.
Realtek SMI-based Switches
==========================
The SMI "Simple Management Interface" is a two-wire protocol using
bit-banged GPIO that while it reuses the MDIO lines MCK and MDIO does
not use the MDIO protocol. This binding defines how to specify the
SMI-based Realtek devices.
Ah this is the key here, using the MDIO controller won't work sorry
about misleading you. I suppose you will have to go back to the previous
Device Tree representation you had, but change the dsa,member property
and then you should be in business baring additional bugs/features.
All good. After fixing "dsa,member" on the original specification, the
log slightly changed. I'm going to see if I can switch to the net-next
kernel on OpenWrt to test the driver further. Something might be wrong
with my backport.
[ 1.377530] realtek-smi switch@1: failed to get RESET GPIO
---
[ 2.759267] realtek-smi switch@1: deasserted RESET
[ 2.764927] realtek-smi switch@1: found an RTL8365MB-VC switch
(ver=0x0040)
[ 2.771956] realtek-smi switch@1: unable to register switch ret = -517
---
[ 3.149262] realtek-smi switch@1: deasserted RESET
[ 3.154906] realtek-smi switch@1: found an RTL8365MB-VC switch
(ver=0x0040)
[ 3.287052] realtek-smi switch@1: failed to get parent irq: -22
[ 3.293060] realtek-smi switch@1: no interrupt support
[ 3.298211] realtek-smi switch@1: no MDIO bus node
[ 3.303025] realtek-smi switch@1: could not set up MDIO bus
[ 3.308648] realtek-smi switch@1: unable to register switch ret = -19