linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Cano" <ccano@interfaceconcept.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: Question: how can I get the real PCI address of a BAR?
Date: Thu, 03 Jan 2013 09:58:00 +0100	[thread overview]
Message-ID: <50E54818.9030401@interfaceconcept.com> (raw)
In-Reply-To: <CAErSpo4nkWwwY5qtsAzgsPYAvUWAKPkML99u+2oiuuzdq4VPKw@mail.gmail.com>

Hi,

pcibios_resource_to_bus() does  what I need.

Thanks.

Le 30/12/2012 20:46, Bjorn Helgaas a écrit :
> On Fri, Dec 28, 2012 at 2:36 AM, Cédric Cano <ccano@interfaceconcept.com> wrote:
>> Hi,
>>
>> I'm writing a driver for a DMA engine on the PCI bus. My architecture is a
>> 36-bit PowerPC (MPC85xx).
>>
>> In my DMA driver, I want to configure the DMA to transfer data to/from a PCI
>> device.
>> I get the PCI address of the device BAR with the command pci_resource_start.
> pci_resource_start() doesn't give you a PCI bus address; it gives you
> a CPU physical address.  You ioremap() that address if you want a CPU
> to access the BAR MMIO space.
>
>> This address is 36-bit but the PCI BAR of the device is 32-bit: I can't use
>> the 36-bit address to run the DMA.
>>
>> In kernel documentations, it's advised not to directly read the BAR.
>>
>> Is there a function which provides the real PCI address i.e. the one stored
>> in the BAR?
> You can use pcibios_resource_to_bus() to convert the CPU physical
> address from the pci_dev.resource[] back to a PCI bus address.
> sym_iomap_device() does something similar to what you're asking about.
>
> Bjorn
>


      reply	other threads:[~2013-01-03  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28  9:36 Question: how can I get the real PCI address of a BAR? Cédric Cano
2012-12-30 19:46 ` Bjorn Helgaas
2013-01-03  8:58   ` Cédric Cano [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=50E54818.9030401@interfaceconcept.com \
    --to=ccano@interfaceconcept.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.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).