From: Andrew Murray <andrew.murray@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Toan Le <toan@os.amperecomputing.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 09/11] PCI: xgene: Use inbound resources for setup
Date: Thu, 26 Sep 2019 09:39:36 +0100 [thread overview]
Message-ID: <20190926083935.GY9720@e119886-lin.cambridge.arm.com> (raw)
In-Reply-To: <20190924214630.12817-10-robh@kernel.org>
On Tue, Sep 24, 2019 at 04:46:28PM -0500, Rob Herring wrote:
> Now that the helpers provide the inbound resources in the host bridge
> 'dma_ranges' resource list, convert the Xgene host bridge to use the
> resource list to setup the inbound addresses.
>
> Cc: Toan Le <toan@os.amperecomputing.com>
> Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Signed-off-by: Rob Herring <robh@kernel.org>
Reviewed-by: Andrew Murray <andrew.murray@arm.com>
> ---
> drivers/pci/controller/pci-xgene.c | 32 ++++++++++--------------------
> 1 file changed, 10 insertions(+), 22 deletions(-)
>
> diff --git a/drivers/pci/controller/pci-xgene.c b/drivers/pci/controller/pci-xgene.c
> index 11f27c42c06a..09c913b12ebc 100644
> --- a/drivers/pci/controller/pci-xgene.c
> +++ b/drivers/pci/controller/pci-xgene.c
> @@ -485,27 +485,27 @@ static int xgene_pcie_select_ib_reg(u8 *ib_reg_mask, u64 size)
> }
>
> static void xgene_pcie_setup_ib_reg(struct xgene_pcie_port *port,
> - struct of_pci_range *range, u8 *ib_reg_mask)
> + struct resource_entry *entry, u8 *ib_reg_mask)
> {
> void __iomem *cfg_base = port->cfg_base;
> struct device *dev = port->dev;
> void *bar_addr;
> u32 pim_reg;
> - u64 cpu_addr = range->cpu_addr;
> - u64 pci_addr = range->pci_addr;
> - u64 size = range->size;
> + u64 cpu_addr = entry->res->start;
> + u64 pci_addr = cpu_addr - entry->offset;
> + u64 size = resource_size(entry->res);
> u64 mask = ~(size - 1) | EN_REG;
> u32 flags = PCI_BASE_ADDRESS_MEM_TYPE_64;
> u32 bar_low;
> int region;
>
> - region = xgene_pcie_select_ib_reg(ib_reg_mask, range->size);
> + region = xgene_pcie_select_ib_reg(ib_reg_mask, size);
> if (region < 0) {
> dev_warn(dev, "invalid pcie dma-range config\n");
> return;
> }
>
> - if (range->flags & IORESOURCE_PREFETCH)
> + if (entry->res->flags & IORESOURCE_PREFETCH)
> flags |= PCI_BASE_ADDRESS_MEM_PREFETCH;
>
> bar_low = pcie_bar_low_val((u32)cpu_addr, flags);
> @@ -536,25 +536,13 @@ static void xgene_pcie_setup_ib_reg(struct xgene_pcie_port *port,
>
> static int xgene_pcie_parse_map_dma_ranges(struct xgene_pcie_port *port)
> {
> - struct device_node *np = port->node;
> - struct of_pci_range range;
> - struct of_pci_range_parser parser;
> - struct device *dev = port->dev;
> + struct pci_host_bridge *bridge = pci_host_bridge_from_priv(port);
> + struct resource_entry *entry;
> u8 ib_reg_mask = 0;
>
> - if (of_pci_dma_range_parser_init(&parser, np)) {
> - dev_err(dev, "missing dma-ranges property\n");
> - return -EINVAL;
> - }
> -
> - /* Get the dma-ranges from DT */
> - for_each_of_pci_range(&parser, &range) {
> - u64 end = range.cpu_addr + range.size - 1;
> + resource_list_for_each_entry(entry, &bridge->dma_ranges)
> + xgene_pcie_setup_ib_reg(port, entry, &ib_reg_mask);
>
> - dev_dbg(dev, "0x%08x 0x%016llx..0x%016llx -> 0x%016llx\n",
> - range.flags, range.cpu_addr, end, range.pci_addr);
> - xgene_pcie_setup_ib_reg(port, &range, &ib_reg_mask);
> - }
> return 0;
> }
>
> --
> 2.20.1
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-26 8:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 21:46 [PATCH 00/11] PCI dma-ranges parsing consolidation Rob Herring
2019-09-24 21:46 ` [PATCH 01/11] PCI: aardvark: Use pci_parse_request_of_pci_ranges() Rob Herring
2019-09-25 8:59 ` Thomas Petazzoni
2019-09-25 9:04 ` Andrew Murray
2019-09-24 21:46 ` [PATCH 02/11] PCI: altera: " Rob Herring
2019-09-25 10:24 ` Andrew Murray
2019-09-25 12:33 ` Rob Herring
2019-09-30 15:13 ` Andrew Murray
2019-09-30 17:36 ` Rob Herring
2019-10-15 11:02 ` Lorenzo Pieralisi
2019-10-15 11:17 ` Rob Herring
2019-09-24 21:46 ` [PATCH 03/11] PCI: mediatek: " Rob Herring
2019-09-25 11:34 ` Andrew Murray
2019-09-24 21:46 ` [PATCH 04/11] PCI: versatile: Enable COMPILE_TEST Rob Herring
2019-09-26 8:12 ` Andrew Murray
2019-09-24 21:46 ` [PATCH 05/11] PCI: versatile: Use pci_parse_request_of_pci_ranges() Rob Herring
2019-09-25 10:37 ` Andrew Murray
2019-09-26 21:44 ` Rob Herring
2019-09-30 15:16 ` Andrew Murray
2019-09-30 16:56 ` Peter Maydell
2019-09-30 19:36 ` Andrew Murray
2019-09-24 21:46 ` [PATCH 06/11] PCI: of: Add inbound resource parsing to helpers Rob Herring
2019-09-25 9:00 ` Thomas Petazzoni
2019-09-26 8:29 ` Andrew Murray
2019-09-26 10:43 ` Gustavo Pimentel
2019-09-27 16:12 ` Jingoo Han
2019-09-27 16:12 ` Jingoo Han
2019-09-24 21:46 ` [PATCH 07/11] PCI: ftpci100: Use inbound resources for setup Rob Herring
2019-09-26 8:39 ` Andrew Murray
2019-09-24 21:46 ` [PATCH 08/11] PCI: v3-semi: " Rob Herring
2019-09-26 8:39 ` Andrew Murray
2019-09-30 22:00 ` Linus Walleij
2019-09-24 21:46 ` [PATCH 09/11] PCI: xgene: " Rob Herring
2019-09-26 8:39 ` Andrew Murray [this message]
2019-09-24 21:46 ` [PATCH 10/11] PCI: iproc: " Rob Herring
2019-09-26 8:39 ` Andrew Murray
2019-09-24 21:46 ` [PATCH 11/11] PCI: rcar: " Rob Herring
2019-09-26 8:47 ` Andrew Murray
2019-09-26 12:53 ` Rob Herring
2019-09-26 13:32 ` Andrew Murray
2019-09-26 8:49 ` [PATCH 00/11] PCI dma-ranges parsing consolidation Andrew Murray
2019-09-26 11:20 ` Marc Gonzalez
2019-09-26 13:11 ` Rob Herring
2019-09-26 13:38 ` Andrew Murray
2019-09-26 14:09 ` Marc Gonzalez
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=20190926083935.GY9720@e119886-lin.cambridge.arm.com \
--to=andrew.murray@arm.com \
--cc=bhelgaas@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=toan@os.amperecomputing.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).