From: Stuart Yoder <stuart.yoder@freescale.com>
To: Alexander Graf <agraf@suse.de>, "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
Thread-Topic: [PATCH 0/3 v6] drivers/bus: Freescale Management Complex bus
 driver patch series
Thread-Index: AQHQMfGjrcNvsyPegk6kHUFBdNRjCpzUEwHAgC8raICAAGIGcA==
Date: Thu, 26 Feb 2015 20:32:53 +0000
Message-ID: <CY1PR0301MB0748E8D278F27256473A6D1E87140@CY1PR0301MB0748.namprd03.prod.outlook.com>
References: <1421456477-27041-1-git-send-email-German.Rivera@freescale.com>
 <CY1PR0301MB07489DAC1197846545E79F0587320@CY1PR0301MB0748.namprd03.prod.outlook.com>
 <54EF2EA9.8080107@suse.de>
In-Reply-To: <54EF2EA9.8080107@suse.de>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Feb 2015 20:32:53.6291
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 710a03f5-10f6-4d38-9ff4-a80b81da590d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB1308
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2263
Lines: 67


> -----Original Message-----
> From: Alexander Graf [mailto:agraf@suse.de]
> Sent: Thursday, February 26, 2015 8:33 AM
> To: Yoder Stuart-B08248; arnd@arndb.de
> Cc: Rivera Jose-B46482; linux-kernel@vger.kernel.org; gregkh@linuxfoundation.org
> 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.

Yes.

> That driver then
> goes and allocates / blocks more devices from that bus as it initializes.

Yes, there are certain devices/objects on the bus that by themselves
are not standalone, functional devices.  An example is a "buffer pool".
Network interface drivers, crypto driver, decompression driver, etc need
one or more hardware buffer pools.  There is a buffer depletion interrupt
associated with the device.

The buffer pools itself binds to a resource allocation driver in
the kernel, which then can hand out buffer pools as required by
other drivers.

> Is that model always possible?

Yes, why would it not be?

> Which device would a NIC bind to for
> example?

Network interface / Ethernet driver requires some number
of buffer pools, plus a management complex portal device
(DPMCP) used for sending commands to manage the hardware.

> I merely want to make sure we're not running ourselves into a
> bad corner ;).

If we are, I would like to understand it. :)

Thanks,
Stuart
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/