On 11/29/2017 01:28 PM, Linus Walleij wrote: > On Wed, Nov 29, 2017 at 4:56 PM, Andrew Lunn <andrew@xxxxxxx> wrote: >>> I have the phy-handle in the ethernet controller. This RTL8366RB >>> thing is just one big PHY as far as I know. >> >> We don't model switches as PHYs. They are their own device type. And >> the internal or external PHYs are just normal PHYs in the linux >> model. Meaning their interrupt properties goes in the PHY node in >> device tree, as documented in the phy.txt binding documentation. > > I do model the PHYs on the switch as PHYs. > They are using the driver in drivers/phy/realtek.c. That's good. > > The interrupts are assigned to the PHYs not to the Switch. > Just that the PHYs are on the MDIO bus inside the switch, of > course. > > The switch however provides an irqchip to demux the interrupts. > > I think there is some misunderstanding in what I'm trying to do.. > > I have tried learning the DSA ideas by reading e.g. your paper: > https://www.netdevconf.org/2.1/papers/distributed-switch-architecture.pdf > > So I try my best to conform with these ideas. > > I however have a hard time testing things since I don't really have a > system to compare to. What would be useful is to know how > commands like "ip" and "ifconfig" are used on a typical > say home router. There is a mock-up driver: drivers/net/dsa/dsa_loop.c which does not pass any packets, but at least allows you to exercise user-space tools and so on. -- Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
