Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: arend@broadcom.com (Arend van Spriel)
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:39:59 +0200	[thread overview]
Message-ID: <op.vt74sxvp3ri7v4@arend-laptop> (raw)
In-Reply-To: <20110419140257.GA20456@kroah.com>

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.

Gr. AvS
-- 
"The world is indeed comic, but the joke is on mankind." ? H.P. Lovecraft

  reply	other threads:[~2011-04-20  6:39 UTC|newest]

Thread overview: 37+ 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:43 ` George Kashperko
2011-04-14 12:04   ` Rafał Miłecki
2011-04-14 12:34     ` Hauke Mehrtens
2011-04-14 13:07       ` Rafał Miłecki
2011-04-14 13:15         ` George Kashperko
2011-04-14 13:45           ` Rafał Miłecki
2011-04-15 18:36             ` George Kashperko
2011-04-15 19:21               ` Rafał Miłecki
2011-04-15 19:42                 ` George Kashperko
2011-04-15 19:52                   ` Rafał Miłecki
2011-04-15 19:56                     ` Peter Stuge
2011-04-16 14:00                       ` Rafał Miłecki
2011-04-16 14:13                         ` Jonas Gorski
2011-04-15 19:50                 ` George Kashperko
2011-04-17 17:38                 ` Arnd Bergmann
2011-04-18 12:19                   ` Rafał Miłecki
2011-04-18 14:19                     ` Arnd Bergmann
2011-04-18 14:31                       ` Rafał Miłecki
2011-04-18 15:35                         ` George Kashperko
2011-04-18 15:53                           ` Rafał Miłecki
2011-04-18 16:48                             ` George Kashperko
2011-04-19 13:46                         ` Arnd Bergmann
2011-04-19 13:58                   ` Arend van Spriel
2011-04-19 14:02                     ` Greg KH
2011-04-20  6:39                       ` Arend van Spriel [this message]
2011-04-20  6:44                         ` Arnd Bergmann
2011-04-19 14:20                     ` Rafał Miłecki
2011-04-19 14:35                     ` Arnd Bergmann
2011-04-20  7:16                       ` Arend van Spriel
2011-04-20  7:26                         ` Arnd Bergmann
2011-04-20  7:57                           ` Arend van Spriel
2011-04-20  7:29                         ` Rafał Miłecki
2011-05-05 12:33                           ` AXI driver status => previously: " Arend van Spriel
2011-05-05 12:48                             ` Rafał Miłecki
2011-05-05 12:54                               ` Arend van Spriel
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=op.vt74sxvp3ri7v4@arend-laptop \
    --to=arend@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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