From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] arm/ls102xa: create TLB to map PCIe region
Date: Wed, 25 Feb 2015 13:33:12 -0800 [thread overview]
Message-ID: <54EE3F98.1030409@freescale.com> (raw)
In-Reply-To: <1421832560-30696-1-git-send-email-Minghuan.Lian@freescale.com>
On 01/21/2015 01:29 AM, Minghuan Lian wrote:
> LS1021A's PCIe1 region begins 0x40_00000000; PCIe2 begins
> 0x48_00000000. In order to access PCIe device, we must create
> TLB to map the 40bit physical address to 32bit virtual address.
> This patch will enable MMU after DDR is available and creates MMU
> table in DRAM to map all 4G space; then, re-use the reserved space
> to map PCIe region. The following the mapping layout.
>
> VA mapping:
> ------- <---- 0GB
> | |
> | |
> |-------| <---- 0x24000000
> |///////| ===> 192MB VA map for PCIe1 with offset 0x40_0000_0000
> |-------| <---- 0x300000000
> | |
> |-------| <---- 0x34000000
> |///////| ===> 192MB VA map for PCIe2 with offset 0x48_0000_0000
> |-------| <---- 0x40000000
> | |
> |-------| <---- 0x80000000 DDR0 space start
> |\\\\\\\|
> |\\\\\\\| ===> 2GB VA map for 2GB DDR0 Memory space
> |\\\\\\\|
> ------- <---- 4GB DDR0 space end
>
> Signed-off-by: Minghuan Lian <Minghuan.Lian@freescale.com>
> ---
Applied to u-boot-fsl-qoriq master branch, awaiting upstream.
York
prev parent reply other threads:[~2015-02-25 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 9:29 [U-Boot] [PATCH 1/4] arm/ls102xa: create TLB to map PCIe region Minghuan Lian
2015-01-21 9:29 ` [U-Boot] [PATCH 2/4] arm/ls102xa: use a array to define pexmscportsr Minghuan Lian
2015-02-25 21:34 ` York Sun
2015-01-21 9:29 ` [U-Boot] [PATCH 3/4] arm/ls1021a: add PCIe settings Minghuan Lian
2015-01-21 9:29 ` [U-Boot] [PATCH 4/4] driver/pci: add Layerscape PCIe driver Minghuan Lian
2015-02-25 21:33 ` York Sun [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=54EE3F98.1030409@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.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