From: Kumar Gala <galak@kernel.crashing.org>
To: Trent Piepho <tpiepho@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Trent Piepho <xyzzy@speakeasy.org>
Subject: Re: [PATCH 2/2] POWERPC/fsl-pci: Set relaxed ordering on prefetchable ranges
Date: Tue, 6 Jan 2009 22:38:47 -0600 [thread overview]
Message-ID: <0DE1536E-02B5-4D1C-9753-295EDF0D6721@kernel.crashing.org> (raw)
In-Reply-To: <1229543006-8950-2-git-send-email-tpiepho@freescale.com>
On Dec 17, 2008, at 1:43 PM, Trent Piepho wrote:
> Provides a small speedup when accessing pefetchable ranges. To
> indicate
> that a memory range is prefetchable, mark it in the dts file with
> 42000000
> instead of 02000000.
>
> A powepc pci_controller is allowed three memory ranges, any of which
> may be
> prefetchable. However, the PCI-PCI bridge configuration space only
> has one
> field for "non-prefetchable memory behind bridge", which has a 32 bit
> address, and one field for "prefetchable memory behind bridge",
> which may
> have a 64 bit address. These are PCI bus addresses, not CPU physical
> addresses.
>
> So really you're only allowed one memory range of each type. And if
> you
> want the range at a PCI address above 32 bits you must make it
> prefetchable.
>
> Signed-off-by: Trent Piepho <tpiepho@freescale.com>
> ---
> arch/powerpc/sysdev/fsl_pci.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
applied
- k
next prev parent reply other threads:[~2009-01-07 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 19:43 [PATCH 1/2] POWERPC/fsl-pci: Better ATMU setup Trent Piepho
2008-12-17 19:43 ` [PATCH 2/2] POWERPC/fsl-pci: Set relaxed ordering on prefetchable ranges Trent Piepho
2009-01-07 4:38 ` Kumar Gala [this message]
2008-12-17 20:59 ` [PATCH 1/2] POWERPC/fsl-pci: Better ATMU setup Benjamin Herrenschmidt
2009-01-07 4:38 ` Kumar Gala
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=0DE1536E-02B5-4D1C-9753-295EDF0D6721@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tpiepho@freescale.com \
--cc=xyzzy@speakeasy.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).