On 01/10/2017 01:21 PM, Andrew Lunn wrote: >> Last time we discussed this, I had a super complex dsa2_platform_data >> that allowed you to do exactly the same thing we currently do with >> Device Tree, except that this was with platform_data. It took a lot of >> effort to get there, but I essentially had the ZII vf160 board example >> re-implemented and verified with a mockup driver (still have it in a >> branch that's not too far from net-next/master). > > One thing different this time is you have associated the platform data > to an MDIO device. So the platform data represents one switch, not the > whole complex. This is going to make the platform data much simpler, > and allow the core to do the work of assembling the multiple platform > datas into one switch complex. So basically, the platform data is > dsa_chip_data. > > To handle multi-CPUs, we need to move the master ethernet device and > put it next to the cpu port. So add a > > struct device *netdev[DSA_MAX_PORTS]; > > to dsa_chip_data. It then becomes easy to represent multiple CPU > ports.
Alright, let me get that prepared then, thanks! > >> I would very much like to see the patches and then make a decision based >> on the submission rather than project a decision on code that has not >> been submitted yet. > > The first version was posted a week ago. I requested a lot of > changes. So lets see what John says about when the next version will > be ready. Oh that series, okay, somehow I thought you were referring to something else. -- Florian
