linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Jui <ray.jui@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, Hari Vyas <hari.vyas@broadcom.com>,
	Abhishek Shah <abhishek.shah@broadcom.com>,
	Srinath Mannam <srinath.mannam@broadcom.com>,
	Vikram Prakash <vikram.prakash@broadcom.com>
Subject: [RFC] PCIe bus address at 0x00000000
Date: Fri, 29 Sep 2017 17:47:23 -0700	[thread overview]
Message-ID: <a9aba0db-4865-2a6b-b77c-9cb70a4eeab0@broadcom.com> (raw)

Hi Bjorn and all,

One of our ARM64 based processor (NS2) has our system address reversed 
for PCIe outbound transaction in the range of 0x0000_0000 and 
0x1fff_ffff. If we use 1:1 mapping between the system address and PCIe 
address, we end up having the PCIe address in the same range.

In this case, we noticed that certain USB-PCI adapters will decline 
access to BARs mapped in this address range with "Unsupported Request". 
In this case, if we change the PCIe address range to something else like 
0x8000_0000, it would work without an issue.

This sounds like an issue with the USB PCI adapter that cannot allow 
BARs to be used with specific PCIe address range. Is my understanding 
correct?

Thanks,

Ray

             reply	other threads:[~2017-09-30  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-30  0:47 Ray Jui [this message]
2017-10-02 19:35 ` [RFC] PCIe bus address at 0x00000000 Bjorn Helgaas
2017-10-02 19:47   ` Ray Jui
2017-10-02 20:08     ` Bjorn Helgaas
2017-10-03 22:50       ` Ray Jui
2017-10-04  6:17         ` Hari Vyas

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=a9aba0db-4865-2a6b-b77c-9cb70a4eeab0@broadcom.com \
    --to=ray.jui@broadcom.com \
    --cc=abhishek.shah@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=hari.vyas@broadcom.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=srinath.mannam@broadcom.com \
    --cc=vikram.prakash@broadcom.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).