linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] 4xx: Add endpoint support to 4xx PCIe driver
Date: Thu, 10 Apr 2008 20:35:35 +1000	[thread overview]
Message-ID: <1207823735.6958.7.camel@pasglop> (raw)
In-Reply-To: <200804101221.43154.sr@denx.de>


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 :-)

> 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...

> Good idea. How about "vendor-id" and "device-id"? And we probably need
> some 
> for endpoint mode too now. "vendor-id-endpoint" and
> "device-id-endpoint"?

If the host bridge in EP mode has a different name/type than the host
bridge one, just 'vendor-id' and 'device-id' will do there too.

> And how should we handle the backward compatibility? Should I set the
> old 
> values as default when those properties are not available?

Yup.

Cheers,
Ben.

  reply	other threads:[~2008-04-10 11:37 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 [this message]
2008-04-10 11:59       ` Stefan Roese
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=1207823735.6958.7.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 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).