All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	"mohit.kumar@st.com" <mohit.kumar@st.com>
Subject: Re: [PATCH 2/3] PCI: ARM: add support for virtual PCI host controller
Date: Wed, 12 Feb 2014 11:19:13 -0700	[thread overview]
Message-ID: <20140212181913.GA16428@obsidianresearch.com> (raw)
In-Reply-To: <20140212181015.GJ29132@mudshark.cambridge.arm.com>

On Wed, Feb 12, 2014 at 06:10:15PM +0000, Will Deacon wrote:

> > AFAIK, the job is fairly simple, when you call pci_add_resource_offset
> > for memory compute the offset from 
> >   of_pci_range.pci_addr - of_pci_range.cpu_addr
> > 
> > (or is it the other way around ?)
> 
> I think it's the other way round: bus = cpu - offset, then Arnd's example of
> PCI bus 0 works out as: 0 = cpu - pci->mem_start.

That looks right to me

> I added that to my driver, but I get some weird looking bus addresses in
> dmesg:
> 
> [    0.307585] pci-arm-generic 40000000.pci: PCI host bridge to bus 0000:00
> [    0.307601] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
> [    0.307615] pci_bus 0000:00: root bus resource [mem 0x00000000-0x3effffff] (bus address [0xffffffffbf000000-0xfffffffffdffffff])
> 
> Looking at drivers/pci/probe.c, it seems to think that res->start - offset
> gives a bus address, which implies that the resources are indeed *CPU*
> addresses.
> 
> Are you sure pci_add_resource_offset wants bus addresses?

Sorry, I wasn't clear: It accepts a cpu address in the struct
resource and an offset to convert back to a bus address.

You should compute 0 as the offset in the normal case, ie
of_pci_range.pci_addr and of_pci_range.cpu_addr should be identical,
which depends on the DT ranges being correct..

Jason

WARNING: multiple messages have this Message-ID (diff)
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] PCI: ARM: add support for virtual PCI host controller
Date: Wed, 12 Feb 2014 11:19:13 -0700	[thread overview]
Message-ID: <20140212181913.GA16428@obsidianresearch.com> (raw)
In-Reply-To: <20140212181015.GJ29132@mudshark.cambridge.arm.com>

On Wed, Feb 12, 2014 at 06:10:15PM +0000, Will Deacon wrote:

> > AFAIK, the job is fairly simple, when you call pci_add_resource_offset
> > for memory compute the offset from 
> >   of_pci_range.pci_addr - of_pci_range.cpu_addr
> > 
> > (or is it the other way around ?)
> 
> I think it's the other way round: bus = cpu - offset, then Arnd's example of
> PCI bus 0 works out as: 0 = cpu - pci->mem_start.

That looks right to me

> I added that to my driver, but I get some weird looking bus addresses in
> dmesg:
> 
> [    0.307585] pci-arm-generic 40000000.pci: PCI host bridge to bus 0000:00
> [    0.307601] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
> [    0.307615] pci_bus 0000:00: root bus resource [mem 0x00000000-0x3effffff] (bus address [0xffffffffbf000000-0xfffffffffdffffff])
> 
> Looking at drivers/pci/probe.c, it seems to think that res->start - offset
> gives a bus address, which implies that the resources are indeed *CPU*
> addresses.
> 
> Are you sure pci_add_resource_offset wants bus addresses?

Sorry, I wasn't clear: It accepts a cpu address in the struct
resource and an offset to convert back to a bus address.

You should compute 0 as the offset in the normal case, ie
of_pci_range.pci_addr and of_pci_range.cpu_addr should be identical,
which depends on the DT ranges being correct..

