linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Al Stone <ahs3@redhat.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh+dt@kernel.org>,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Will Deacon <Will.Deacon@arm.com>,
	Russell King <linux@arm.linux.org.uk>,
	linux-pci <linux-pci@vger.kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	Sinan Kaya <okaya@codeaurora.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Device Tree ML <devicetree@vger.kernel.org>,
	Jingoo Han <jg1.han@samsung.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Tanmay Inamdar <tinamdar@apm.com>,
	Suravee Suthikulanit <suravee.suthikulpanit@amd.com>,
	"grant.likely@linaro.org" <grant.likely@linaro.org>,
	Yinghai Lu <yinghai@kernel.org>,
	Jiang Liu <jiang.liu@linux.intel.com>,
	LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v13 02/12] of/pci: Add pci_register_io_range() and pci_pio_to_address()
Date: Tue, 30 Sep 2014 09:59:33 +0100	[thread overview]
Message-ID: <20140930085933.GM841@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <5429B0FE.4070904@redhat.com>

On Mon, Sep 29, 2014 at 08:20:30PM +0100, Al Stone wrote:
> On 09/29/2014 08:29 AM, Liviu Dudau wrote:
> > Some architectures do not have a simple view of the PCI I/O space and
> > instead use a range of CPU addresses that map to bus addresses.  For some
> > architectures these ranges will be expressed by OF bindings in a device
> > tree file.
> > 
> > This patch introduces a pci_register_io_range() helper function with a
> > generic implementation that can be used by such architectures to keep track
> > of the I/O ranges described by the PCI bindings.  If the PCI_IOBASE macro
> > is not defined, that signals lack of support for PCI and we return an
> > error.
> > 
> > In order to retrieve the CPU address associated with an I/O port, a new
> > helper function pci_pio_to_address() is introduced.  This will search in
> > the list of ranges registered with pci_register_io_range() and return the
> > CPU address that corresponds to the given port.
> > 
> > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> > Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
> > Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
> > Acked-by: Rob Herring <robh@kernel.org>
> > CC: Grant Likely <grant.likely@linaro.org>
> > CC: Arnd Bergmann <arnd@arndb.de>
> > ---
> >  drivers/of/address.c       | 109 +++++++++++++++++++++++++++++++++++++++++++++
> >  include/linux/of_address.h |   2 +
> >  2 files changed, 111 insertions(+)
> > 
> > diff --git a/drivers/of/address.c b/drivers/of/address.c
> > index e371825..758d4f0 100644
> > --- a/drivers/of/address.c
> > +++ b/drivers/of/address.c
> > @@ -5,6 +5,8 @@
> >  #include <linux/module.h>
> >  #include <linux/of_address.h>
> >  #include <linux/pci_regs.h>
> > +#include <linux/sizes.h>
> > +#include <linux/slab.h>
> >  #include <linux/string.h>
> >  
> >  /* Max address size we deal with */
> > @@ -601,12 +603,119 @@ const __be32 *of_get_address(struct device_node *dev, int index, u64 *size,
> >  }
> >  EXPORT_SYMBOL(of_get_address);
> >  
> > +#ifdef PCI_IOBASE
> > +struct io_range {
> > +	struct list_head list;
> > +	phys_addr_t start;
> > +	resource_size_t size;
> > +};
> > +
> > +static LIST_HEAD(io_range_list);
> > +static DEFINE_SPINLOCK(io_range_lock);
> > +#endif
> > +
> > +/*
> > + * Record the PCI IO range (expressed as CPU physical address + size).
> > + * Return a negative value if an error has occured, zero otherwise
> > + */
> > +int __weak pci_register_io_range(phys_addr_t addr, resource_size_t size)
> > +{
> > +	int err = 0;
> > +
> > +#ifdef PCI_IOBASE
> > +	struct io_range *range;
> > +	resource_size_t allocated_size = 0;
> > +
> > +	/* check if the range hasn't been previously recorded */
> > +	spin_lock(&io_range_lock);
> > +	list_for_each_entry(range, &io_range_list, list) {
> > +		if (addr >= range->start && addr + size <= range->start + size) {
> > +			/* range already registered, bail out */
> > +			goto end_register;
> > +		}
> > +		allocated_size += range->size;
> > +	}
> > +
> > +	/* range not registed yet, check for available space */
> > +	if (allocated_size + size - 1 > IO_SPACE_LIMIT) {
> > +		/* if it's too big check if 64K space can be reserved */
> > +		if (allocated_size + SZ_64K - 1 > IO_SPACE_LIMIT) {
> > +			err = -E2BIG;
> > +			goto end_register;
> > +		}
> > +
> > +		size = SZ_64K;
> > +		pr_warn("Requested IO range too big, new size set to 64K\n");
> > +	}
> > +
> > +	/* add the range to the list */
> > +	range = kzalloc(sizeof(*range), GFP_KERNEL);
> > +	if (!range) {
> > +		err = -ENOMEM;
> > +		goto end_register;
> > +	}
> > +
> > +	range->start = addr;
> > +	range->size = size;
> > +
> > +	list_add_tail(&range->list, &io_range_list);
> > +
> > +end_register:
> > +	spin_unlock(&io_range_lock);
> > +#endif
> > +
> > +	return err;
> > +}
> > +
> > +phys_addr_t pci_pio_to_address(unsigned long pio)
> > +{
> > +	phys_addr_t address = (phys_addr_t)OF_BAD_ADDR;

Hi Al,

> 
> This reference to OF_BAD_ADDR is the only thing I'm seeing in this
> patch that is DT specific.
> 
> Couldn't these helper functions be more useful if provided outside
> of DT, perhaps in the PCI code instead?  I was giving some thought
> to re-using them for ACPI support of PCI but don't want to have to
> build DT if I'm not really going to use it.

The reason why I've put it (now) in drivers/of is that the code is only
used by DT specific code. At some moment one of the older series put
it into drivers/pci but I was trying to make it more clear that this
is DT specific.

If you find this useful for ACPI (and this series lands in v3.18) then
I suggest you send a patch to move it into drivers/pci?

Best regards,
Liviu

> 
> > +#ifdef PCI_IOBASE
> > +	struct io_range *range;
> > +	resource_size_t allocated_size = 0;
> > +
> > +	if (pio > IO_SPACE_LIMIT)
> > +		return address;
> > +
> > +	spin_lock(&io_range_lock);
> > +	list_for_each_entry(range, &io_range_list, list) {
> > +		if (pio >= allocated_size && pio < allocated_size + range->size) {
> > +			address = range->start + pio - allocated_size;
> > +			break;
> > +		}
> > +		allocated_size += range->size;
> > +	}
> > +	spin_unlock(&io_range_lock);
> > +#endif
> > +
> > +	return address;
> > +}
> > +
> >  unsigned long __weak pci_address_to_pio(phys_addr_t address)
> >  {
> > +#ifdef PCI_IOBASE
> > +	struct io_range *res;
> > +	resource_size_t offset = 0;
> > +	unsigned long addr = -1;
> > +
> > +	spin_lock(&io_range_lock);
> > +	list_for_each_entry(res, &io_range_list, list) {
> > +		if (address >= res->start && address < res->start + res->size) {
> > +			addr = res->start - address + offset;
> > +			break;
> > +		}
> > +		offset += res->size;
> > +	}
> > +	spin_unlock(&io_range_lock);
> > +
> > +	return addr;
> > +#else
> >  	if (address > IO_SPACE_LIMIT)
> >  		return (unsigned long)-1;
> >  
> >  	return (unsigned long) address;
> > +#endif
> >  }
> >  
> >  static int __of_address_to_resource(struct device_node *dev,
> > diff --git a/include/linux/of_address.h b/include/linux/of_address.h
> > index fb7b722..f8cc7da 100644
> > --- a/include/linux/of_address.h
> > +++ b/include/linux/of_address.h
> > @@ -55,7 +55,9 @@ extern void __iomem *of_iomap(struct device_node *device, int index);
> >  extern const __be32 *of_get_address(struct device_node *dev, int index,
> >  			   u64 *size, unsigned int *flags);
> >  
> > +extern int pci_register_io_range(phys_addr_t addr, resource_size_t size);
> >  extern unsigned long pci_address_to_pio(phys_addr_t addr);
> > +extern phys_addr_t pci_pio_to_address(unsigned long pio);
> >  
> >  extern int of_pci_range_parser_init(struct of_pci_range_parser *parser,
> >  			struct device_node *node);
> > 
> 
> 
> -- 
> ciao,
> al
> -----------------------------------
> Al Stone
> Software Engineer
> Red Hat, Inc.
> ahs3@redhat.com
> -----------------------------------
> 

-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯


  reply	other threads:[~2014-09-30  8:59 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 14:29 [PATCH v13 00/12] Support for creating generic PCI host bridges from DT Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 01/12] asm-generic/io.h: Fix ioport_map() for !CONFIG_GENERIC_IOMAP Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 02/12] of/pci: Add pci_register_io_range() and pci_pio_to_address() Liviu Dudau
