From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932326AbbBZOdR (ORCPT ); Thu, 26 Feb 2015 09:33:17 -0500 Received: from cantor2.suse.de ([195.135.220.15]:47785 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932124AbbBZOdQ (ORCPT ); Thu, 26 Feb 2015 09:33:16 -0500 Message-ID: <54EF2EA9.8080107@suse.de> Date: Thu, 26 Feb 2015 15:33:13 +0100 From: Alexander Graf User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Stuart Yoder , "arnd@arndb.de" CC: Jose Rivera , "linux-kernel@vger.kernel.org" , "gregkh@linuxfoundation.org" Subject: Re: [PATCH 0/3 v6] drivers/bus: Freescale Management Complex bus driver patch series References: <1421456477-27041-1-git-send-email-German.Rivera@freescale.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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