From: Arnd Bergmann <arnd@arndb.de>
To: Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Liviu.Dudau@arm.com" <Liviu.Dudau@arm.com>,
nofooter <nofooter@xilinx.com>,
"thomas.petazzoni@free-electrons.com"
<thomas.petazzoni@free-electrons.com>
Subject: Re: Purpose of pci_remap_iospace
Date: Tue, 12 Jul 2016 10:31:59 +0200 [thread overview]
Message-ID: <3927657.6zNCtCntSU@wuerfel> (raw)
In-Reply-To: <8520D5D51A55D047800579B094147198258B85DC@XAP-PVEXMBX01.xlnx.xilinx.com>
On Tuesday, July 12, 2016 6:57:10 AM CEST Bharat Kumar Gogada wrote:
> Hi,
>
> I have a query.
>
> Can any once explain the purpose of pci_remap_iospace function in root port driver.
>
> What is its dependency with architecture ?
>
> Here is my understanding, the above API takes PCIe IO resource and its to be mapped CPU address from
> ranges property and remaps into virtual address space.
>
> So my question is who uses this virtual addresses ?
The inb()/outb() functions declared in asm/io.h
> When End Point requests for IO BARs doesn't it get
> from the above resource range (first parameter of API) and
> do ioremap to access this region ?
Device drivers generally do not ioremap() the I/O BARs but they
use inb()/outb() directly. They can also call pci_iomap() and
do ioread8()/iowrite8() on the pointer returned from that function,
but generally the call to pci_iomap() then returns a pointer into
the virtual address that is already mapped.
> But why root complex driver is mapping this address region ?
The PCI core does not know that the I/O space is memory mapped.
On x86 and a few others, I/O space is not memory mapped but requires
the use of special CPU instructions.
Arnd
next prev parent reply other threads:[~2016-07-12 8:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 6:57 Purpose of pci_remap_iospace Bharat Kumar Gogada
2016-07-12 8:31 ` Arnd Bergmann [this message]
2016-07-12 8:40 ` Bharat Kumar Gogada
2016-07-13 8:11 ` Bharat Kumar Gogada
2016-07-13 8:30 ` Arnd Bergmann
2016-07-13 12:30 ` Bharat Kumar Gogada
2016-07-13 13:28 ` Arnd Bergmann
2016-07-13 15:16 ` Bharat Kumar Gogada
2016-07-13 15:28 ` Arnd Bergmann
2016-07-13 15:42 ` Liviu.Dudau
2016-07-13 16:13 ` Lorenzo Pieralisi
2016-07-13 13:46 ` Lorenzo Pieralisi
2016-07-14 6:03 ` Bharat Kumar Gogada
2016-07-14 13:32 ` Bharat Kumar Gogada
2016-07-14 14:56 ` Lorenzo Pieralisi
2016-07-14 15:05 ` Bharat Kumar Gogada
2016-07-14 15:20 ` Lorenzo Pieralisi
2016-07-14 15:12 ` Arnd Bergmann
2016-07-14 15:27 ` Lorenzo Pieralisi
2016-07-15 5:21 ` Bharat Kumar Gogada
2016-07-15 6:55 ` Arnd Bergmann
2016-07-13 13:24 ` Liviu.Dudau
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=3927657.6zNCtCntSU@wuerfel \
--to=arnd@arndb.de \
--cc=Liviu.Dudau@arm.com \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nofooter@xilinx.com \
--cc=thomas.petazzoni@free-electrons.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