From: Alexander Graf <agraf@suse.de>
To: Stuart Yoder <stuart.yoder@freescale.com>,
"arnd@arndb.de" <arnd@arndb.de>
Cc: Jose Rivera <German.Rivera@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 0/3 v6] drivers/bus: Freescale Management Complex bus driver patch series
Date: Thu, 26 Feb 2015 15:33:13 +0100 [thread overview]
Message-ID: <54EF2EA9.8080107@suse.de> (raw)
In-Reply-To: <CY1PR0301MB07489DAC1197846545E79F0587320@CY1PR0301MB0748.namprd03.prod.outlook.com>
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
next prev parent reply other threads:[~2015-02-26 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 1:01 [PATCH 0/3 v6] drivers/bus: Freescale Management Complex bus driver patch series J. German Rivera
2015-01-17 1:01 ` [PATCH 1/3 v6] drivers/bus: Added Freescale Management Complex APIs J. German Rivera
2015-01-17 1:01 ` [PATCH 2/3 v6] drivers/bus: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2015-01-17 1:01 ` [PATCH 3/3 v6] drivers/bus: Device driver for FSL-MC DPRC devices J. German Rivera
2015-01-27 14:35 ` [PATCH 0/3 v6] drivers/bus: Freescale Management Complex bus driver patch series Stuart Yoder
2015-02-26 14:33 ` Alexander Graf [this message]
2015-02-26 20:32 ` Stuart Yoder
2015-02-26 21:38 ` Alexander Graf
2015-02-26 22:25 ` Stuart Yoder
2015-02-26 22:31 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54EF2EA9.8080107@suse.de \
--to=agraf@suse.de \
--cc=German.Rivera@freescale.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stuart.yoder@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox