From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Connecting to "PCI command write" interrupt on 4xx platforms
Date: Tue, 04 Nov 2008 17:16:43 +1100 [thread overview]
Message-ID: <1225779403.8004.263.camel@pasglop> (raw)
In-Reply-To: <200811040619.13820.sr@denx.de>
On Tue, 2008-11-04 at 06:19 +0100, Stefan Roese wrote:
> On Monday 03 November 2008, Benjamin Herrenschmidt wrote:
> > > I will try to add endpoint support for PCI as well. I would like to have
> > > a single PCI node and let the device_type attribute decide if we are
> > > running in hostbridge or endpoint mode.
> >
> > Don't use device_type. Do the same we do for PCI-E (whatever it is, I
> > don't have the source code at hand right now).
>
> It is device_type for PCIe right now, I'm afraid. This was what we agreed
> upon. Here a code sniplet from the patch:
>
> /* Check if device_type property is set to "pci" or "pci-endpoint".
> * Resulting from this setup this PCIe port will be configured
> * as root-complex or as endpoint.
> */
> val = of_get_property(port->node, "device_type", NULL);
> if (!strcmp(val, "pci-endpoint")) {
> port->endpoint = 1;
> } else if (!strcmp(val, "pci")) {
> port->endpoint = 0;
> } else {
> printk(KERN_ERR "PCIE: missing or incorrect device_type for %s\n",
> np->full_name);
> return;
> }
Allright, that was a bad idea from both of us, David will have my
skin ...
We should try to move toward something like an "endpoint" property and a
"pci-endpoint" name instead.
Ben.
next prev parent reply other threads:[~2008-11-04 6:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 10:58 Connecting to "PCI command write" interrupt on 4xx platforms Matthias Fuchs
2008-10-30 20:15 ` Benjamin Herrenschmidt
2008-11-03 9:10 ` Matthias Fuchs
2008-11-03 10:57 ` Benjamin Herrenschmidt
2008-11-03 11:54 ` Stefan Roese
2008-11-03 13:40 ` Matthias Fuchs
2008-11-03 13:45 ` Matthias Fuchs
2008-11-03 20:19 ` Benjamin Herrenschmidt
2008-11-04 5:19 ` Stefan Roese
2008-11-04 6:16 ` Benjamin Herrenschmidt [this message]
2008-11-04 11:17 ` Matthias Fuchs
2008-11-04 21:29 ` Benjamin Herrenschmidt
2008-11-05 20:32 ` Matthias Fuchs
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=1225779403.8004.263.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/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.