linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH/RFC] powerpc: Create PCI busses from of_platform
Date: Sun, 05 Nov 2006 08:53:56 +1100	[thread overview]
Message-ID: <1162677236.28571.43.camel@localhost.localdomain> (raw)
In-Reply-To: <A9F3AC31-AB61-4E39-86D7-B14B96B50B4D@kernel.crashing.org>

On Sat, 2006-11-04 at 16:40 +0100, Segher Boessenkool wrote:
> > +static struct of_device_id of_pci_phb_ids[] = {
> > +	{ .type = "pci", },
> > +	{ .type = "pcix", },
> > +	{ .type = "pcie", },
> > +	{ .type = "pciex", },
> > +	{ .type = "ht", },
> > +	{}
> > +};
> > +
> > +static struct of_platform_driver of_pci_phb_driver = {
> > +       .name = "of-pci",
> > +       .match_table = of_pci_phb_ids,
> > +       .probe = of_pci_phb_probe,
> > +       .driver = {
> > +	       .multithread_probe = 1,
> > +       },
> > +};
> 
> Shouldn't you also/only check for compatible=pci?  Or maybe
> that would give too much fallout from all the broken device
> trees out there?

We can add things when we need them. This mecanism is to be used by
platforms who register of_device's for the PHBs. Currently, this will
only happen with Cell, so I only need to deal with what's there (I could
even remove 'ht' from the list :-)

As more platforms want to use it, they can fine-tune the list and probe
function.

Ben.

      reply	other threads:[~2006-11-04 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 21:28 [PATCH/RFC] powerpc: Create PCI busses from of_platform Benjamin Herrenschmidt
2006-11-04 15:40 ` Segher Boessenkool
2006-11-04 21:53   ` Benjamin Herrenschmidt [this message]

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=1162677236.28571.43.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).