From: Arnd Bergmann <arnd@arndb.de>
To: "Arend van Spriel" <arend@broadcom.com>
Cc: "Greg KH" <greg@kroah.com>, "Rafał Miłecki" <zajec5@gmail.com>,
"George Kashperko" <george@znau.edu.ua>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Russell King" <rmk@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Jonas Gorski" <jonas.gorski@gmail.com>,
"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
"Andy Botting" <andy@andybotting.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: Re: Could I (ab)use bus (struct bus_type) for virtual Broadcom bus?
Date: Wed, 20 Apr 2011 08:44:10 +0200 [thread overview]
Message-ID: <201104200844.10607.arnd@arndb.de> (raw)
In-Reply-To: <op.vt74sxvp3ri7v4@arend-laptop>
On Wednesday 20 April 2011 08:39:59 Arend van Spriel wrote:
> On Tue, 19 Apr 2011 16:02:57 +0200, Greg KH <greg@kroah.com> wrote:
>
> > Please don't use a platform device, unless there is no other way for
> > your device to work. For this device, you are connected to the PCI bus,
> > so a platform device does not make sense at all.
>
> Hi Greg,
>
> This is only true for a particular usage model. There are two models as
> shown below:
>
> 1) PCI(e) card
> ...........
> +----------+ : x y z : x, y, and z are cores.
> | uC |__________:___|_|_| :
> | | PCI-bus : axi-bus :
> +----------+ :.........:
> bcm chipset
>
> 2) SoC
> ...............
> : uC x y z :
> : |____|_|_| :
> : axi-bus :
> :.............:
> bcm chipset
>
> Your statement is true for 1) but in usage model 2) there is no PCI bus.
> Also you refer to the chipset when you say 'device'. In the axi bus type
> each individual core is registered as a device in the linux device tree.
I guess what Greg was referring to is having platform devices for x/y/z
here. In case 2, you might still need to have a platform_device for the
combination of the three IP cores if they make up one logical device.
As mentioned in my reply, it depends a lot on what these cores actually
are, e.g. whether you might want to have only one of them active in a
given system to drive a specific functionality, or if you always need
all three of them.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Could I (ab)use bus (struct bus_type) for virtual Broadcom bus?
Date: Wed, 20 Apr 2011 08:44:10 +0200 [thread overview]
Message-ID: <201104200844.10607.arnd@arndb.de> (raw)
In-Reply-To: <op.vt74sxvp3ri7v4@arend-laptop>
On Wednesday 20 April 2011 08:39:59 Arend van Spriel wrote:
> On Tue, 19 Apr 2011 16:02:57 +0200, Greg KH <greg@kroah.com> wrote:
>
> > Please don't use a platform device, unless there is no other way for
> > your device to work. For this device, you are connected to the PCI bus,
> > so a platform device does not make sense at all.
>
> Hi Greg,
>
> This is only true for a particular usage model. There are two models as
> shown below:
>
> 1) PCI(e) card
> ...........
> +----------+ : x y z : x, y, and z are cores.
> | uC |__________:___|_|_| :
> | | PCI-bus : axi-bus :
> +----------+ :.........:
> bcm chipset
>
> 2) SoC
> ...............
> : uC x y z :
> : |____|_|_| :
> : axi-bus :
> :.............:
> bcm chipset
>
> Your statement is true for 1) but in usage model 2) there is no PCI bus.
> Also you refer to the chipset when you say 'device'. In the axi bus type
> each individual core is registered as a device in the linux device tree.
I guess what Greg was referring to is having platform devices for x/y/z
here. In case 2, you might still need to have a platform_device for the
combination of the three IP cores if they make up one logical device.
As mentioned in my reply, it depends a lot on what these cores actually
are, e.g. whether you might want to have only one of them active in a
given system to drive a specific functionality, or if you always need
all three of them.
Arnd
next prev parent reply other threads:[~2011-04-20 6:44 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 11:28 Could I (ab)use bus (struct bus_type) for virtual Broadcom bus? Rafał Miłecki
2011-04-14 11:28 ` Rafał Miłecki
2011-04-14 11:28 ` Rafał Miłecki
2011-04-14 11:43 ` George Kashperko
2011-04-14 11:43 ` George Kashperko
2011-04-14 12:04 ` Rafał Miłecki
2011-04-14 12:04 ` Rafał Miłecki
2011-04-14 12:04 ` Rafał Miłecki
2011-04-14 12:34 ` Hauke Mehrtens
2011-04-14 12:34 ` Hauke Mehrtens
2011-04-14 12:34 ` Hauke Mehrtens
2011-04-14 13:07 ` Rafał Miłecki
2011-04-14 13:07 ` Rafał Miłecki
2011-04-14 13:07 ` Rafał Miłecki
2011-04-14 13:15 ` George Kashperko
2011-04-14 13:15 ` George Kashperko
2011-04-14 13:45 ` Rafał Miłecki
2011-04-14 13:45 ` Rafał Miłecki
2011-04-14 13:45 ` Rafał Miłecki
2011-04-15 18:36 ` George Kashperko
2011-04-15 18:36 ` George Kashperko
2011-04-15 19:21 ` Rafał Miłecki
2011-04-15 19:21 ` Rafał Miłecki
2011-04-15 19:21 ` Rafał Miłecki
2011-04-15 19:42 ` George Kashperko
2011-04-15 19:42 ` George Kashperko
2011-04-15 19:52 ` Rafał Miłecki
2011-04-15 19:52 ` Rafał Miłecki
2011-04-15 19:52 ` Rafał Miłecki
2011-04-15 19:56 ` Peter Stuge
2011-04-15 19:56 ` Peter Stuge
2011-04-15 19:56 ` Peter Stuge
2011-04-16 14:00 ` Rafał Miłecki
2011-04-16 14:00 ` Rafał Miłecki
2011-04-16 14:00 ` Rafał Miłecki
2011-04-16 14:13 ` Jonas Gorski
2011-04-16 14:13 ` Jonas Gorski
2011-04-16 14:13 ` Jonas Gorski
2011-04-15 19:50 ` George Kashperko
2011-04-15 19:50 ` George Kashperko
2011-04-17 17:38 ` Arnd Bergmann
2011-04-17 17:38 ` Arnd Bergmann
2011-04-18 12:19 ` Rafał Miłecki
2011-04-18 12:19 ` Rafał Miłecki
2011-04-18 12:19 ` Rafał Miłecki
2011-04-18 14:19 ` Arnd Bergmann
2011-04-18 14:19 ` Arnd Bergmann
2011-04-18 14:31 ` Rafał Miłecki
2011-04-18 14:31 ` Rafał Miłecki
2011-04-18 14:31 ` Rafał Miłecki
2011-04-18 15:35 ` George Kashperko
2011-04-18 15:35 ` George Kashperko
2011-04-18 15:53 ` Rafał Miłecki
2011-04-18 15:53 ` Rafał Miłecki
2011-04-18 15:53 ` Rafał Miłecki
2011-04-18 16:48 ` George Kashperko
2011-04-18 16:48 ` George Kashperko
2011-04-19 13:46 ` Arnd Bergmann
2011-04-19 13:46 ` Arnd Bergmann
2011-04-19 13:58 ` Arend van Spriel
2011-04-19 13:58 ` Arend van Spriel
2011-04-19 14:02 ` Greg KH
2011-04-19 14:02 ` Greg KH
2011-04-20 6:39 ` Arend van Spriel
2011-04-20 6:39 ` Arend van Spriel
2011-04-20 6:44 ` Arnd Bergmann [this message]
2011-04-20 6:44 ` Arnd Bergmann
2011-04-19 14:20 ` Rafał Miłecki
2011-04-19 14:20 ` Rafał Miłecki
2011-04-19 14:20 ` Rafał Miłecki
2011-04-19 14:35 ` Arnd Bergmann
2011-04-19 14:35 ` Arnd Bergmann
2011-04-20 7:16 ` Arend van Spriel
2011-04-20 7:16 ` Arend van Spriel
2011-04-20 7:26 ` Arnd Bergmann
2011-04-20 7:26 ` Arnd Bergmann
2011-04-20 7:57 ` Arend van Spriel
2011-04-20 7:57 ` Arend van Spriel
2011-04-20 7:29 ` Rafał Miłecki
2011-04-20 7:29 ` Rafał Miłecki
2011-04-20 7:29 ` Rafał Miłecki
2011-05-05 12:33 ` AXI driver status => previously: " Arend van Spriel
2011-05-05 12:33 ` Arend van Spriel
2011-05-05 12:48 ` Rafał Miłecki
2011-05-05 12:48 ` Rafał Miłecki
2011-05-05 12:48 ` Rafał Miłecki
2011-05-05 12:54 ` Arend van Spriel
2011-05-05 12:54 ` Arend van Spriel
2011-04-14 13:03 ` George Kashperko
2011-04-14 13:03 ` George Kashperko
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=201104200844.10607.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=Larry.Finger@lwfinger.net \
--cc=andy@andybotting.com \
--cc=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=george@znau.edu.ua \
--cc=greg@kroah.com \
--cc=hauke@hauke-m.de \
--cc=jonas.gorski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.