From: Stefan Roese <sr@denx.de>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] 4xx: Add endpoint support to 4xx PCIe driver
Date: Thu, 10 Apr 2008 13:59:31 +0200 [thread overview]
Message-ID: <200804101359.32095.sr@denx.de> (raw)
In-Reply-To: <1207823735.6958.7.camel@pasglop>
On Thursday 10 April 2008, Benjamin Herrenschmidt wrote:
> On Thu, 2008-04-10 at 12:21 +0200, Stefan Roese wrote:
> > Sure, this would be optimal. But frankly, I currently have no need for
> > this
> > non U-Boot mode, and therefore I didn't implement it. This can be
> > added later
> > when really needed don't you think?
>
> It can... but on the other hand, it's not hard :-)
But it takes time. And time is as always short. :)
> > Good. But again, I would really prefer to first include this U-Boot
> > style
> > endpoint support and later add this independent device tree endpoint
> > configuration when really needed.
>
> Well, you are the one with a use case... but I do think we should
> differenciate a PCI in host mode vs. endpoint mode right away. We don't
> want the PCI stack from kicking in at all in endpoint mode, we don't
> want to bother with creating the PCI infrastructure and config space
> accessors etc...
Understood. But for this "dynamic" root-complex/endpoint configuration as
implemented with the current version of the patch, I can't change the PCIe
node in the dts from root-complex mode to endpoint mode, since I would loose
root-complex functionality. Perhaps I'm missing something here.
Best regards,
Stefan
next prev parent reply other threads:[~2008-04-10 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 15:12 [PATCH] [POWERPC] 4xx: Add endpoint support to 4xx PCIe driver Stefan Roese
2008-04-02 15:16 ` Stefan Roese
2008-04-10 9:27 ` Benjamin Herrenschmidt
2008-04-10 10:21 ` Stefan Roese
2008-04-10 10:35 ` Benjamin Herrenschmidt
2008-04-10 11:59 ` Stefan Roese [this message]
2008-04-10 12:23 ` Benjamin Herrenschmidt
2008-04-10 13:37 ` Stefan Roese
2008-04-10 21:58 ` 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=200804101359.32095.sr@denx.de \
--to=sr@denx.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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 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.