From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v11 08/10] OF: PCI: Add support for parsing PCI host bridge resources from DT
Date: Tue, 23 Sep 2014 09:56:37 +0200 [thread overview]
Message-ID: <8687285.EH4RPBeOB5@wuerfel> (raw)
In-Reply-To: <20140922114317.GN1994@e106497-lin.cambridge.arm.com>
On Monday 22 September 2014 12:43:17 Liviu Dudau wrote:
> >
> > From e798af4fc2f664d1aff7e863489b8298f90e716e Mon Sep 17 00:00:00 2001
> > From: Robert Richter <rrichter@cavium.com>
> > Date: Mon, 22 Sep 2014 10:46:01 +0200
> > Subject: [PATCH] OF: PCI: Fix creation of mem-mapped pci host bridges
> >
> > The pci host bridge was not created if io_base was not set when
> > calling of_pci_get_host_bridge_resources(). This is esp. the case for
> > mem-mapped io (IORESOURCE_MEM). This patch fixes this. Function
> > parameter io_base is optional now.
>
> I think the message is misleading. What you want to do is make io_base
> optional for the case where the PCI host bridge only expects to have only
> IORESOURCE_MEM ranges and doesn't care about IORESOURCE_IO ones.
>
> As I'm going to touch this area again to address a comment from Bjorn,
> do you mind if I roll this patch into mine with your Signed-off-by and
> the mention that you have made io_base optional?
I think the best way to deal with this is to move the check for
io_base down into the place where it is used: As long as the DT only
specifies IORESOURCE_MEM windows, we don't need to look at io_base,
but if the host controller driver does not support IORESOURCE_IO
while the DT specifies it, I guess it would be nice to return an
error.
Arnd
next prev parent reply other threads:[~2014-09-23 7:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 1:30 [PATCH v11 00/10] Support for creating generic PCI host bridges from DT Liviu Dudau
2014-09-18 1:30 ` [PATCH v11 01/10] Fix ioport_map() for !CONFIG_GENERIC_IOMAP cases Liviu Dudau
2014-09-18 1:30 ` [PATCH v11 02/10] PCI: Introduce helper functions to deal with PCI I/O ranges Liviu Dudau
2014-09-19 20:48 ` Bjorn Helgaas
2014-09-18 1:30 ` [PATCH v11 03/10] ARM: Define PCI_IOBASE as the base of virtual PCI IO space Liviu Dudau
2014-09-20 2:14 ` Arnd Bergmann
2014-09-18 1:30 ` [PATCH v11 04/10] PCI: OF: Fix the conversion of IO ranges into IO resources Liviu Dudau
2014-09-19 20:56 ` Bjorn Helgaas
2014-09-20 17:33 ` Rob Herring
2014-09-22 15:32 ` Liviu Dudau
2014-09-22 17:18 ` Rob Herring
2014-09-18 1:30 ` [PATCH v11 05/10] PCI: Create pci_host_bridge before its associated bus in pci_create_root_bus Liviu Dudau
2014-09-18 1:30 ` [PATCH v11 06/10] PCI: Introduce generic domain handling for PCI busses Liviu Dudau
2014-09-18 1:30 ` [PATCH v11 07/10] OF: Introduce helper function for getting PCI domain_nr Liviu Dudau
2014-09-19 21:03 ` Bjorn Helgaas
2014-09-22 11:05 ` Liviu Dudau
2014-09-22 15:25 ` Bjorn Helgaas
2014-09-22 15:33 ` Liviu Dudau
2014-09-20 2:24 ` Arnd Bergmann
2014-09-22 15:20 ` Liviu Dudau
2014-09-20 17:52 ` Rob Herring
2014-09-18 1:30 ` [PATCH v11 08/10] OF: PCI: Add support for parsing PCI host bridge resources from DT Liviu Dudau
2014-09-19 21:06 ` Bjorn Helgaas
2014-09-20 0:28 ` Rob Herring
2014-09-22 17:55 ` Liviu Dudau
2014-09-22 22:11 ` Rob Herring
2014-09-22 9:32 ` Robert Richter
2014-09-22 11:43 ` Liviu Dudau
2014-09-22 12:15 ` Robert Richter
2014-09-23 7:56 ` Arnd Bergmann [this message]
2014-09-23 10:49 ` Liviu Dudau
2014-09-23 13:30 ` Rob Herring
2014-09-23 13:58 ` Liviu Dudau
2014-09-18 1:30 ` [PATCH v11 09/10] PCI: Assign unassigned bus resources in pci_scan_root_bus() Liviu Dudau
2014-09-18 1:30 ` [PATCH v11 10/10] PCI: Introduce pci_remap_iospace() for remapping PCI I/O bus resources into CPU space Liviu Dudau
2014-09-19 21:54 ` Bjorn Helgaas
2014-09-20 2:20 ` Arnd Bergmann
2014-09-22 15:29 ` Robert Richter
2014-09-20 0:34 ` Rob Herring
2014-09-19 21:59 ` [PATCH v11 00/10] Support for creating generic PCI host bridges from DT Bjorn Helgaas
2014-09-22 11:35 ` Liviu Dudau
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=8687285.EH4RPBeOB5@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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