Messages in this thread | | | Date | Thu, 26 Feb 2015 15:33:13 +0100 | From | Alexander Graf <> | Subject | Re: [PATCH 0/3 v6] drivers/bus: Freescale Management Complex bus driver patch series |
| |
On 27.01.15 15:35, Stuart Yoder wrote: > Hi Arnd/Alex, > > German has posted an example driver for the fsl-mc bus in his RFC > "[RFC PATCH 1/1] drivers/bus: fsl-mc object allocator driver". > > In addition I have made available the skeleton for a driver for > one of the objects/devices (crypto) that will be discovered on > the bus: > https://github.com/stuyoder/linux > branch: fsl-ms-bus > > ...it is not functional yet, but shows how a driver registers with > the bus, get's probed, performs initialization.
Ok, so if I grasp this correctly the idea is that we have a driver attaching to an individual device on the fsl-mc bus. That driver then goes and allocates / blocks more devices from that bus as it initializes.
Is that model always possible? Which device would a NIC bind to for example? I merely want to make sure we're not running ourselves into a bad corner ;).
Alex
| |