linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pratyush Anand <pratyush.anand@st.com>
To: Arnd Bergmann <arnd@arndb.de>, Jingoo Han <jg1.han@samsung.com>
Cc: Mohit Kumar <mohit.kumar@st.com>, Marek Vasut <marex@denx.de>,
	Richard Zhu <Hong-Xing.Zhu@freescale.com>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	<linux-pci@vger.kernel.org>, Tim Harvey <tharvey@gateworks.com>
Subject: [Query/Discussion]: IO translation with designware PCIe controller
Date: Thu, 5 Dec 2013 10:34:24 +0530	[thread overview]
Message-ID: <20131205050424.GA2298@pratyush-vbox> (raw)

Hi Arnd / Jingoo,

Sorry for not able to follow earlier discussion you had on this
topic while initial reviews of patches from Jingoo.

I have few doubts that how will it actually work.

As per my understanding under current implementation:

1. Physical IO addresses are in the range of 0x1000 to 0xfffff.
2. They are mapped to fixed virtual address 0xFEE00000 using
pci_ioremap_io.
3. IO resource addresses to any PCIe device will be allocated in above
range.
4. Driver for that PCIe device will write in the above range only for
IO transaction to the device.
5. As per current IO translation programming, its one to one
translation. It means PCIe translation unit will have both input and
output address in the range of 0x1000 to 0xfffff.

Did I miss something, or if above statements are correct, then what I
do not understand is how can designware PCIe translation unit accept
input address in the range of 0x1000 to 0xfffff?

For example in SPEAr1340, physically RAM is mapped on above addresses.
PCIe address translation unit can accept address only in the range of
core addresses which are assigned to PCIe RC ie 0x80000000-0x8FFFFFFF.

Regards
Pratyush


             reply	other threads:[~2013-12-05  5:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  5:04 Pratyush Anand [this message]
2013-12-05 21:33 ` [Query/Discussion]: IO translation with designware PCIe controller Arnd Bergmann
2013-12-06  9:12   ` Pratyush Anand
2013-12-06 14:46     ` Arnd Bergmann
2013-12-09  7:12       ` Pratyush Anand
2013-12-09 16:09         ` Arnd Bergmann
2013-12-10  4:34           ` Pratyush Anand
2013-12-10  5:25             ` Jingoo Han
2013-12-10  6:31               ` Mohit KUMAR DCG
2013-12-10  6:57                 ` Pratyush Anand
2013-12-10  7:02                 ` Jingoo Han
2013-12-13  7:36                   ` Hong-Xing.Zhu
2013-12-10 13:26         ` Marek Vasut
2013-12-10 22:22           ` Jingoo Han
2013-12-10 23:23             ` Tim Harvey
2013-12-10 23:25               ` Marek Vasut
2013-12-10 23:58               ` Jingoo Han

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=20131205050424.GA2298@pratyush-vbox \
    --to=pratyush.anand@st.com \
    --cc=Hong-Xing.Zhu@freescale.com \
    --cc=arnd@arndb.de \
    --cc=jg1.han@samsung.com \
    --cc=kishon@ti.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=mohit.kumar@st.com \
    --cc=tharvey@gateworks.com \
    /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).