Jason

  reply	other threads:[~2014-02-12 18:19 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 16:53 [PATCH 0/3] ARM: PCI: implement virtual PCI host controller Will Deacon
2014-02-04 16:53 ` Will Deacon
2014-02-04 16:53 ` [PATCH 1/3] ARM: bios32: use pci_enable_resource to enable PCI resources Will Deacon
2014-02-04 16:53   ` Will Deacon
2014-02-12  1:06   ` Bjorn Helgaas
2014-02-12  1:06     ` Bjorn Helgaas
2014-02-12 16:18     ` Will Deacon
2014-02-12 16:18       ` Will Deacon
2014-02-04 16:53 ` [PATCH 2/3] PCI: ARM: add support for virtual PCI host controller Will Deacon
2014-02-04 16:53   ` Will Deacon
2014-02-04 19:13   ` Arnd Bergmann
2014-02-04 19:13     ` Arnd Bergmann
2014-02-05 19:09     ` Will Deacon
2014-02-05 19:09       ` Will Deacon
2014-02-05 19:27       ` Jason Gunthorpe
2014-02-05 19:27         ` Jason Gunthorpe
2014-02-05 19:41         ` Peter Maydell
2014-02-05 19:41           ` Peter Maydell
2014-02-05 20:26       ` Arnd Bergmann
2014-02-05 20:26         ` Arnd Bergmann
2014-02-05 20:53         ` Jason Gunthorpe
2014-02-05 20:53           ` Jason Gunthorpe
2014-02-06  8:28           ` Arnd Bergmann
2014-02-06  8:28             ` Arnd Bergmann
2014-02-06 20:31             ` Russell King - ARM Linux
2014-02-06 20:31               ` Russell King - ARM Linux
2014-02-09 20:18               ` Arnd Bergmann
2014-02-09 20:18                 ` Arnd Bergmann
2014-02-09 20:34                 ` Russell King - ARM Linux
2014-02-09 20:34                   ` Russell King - ARM Linux
2014-02-11 19:15                   ` Arnd Bergmann
2014-02-11 19:15                     ` Arnd Bergmann
2014-02-07 11:46         ` Will Deacon
2014-02-07 11:46           ` Will Deacon
2014-02-07 17:54           ` Jason Gunthorpe
2014-02-07 17:54             ` Jason Gunthorpe
2014-02-12 18:10             ` Will Deacon
2014-02-12 18:10               ` Will Deacon
2014-02-12 18:19               ` Jason Gunthorpe [this message]
2014-02-12 18:19                 ` Jason Gunthorpe
2014-02-12 18:21                 ` Will Deacon
2014-02-12 18:21                   ` Will Deacon
2014-02-09 20:30           ` Arnd Bergmann
2014-02-09 20:30             ` Arnd Bergmann
2014-02-10 17:34             ` Jason Gunthorpe
2014-02-10 17:34               ` Jason Gunthorpe
2014-02-11 10:42               ` Arnd Bergmann
2014-02-11 10:42                 ` Arnd Bergmann
2014-02-12 19:43                 ` Jason Gunthorpe
2014-02-12 19:43                   ` Jason Gunthorpe
2014-02-12 20:07                   ` Arnd Bergmann
2014-02-12 20:07                     ` Arnd Bergmann
2014-02-12 20:33                     ` Bjorn Helgaas
2014-02-12 20:33                       ` Bjorn Helgaas
2014-02-12 21:15                   ` Thomas Petazzoni
2014-02-12 21:15                     ` Thomas Petazzoni
2014-02-12 22:24                     ` Jason Gunthorpe
2014-02-12 22:24                       ` Jason Gunthorpe
2014-02-12 19:49                 ` Will Deacon
2014-02-12 19:49                   ` Will Deacon
2014-02-06  8:54   ` Anup Patel
2014-02-06  8:54     ` Anup Patel
2014-02-06 10:26     ` Arnd Bergmann
2014-02-06 10:26       ` Arnd Bergmann
2014-02-06 10:52       ` Anup Patel
2014-02-06 10:52         ` Anup Patel
2014-02-06 10:54     ` Liviu Dudau
2014-02-06 10:54       ` Liviu Dudau
2014-02-06 11:00       ` Will Deacon
2014-02-06 11:00         ` Will Deacon
2014-02-06 11:28         ` Arnd Bergmann
2014-02-06 11:28           ` Arnd Bergmann
2014-02-04 16:53 ` [PATCH 3/3] ARM: mach-virt: allow PCI support to be selected Will Deacon
2014-02-04 16:53   ` Will Deacon
2014-04-03 22:07 ` [PATCH 0/3] ARM: PCI: implement virtual PCI host controller Bjorn Helgaas
2014-04-03 22:07   ` Bjorn Helgaas
2014-04-14 17:13   ` Will Deacon
2014-04-14 17:13     ` Will Deacon
2014-04-14 18:48     ` Arnd Bergmann
2014-04-14 18:48       ` Arnd Bergmann
2014-04-15 14:47       ` Will Deacon
2014-04-15 14:47         ` Will Deacon
2014-04-15 15:26         ` Arnd Bergmann
2014-04-15 15:26           ` Arnd Bergmann
2014-04-16 13:58           ` Will Deacon
2014-04-16 13:58             ` Will Deacon

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=20140212181913.GA16428@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mohit.kumar@st.com \
    --cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.