linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: David Miller <davem@davemloft.net>
Cc: linuxppc-dev@ozlabs.org, thunderbird2k@gmail.com,
	John.Linn@xilinx.com, arnd@arndb.de
Subject: Re: Musings on PCI busses
Date: Tue, 19 May 2009 14:02:55 -0600	[thread overview]
Message-ID: <fa686aa40905191302g6c7c3b9dmedacfcd96462a23f@mail.gmail.com> (raw)
In-Reply-To: <20090519.120514.26253637.davem@davemloft.net>

On Tue, May 19, 2009 at 1:05 PM, David Miller <davem@davemloft.net> wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Tue, 19 May 2009 18:12:02 +0200
>
>> On Tuesday 19 May 2009, Grant Likely wrote:
>>> 1) Probe the host controller in an of_platform driver. =A0This has the
>>> advantage of simplicity. =A0The probe routine will get automatically
>>> called when the PCI host controller device tree node is registered
>>> with the of_platform bus. =A0The bus parenthood also gets reflected in
>>> the device model and sysfs. =A0The disadvantage is that it defers PCI
>>> bus probing until after the of_platform bus is probed (maybe this is
>>> okay; maybe this already happens anyway).
>>
>> This is also what we do on 64-bit systems (well, Cell at this time).
>> There are no fundamental problems with this, just some slightly
>> unexpected interactions e.g. when you have use a PCI serial port
>> as your console before probing PCI.
>
> This is also what sparc64 does :-)
>
> All of the individual sparc64 PCI controller types have a OF driver
> and then there is a common layer of OF PCI helper code to do most
> of the work.

Cool, well I have my solution then.  :-)

g.


--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2009-05-19 20:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 15:28 Musings on PCI busses Grant Likely
2009-05-19 16:12 ` Arnd Bergmann
2009-05-19 19:05   ` David Miller
2009-05-19 20:02     ` Grant Likely [this message]
2009-05-20  5:33     ` Benjamin Herrenschmidt
2009-05-19 16:25 ` Stephen Neuendorffer
2009-05-19 16:30   ` Grant Likely
2009-05-20  3:02   ` Benjamin Herrenschmidt
2009-05-20  3:17     ` Grant Likely
2009-05-20  5:31       ` Benjamin Herrenschmidt
2009-05-20  3:01 ` Benjamin Herrenschmidt
2009-05-20  5:51   ` David Miller
2009-05-20  6:51     ` Benjamin Herrenschmidt
2009-05-20 19:24       ` David Miller
2009-05-20 20:06         ` Grant Likely
2009-05-20 21:59           ` Benjamin Herrenschmidt
2009-05-20 22:28             ` Grant Likely
2009-05-20 22:41             ` David Miller
2009-05-20 22:49               ` Benjamin Herrenschmidt
2009-05-20 21:56         ` Benjamin Herrenschmidt

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=fa686aa40905191302g6c7c3b9dmedacfcd96462a23f@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=John.Linn@xilinx.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=thunderbird2k@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).