mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: "'Jim Quinlan'" <jim2101024@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	"Brian Norris" <computersforpeace@gmail.com>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Robin Murphy <robin.murphy@arm.com>,
	"Christoph Hellwig" <hch@lst.de>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"bcm-kernel-feedback-list@broadcom.com" 
	<bcm-kernel-feedback-list@broadcom.com>,
	Gregory Fong <gregory.0xf0@gmail.com>,
	Kevin Cernekee <cernekee@gmail.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
	Ralf Baechle <ralf@linux-mips.org>
Subject: RE: [PATCH 4/8] PCI: host: brcmstb: add dma-ranges for inbound traffic
Date: Wed, 25 Oct 2017 09:46:45 +0000	[thread overview]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DD00A252D@AcuExch.aculab.com> (raw)
In-Reply-To: <1508868949-16652-5-git-send-email-jim2101024@gmail.com>

From: Jim Quinlan
> Sent: 24 October 2017 19:16
> The Broadcom STB PCIe host controller is intimately related to the
> memory subsystem.  This close relationship adds complexity to how cpu
> system memory is mapped to PCIe memory.  Ideally, this mapping is an
> identity mapping, or an identity mapping off by a constant.  Not so in
> this case.
> 
> Consider the Broadcom reference board BCM97445LCC_4X8 which has 6 GB
> of system memory.  Here is how the PCIe controller maps the
> system memory to PCIe memory:
> 
>   memc0-a@[        0....3fffffff] <=> pci@[        0....3fffffff]
>   memc0-b@[100000000...13fffffff] <=> pci@[ 40000000....7fffffff]
>   memc1-a@[ 40000000....7fffffff] <=> pci@[ 80000000....bfffffff]
>   memc1-b@[300000000...33fffffff] <=> pci@[ c0000000....ffffffff]
>   memc2-a@[ 80000000....bfffffff] <=> pci@[100000000...13fffffff]
>   memc2-b@[c00000000...c3fffffff] <=> pci@[140000000...17fffffff]

I presume the first column is the 'cpu physical address'
and the second the 'pci' address?

...

Isn't this just the same as having an iommu that converts 'bus'
addresses into 'physical' ones?

A simple table lookup of the high address bits will do the
conversion.

	David

  reply	other threads:[~2017-10-25  9:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 18:15 Subject: PCI: brcmstb: Add Broadcom Settopbox PCIe support (V2) Jim Quinlan
2017-10-24 18:15 ` [PATCH 1/8] SOC: brcmstb: add memory API Jim Quinlan
2017-10-25  0:23   ` Florian Fainelli
2017-10-25 15:00     ` Jim Quinlan
2017-10-24 18:15 ` [PATCH 2/8] PCI: host: brcmstb: add DT docs for Brcmstb PCIe device Jim Quinlan
2017-10-27 14:37   ` Rob Herring
2017-10-30 14:07   ` Jonas Gorski
2017-10-24 18:15 ` [PATCH 3/8] PCI: host: brcmstb: Broadcom PCIe Host Controller Jim Quinlan
2017-10-24 21:15   ` Bjorn Helgaas
2017-10-25 17:42     ` Jim Quinlan
2017-10-24 18:15 ` [PATCH 4/8] PCI: host: brcmstb: add dma-ranges for inbound traffic Jim Quinlan
2017-10-25  9:46   ` David Laight [this message]
2017-10-25 16:00     ` Jim Quinlan
2017-10-24 18:15 ` [PATCH 5/8] PCI/MSI: Enable PCI_MSI_IRQ_DOMAIN support for MIPS Jim Quinlan
2017-10-24 18:15 ` [PATCH 6/8] PCI: host: brcmstb: add MSI capability Jim Quinlan
2017-10-24 18:57   ` Florian Fainelli
2017-10-25 15:28     ` Jim Quinlan
2017-10-25 17:23       ` Bjorn Helgaas
2017-10-25 18:40         ` Scott Branden
2017-10-25 20:16           ` Bjorn Helgaas
2017-10-25 21:11             ` Jim Quinlan
2017-10-25 13:22   ` Bjorn Helgaas
2017-10-25 15:50     ` Jim Quinlan
2017-10-24 18:15 ` [PATCH 7/8] MIPS: BMIPS: add PCI bindings for 7425, 7435 Jim Quinlan
2017-10-24 18:15 ` [PATCH 8/8] MIPS: BMIPS: enable PCI Jim Quinlan

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=063D6719AE5E284EB5DD2968C1650D6DD00A252D@AcuExch.aculab.com \
    --to=david.laight@aculab.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=cernekee@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregory.0xf0@gmail.com \
    --cc=hch@lst.de \
    --cc=jim2101024@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ralf@linux-mips.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®