2014-09-29 19:20   ` Al Stone
2014-09-30  8:59     ` Liviu Dudau [this message]
2014-09-29 14:29 ` [PATCH v13 03/12] ARM: Define PCI_IOBASE as the base of virtual PCI IO space Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 04/12] of/pci: Define of_pci_range_to_resource() only when CONFIG_PCI=y Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 05/12] of/pci: Move of_pci_range_to_resources() to of/address.c Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 06/12] of/pci: Fix the conversion of IO ranges into IO resources Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 07/12] PCI: Add generic domain handling Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 08/12] of/pci: Add pci_get_new_domain_nr() and of_get_pci_domain_nr() Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 09/12] of/pci: Add support for parsing PCI host bridge resources from DT Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 10/12] PCI: Assign unassigned bus resources in pci_scan_root_bus() Liviu Dudau
2014-09-29 18:25   ` Yinghai Lu
2014-09-29 19:06     ` Yinghai Lu
2014-09-29 21:02       ` Benjamin Herrenschmidt
2014-09-29 21:33         ` Bjorn Helgaas
2014-09-29 22:31           ` Benjamin Herrenschmidt
2014-09-29 23:08             ` Bjorn Helgaas
2014-09-30  8:54               ` Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 11/12] PCI: Add pci_remap_iospace() to map bus I/O resources Liviu Dudau
2014-09-29 14:29 ` [PATCH v13 12/12] arm64: Add architectural support for PCI Liviu Dudau
2014-09-29 19:43 ` [PATCH v13 00/12] Support for creating generic PCI host bridges from DT Bjorn Helgaas
2014-09-30 10:39   ` Liviu Dudau
2014-09-30 16:18     ` Bjorn Helgaas
2014-09-30 16:45       ` Liviu Dudau
2014-09-30 16:54       ` Liviu Dudau
2014-10-08  7:44         ` Robert Richter
2014-10-08  9:13           ` Liviu Dudau
2014-10-08 10:36             ` Robert Richter
2014-10-08 11:46               ` 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=20140930085933.GM841@e106497-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=ahs3@redhat.com \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jg1.han@samsung.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=jiang.liu@linux.intel.com \
    --cc=kgene.kim@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=okaya@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tinamdar@apm.com \
    --cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).