lkml.org 
[lkml]   [2015]   [Feb]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [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


\
 
 \ /
  Last update: 2015-02-26 15:41    [W:0.071 / U:1.748 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site