of/pci: Provide common support for PCI DT parsing
Subsystems (6)
v8 cover of/pci: Provide common support for PCI DT parsing
This patchset factors out duplicated code associated with parsing PCI DT "ranges" properties across the architectures and introduces a "ranges" parser. This parser "of_pci_range_parser" can be used directly by ARM host bridge drivers enabling them to obtain ranges from device trees.
I've included the Reviewed-by, Tested-by and Acked-by's received from v5/v6/v7 in this patchset, earlier versions of this patchset (v3) have been tested-by:
Thierry Reding <[email protected]>
Jingoo Han <[email protected]>
I've tested that this patchset builds and runs on ARM and that it builds on PowerPC, x86_64 and MIPS.
Compared to the v7 sent by Andrew Murray, the following changes have been made (please note that the first patch is unchanged from v7):
* Rename of_pci_range_parser to of_pci_range_parser_init and of_pci_process_ranges to of_pci_range_parser_one as suggested by Grant Likely.
* Reverted back to using a switch statement instead of if/else in pci_process_bridge_OF_ranges. Grant Likely highlighted this change from the original code which was unnecessary.
* Squashed in a patch provided by Gabor Juhos which fixes build errors on MIPS found in the last patchset.
Compared to the v6 sent by Andrew Murray, the following changes have been made in response to build errors/warnings:
* Inclusion of linux/of_address.h in of_pci.c as suggested by Michal Simek to prevent compilation failures on Microblaze (and others) and his ack.
* Use of externs, static inlines and a typo in linux/of_address.h in response to linker errors (multiple defination) on x86_64 as spotted by a kbuild test robot on (jcooper/linux.git mvebu/drivers)
* Add EXPORT_SYMBOL_GPL to of_pci_range_parser function to be consistent with of_pci_process_ranges function
Compared to the v5 sent by Andrew Murray, the following changes have been made:
* Use of CONFIG_64BIT instead of CONFIG_[a32bitarch] as suggested by Rob Herring in drivers/of/of_pci.c
* Added forward declaration of struct pci_controller in linux/of_pci.h to prevent compiler warning as suggested by Thomas Petazzoni
* Improved error checking (!range check), removal of unnecessary be32_to_cpup call, improved formatting of struct of_pci_range_parser layout and replacement of macro with a static inline. All suggested by Rob Herring.
Compared to the v4 (incorrectly labelled v3) sent by Andrew Murray, the following changes have been made:
* Split the patch as suggested by Rob Herring
Compared to the v3 sent by Andrew Murray, the following changes have been made:
* Unify and move duplicate pci_process_bridge_OF_ranges functions to drivers/of/of_pci.c as suggested by Rob Herring
* Fix potential build errors with Microblaze/MIPS
Compared to "[PATCH v5 01/17] of/pci: Provide support for parsing PCI DT ranges property", the following changes have been made:
* Correct use of IORESOURCE_* as suggested by Russell King
* Improved interface and naming as suggested by Thierry Reding
Compared to the v2 sent by Andrew Murray, Thomas Petazzoni did:
* Add a memset() on the struct of_pci_range_iter when starting the for loop in for_each_pci_range(). Otherwise, with an uninitialized of_pci_range_iter, of_pci_process_ranges() may crash.
* Add parenthesis around 'res', 'np' and 'iter' in the for_each_of_pci_range macro definitions. Otherwise, passing something like &foobar as 'res' didn't work.
* Rebased on top of 3.9-rc2, which required fixing a few conflicts in the Microblaze code.
v2:
This follows on from suggestions made by Grant Likely (marc.info/?l=linux-kernel&m=136079602806328)
Andrew Murray (3):
of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and
PowerPC
of/pci: Provide support for parsing PCI DT ranges property of/pci: mips: convert to common of_pci_range_parser
arch/microblaze/include/asm/pci-bridge.h | 5 +- arch/microblaze/pci/pci-common.c | 192 ------------------------------ arch/mips/pci/pci.c | 51 +++----- arch/powerpc/include/asm/pci-bridge.h | 5 +- arch/powerpc/kernel/pci-common.c | 192 ------------------------------ drivers/of/address.c | 67 +++++++++++ drivers/of/of_pci.c | 173 +++++++++++++++++++++++++++ include/linux/of_address.h | 48 ++++++++ include/linux/of_pci.h | 4 + 9 files changed, 313 insertions(+), 424 deletions(-)
PATCH v8 1/3 of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC
The pci_process_bridge_OF_ranges function, used to parse the "ranges" property of a PCI host device, is found in both Microblaze and PowerPC architectures. These implementations are nearly identical. This patch moves this common code to a common place.
--- arch/microblaze/include/asm/pci-bridge.h | 5 +- arch/microblaze/pci/pci-common.c | 192 ---------------------------- arch/powerpc/include/asm/pci-bridge.h | 5 +- arch/powerpc/kernel/pci-common.c | 192 ---------------------------- drivers/of/of_pci.c | 200 ++++++++++++++++++++++++++++++ include/linux/of_pci.h | 4 + 6 files changed, 206 insertions(+), 392 deletions(-)
arch/microblaze/include/asm/pci-bridge.h +1 -4
@@ -10,6 +10,7 @@#include <linux/pci.h> #include <linux/list.h> #include <linux/ioport.h> +#include <linux/of_pci.h> struct device_node ;
@@ -132,10 +133,6 @@ extern void setup_indirect_pci(struct pci_controller *hose,extern struct pci_controller *pci_find_hose_for_OF_device (struct device_node *node); -/* Fill up host controller resources from the OF node */ -extern void pci_process_bridge_OF_ranges (struct pci_controller *hose, -struct device_node *dev,int primary); -/* Allocate & free a PCI host bridge structure */ extern struct pci_controller *pcibios_alloc_controller (struct device_node *dev);extern void pcibios_free_controller (struct pci_controller *phb);
arch/microblaze/pci/pci-common.c +0 -192
198 lines not on this page · raw message
arch/powerpc/include/asm/pci-bridge.h +1 -4
@@ -10,6 +10,7 @@#include <linux/pci.h> #include <linux/list.h> #include <linux/ioport.h> +#include <linux/of_pci.h> #include <asm-generic/pci-bridge.h> struct device_node ;
@@ -231,10 +232,6 @@ extern int pcibios_map_io_space(struct pci_bus *bus);extern struct pci_controller *pci_find_hose_for_OF_device (struct device_node * node); -/* Fill up host controller resources from the OF node */ -extern void pci_process_bridge_OF_ranges (struct pci_controller *hose, -struct device_node *dev,int primary); -/* Allocate & free a PCI host bridge structure */ extern struct pci_controller *pcibios_alloc_controller (struct device_node *dev);extern void pcibios_free_controller (struct pci_controller *phb);
arch/powerpc/kernel/pci-common.c +0 -192
198 lines not on this page · raw message
drivers/of/of_pci.c +200 -0
209 lines not on this page · raw message
include/linux/of_pci.h +4 -0
@@ -11,4 +11,8 @@ struct device_node;struct device_node *of_pci_find_child_device (struct device_node *parent,unsigned int devfn); +struct pci_controller ; +void pci_process_bridge_OF_ranges (struct pci_controller *hose, +struct device_node *dev,int primary); +#endif
Signature · 1 line
1.7.0.4
Re: [PATCH v8 1/3] of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC
Quoted 4 lines · Andrew Murray
The
pci_process_bridge_OF_rangesfunction, used to parse the "ranges" property of a PCI host device, is found in both Microblaze and PowerPC architectures. These implementations are nearly identical. This patch moves this common code to a common place.
What's happening with this ? I'd like to avoid that patch for now as I'm doing some changes to pci_process_bridge_OF_ranges which are fairly urgent (I might even stick them in the current merge window) to deal with memory windows having separate offsets.
There's also a few hacks in there that are really ppc specific...
I think the right long term approach is to change the way powerpc (and microblaze ?) initializes PCI host bridges. Move it away from setup_arch() (which is a PITA anyway since it's way too early) to an early init call of some sort, and encapsulate the new struct pci_host_bridge.
We can then directly configure the host bridge windows rather than having this "intermediary" set of resources in our pci_controller and in fact move most of the fields from pci_controller to pci_host_bridge to the point where the former can remain as a simple platform specific wrapper if needed.
So for new stuff (hint: DT based ARM PCI) or stuff that has to deal with a lot less archaic platforms (hint: Microblaze), I'd recommend going straight for that approach rather than perpetuating the PowerPC code which I'll try to deal with in the next few monthes.
Cheers,
Ben.
PATCH v8 1/3 of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC
Quoted 10 lines · Benjamin Herrenschmidt
Quoted 4 lines · Andrew Murray
The
pci_process_bridge_OF_rangesfunction, used to parse the "ranges" property of a PCI host device, is found in both Microblaze and PowerPC architectures. These implementations are nearly identical. This patch moves this common code to a common place.What's happening with this ? I'd like to avoid that patch for now as I'm doing some changes to
pci_process_bridge_OF_rangeswhich are fairly urgent (I might even stick them in the current merge window) to deal with memory windows having separate offsets.
There were no objections to this latest revision until now and it is currently sitting with Jason Cooper (mvebu-next/pcie). [1]
Quoted 9 lines
There's also a few hacks in there that are really ppc specific...
I think the right long term approach is to change the way powerpc (and microblaze ?) initializes PCI host bridges. Move it away from
setup_arch()(which is a PITA anyway since it's way too early) to an early init call of some sort, and encapsulate the new structpci_host_bridge.
Quoted 5 lines
We can then directly configure the host bridge windows rather than having this "intermediary" set of resources in our
pci_controllerand in fact move most of the fields frompci_controllertopci_host_bridgeto the point where the former can remain as a simple platform specific wrapper if needed.
This is a view that was also shared by Bjorn [2] when I attempted to submit a patchset which moves struct pci_controller to asm-generic.
Quoted 5 lines
So for new stuff (hint: DT based ARM PCI) or stuff that has to deal with a lot less archaic platforms (hint: Microblaze), I'd recommend going straight for that approach rather than perpetuating the PowerPC code which I'll try to deal with in the next few monthes.
The motativation for my patchsets were to give a way for ARM PCI host bridge drivers to parse the DT ranges property, but this snow-balled into unifying pci_process_bridge_OF_ranges.
My v8 patchset provides a of_pci_range_parser which is used directly by a few ARM PCI DT host bridge drivers, this has been generally accepted and tested. I don't see why this can't remain and so I'd really like to keep this around.
Grant, Benjamin would you be happy for me to resubmit this series which provides the of_pci_range_parser which will be used by the separate implementations of pci_process_bridge_OF_ranges in PowerPC/Microblaze?
Benjamin are you able to still use of_pci_range_parser in your 'Support per-aperture memory offset' patch?
Thanks,
Andrew Murray
[1] https://lkml.org/lkml/2013/4/22/505
[2] https://patchwork.kernel.org/patch/2487671
Quoted 6 lines
Cheers,
Ben.
PATCH v8 1/3 of/pci: Unify pci_process_bridge_OF_ranges from Microblaze and PowerPC
Quoted 3 lines · Andrew Murray
There were no objections to this latest revision until now and it is currently sitting with Jason Cooper (mvebu-next/pcie). [1]
Ok, well I've just sent Linus a pull request for my changes so at least drop the powerpc changes from your tree for the time being.
Quoted 2 lines
This is a view that was also shared by Bjorn [2] when I attempted to submit a patchset which moves struct
pci_controllerto asm-generic.
Right, it's the logical way to go
Quoted 3 lines
The motativation for my patchsets were to give a way for ARM PCI host bridge drivers to parse the DT ranges property, but this snow-balled into unifying
pci_process_bridge_OF_ranges.
Which I understand, I would probably have done the same thing in your shoes :-)
Quoted 4 lines
My v8 patchset provides a
of_pci_range_parserwhich is used directly by a few ARM PCI DT host bridge drivers, this has been generally accepted and tested. I don't see why this can't remain and so I'd really like to keep this around.
Sure, no objection, in fact I should/could probably update my new code to use it as well.
Quoted 4 lines
Grant, Benjamin would you be happy for me to resubmit this series which provides the
of_pci_range_parserwhich will be used by the separate implementations ofpci_process_bridge_OF_rangesin PowerPC/Microblaze?
Sure, in fact feel free to update my new code if you have more bandwidth than I do, it should hit Linus tree soon hopefully unless he objects to me having a second pull request this merge window...
Quoted 2 lines
Benjamin are you able to still use
of_pci_range_parserin your 'Support per-aperture memory offset' patch?
I see no reason why not. I just haven't looked into it much, I admit, being bogged down with a pile of new HW bringup in the lab etc...
Cheers,
Ben.
PATCH v8 2/3 of/pci: Provide support for parsing PCI DT ranges property
In reply to Andrew MurrayThis patch factors out common implementation patterns to reduce overall kernel code and provide a means for host bridge drivers to directly obtain struct resources from the DT's ranges property without relying on architecture specific DT handling. This will make it easier to write archiecture independent host bridge drivers and mitigate against further duplication of DT parsing code.
This patch can be used in the following way:
struct of_pci_range_parser parser;
struct of_pci_range range;
if (of_pci_range_parser_init(&parser, np))
; //no ranges property
for_each_of_pci_range(&parser, &range) {
/*
directly access properties of the address range, e.g.:
range.pci_space, range.pci_addr, range.cpu_addr,
range.size, range.flags
alternatively obtain a struct resource, e.g.:
struct resource res;
of_pci_range_to_resource(&range, np, &res);
*/
}Additionally the implementation takes care of adjacent ranges and merges them into a single range (as was the case with powerpc and microblaze).
--- drivers/of/address.c | 67 ++++++++++++++++++++++++++ drivers/of/of_pci.c | 113 +++++++++++++++++--------------------------- include/linux/of_address.h | 48 +++++++++++++++++++ 3 files changed, 158 insertions(+), 70 deletions(-)
drivers/of/address.c +67 -0
@@ -227,6 +227,73 @@ int of_pci_address_to_resource(struct device_node *dev, int bar,return __of_address_to_resource (dev, addrp, size, flags,NULL , r); }EXPORT_SYMBOL_GPL (of_pci_address_to_resource); + +int of_pci_range_parser_init (struct of_pci_range_parser *parser, +struct device_node *node) +{ +const int na =3 , ns =2 ; +int rlen; + + parser->node = node; + parser->pna =of_n_addr_cells (node); + parser->np = parser->pna + na + ns; + + parser->range =of_get_property (node,"ranges" , &rlen); +if (parser->range ==NULL ) +return -ENOENT ; + + parser->end = parser->range + rlen /sizeof (__be32); + +return 0 ; +} +EXPORT_SYMBOL_GPL (of_pci_range_parser_init); + +struct of_pci_range *of_pci_range_parser_one (struct of_pci_range_parser *parser, +struct of_pci_range *range) +{ +const int na =3 , ns =2 ; + +if (!range) +return NULL ; + +if (!parser->range || parser->range + parser->np > parser->end) +return NULL ; + + range->pci_space = parser->range[0 ]; + range->flags =of_bus_pci_get_flags (parser->range); + range->pci_addr =of_read_number (parser->range +1 , ns); + range->cpu_addr =of_translate_address (parser->node, + parser->range + na); + range->size =of_read_number (parser->range + parser->pna + na, ns); + + parser->range += parser->np; + +/* Now consume following elements while they are contiguous */ +while (parser->range + parser->np <= parser->end) { +u32 flags, pci_space; +u64 pci_addr, cpu_addr, size; + + pci_space =be32_to_cpup (parser->range); + flags =of_bus_pci_get_flags (parser->range); + pci_addr =of_read_number (parser->range +1 , ns); + cpu_addr =of_translate_address (parser->node, + parser->range + na); + size =of_read_number (parser->range + parser->pna + na, ns); + +if (flags != range->flags) +break ; +if (pci_addr != range->pci_addr + range->size || + cpu_addr != range->cpu_addr + range->size) +break ; + + range->size += size; + parser->range += parser->np; + } + +return range; +} +EXPORT_SYMBOL_GPL (of_pci_range_parser_one); +#endif /* CONFIG_PCI */ /*
drivers/of/of_pci.c +43 -70
189 lines not on this page · raw message
include/linux/of_address.h +48 -0
66 lines not on this page · raw message
Signature · 1 line
1.7.0.4
Re: [PATCH v8 2/3] of/pci: Provide support for parsing PCI DT ranges property
Quoted 31 lines · Andrew Murray
This patch factors out common implementation patterns to reduce overall kernel code and provide a means for host bridge drivers to directly obtain struct resources from the DT's ranges property without relying on architecture specific DT handling. This will make it easier to write archiecture independent host bridge drivers and mitigate against further duplication of DT parsing code.
This patch can be used in the following way:
struct of_pci_range_parser parser; struct of_pci_range range; if (of_pci_range_parser_init(&parser, np)) ; //no ranges property for_each_of_pci_range(&parser, &range) { /* directly access properties of the address range, e.g.: range.pci_space, range.pci_addr, range.cpu_addr, range.size, range.flags alternatively obtain a struct resource, e.g.: struct resource res; of_pci_range_to_resource(&range, np, &res); */ }Additionally the implementation takes care of adjacent ranges and merges them into a single range (as was the case with powerpc and microblaze).
Quoted 7 lines
Signed-off-by Andrew Murray <[email protected]>Signed-off-by Liviu Dudau <[email protected]>Signed-off-by Thomas Petazzoni <[email protected]>Reviewed-by Rob Herring <[email protected]>Tested-by Thomas Petazzoni <[email protected]>Tested-by Linus Walleij <[email protected]>Acked-by Grant Likely <[email protected]>
Hi Andrew,
I tested this patch with Exynos5440.
It works properly.
Thank you.
Best regards,
Jingoo Han
Quoted 358 lines
--- drivers/of/address.c | 67 ++++++++++++++++++++++++++ drivers/of/of_pci.c | 113 +++++++++++++++++--------------------------- include/linux/of_address.h | 48 +++++++++++++++++++ 3 files changed, 158 insertions(+), 70 deletions(-)drivers/of/address.c +67
-0@@ -227,6 +227,73 @@ int of_pci_address_to_resource(struct device_node *dev, int bar,return __of_address_to_resource (dev, addrp, size, flags,NULL , r); }EXPORT_SYMBOL_GPL (of_pci_address_to_resource); + +int of_pci_range_parser_init (struct of_pci_range_parser *parser, +struct device_node *node) +{ +const int na =3 , ns =2 ; +int rlen; + + parser->node = node; + parser->pna =of_n_addr_cells (node); + parser->np = parser->pna + na + ns; + + parser->range =of_get_property (node,"ranges" , &rlen); +if (parser->range ==NULL ) +return -ENOENT ; + + parser->end = parser->range + rlen /sizeof (__be32); + +return 0 ; +} +EXPORT_SYMBOL_GPL (of_pci_range_parser_init); + +struct of_pci_range *of_pci_range_parser_one (struct of_pci_range_parser *parser, +struct of_pci_range *range) +{ +const int na =3 , ns =2 ; + +if (!range) +return NULL ; + +if (!parser->range || parser->range + parser->np > parser->end) +return NULL ; + + range->pci_space = parser->range[0 ]; + range->flags =of_bus_pci_get_flags (parser->range); + range->pci_addr =of_read_number (parser->range +1 , ns); + range->cpu_addr =of_translate_address (parser->node, + parser->range + na); + range->size =of_read_number (parser->range + parser->pna + na, ns); + + parser->range += parser->np; + +/* Now consume following elements while they are contiguous */ +while (parser->range + parser->np <= parser->end) { +u32 flags, pci_space; +u64 pci_addr, cpu_addr, size; + + pci_space =be32_to_cpup (parser->range); + flags =of_bus_pci_get_flags (parser->range); + pci_addr =of_read_number (parser->range +1 , ns); + cpu_addr =of_translate_address (parser->node, + parser->range + na); + size =of_read_number (parser->range + parser->pna + na, ns); + +if (flags != range->flags) +break ; +if (pci_addr != range->pci_addr + range->size || + cpu_addr != range->cpu_addr + range->size) +break ; + + range->size += size; + parser->range += parser->np; + } + +return range; +} +EXPORT_SYMBOL_GPL (of_pci_range_parser_one); +#endif /* CONFIG_PCI */ /* drivers/of/of_pci.c +43
-70@@ -2,6 +2,7 @@#include <linux/export.h> #include <linux/of.h> #include <linux/of_pci.h> +#include <linux/of_address.h> #include <asm/prom.h> #if defined(CONFIG_PPC32 ) || defined(CONFIG_PPC64 ) || defined(CONFIG_MICROBLAZE )@@ -82,67 +83,42 @@ EXPORT_SYMBOL_GPL(of_pci_find_child_device);void pci_process_bridge_OF_ranges (struct pci_controller *hose,struct device_node *dev,int primary) { -const u32 *ranges; -int rlen; -int pna =of_n_addr_cells (dev); -int np = pna +5 ;int memno =0 , isa_hole =-1 ; -u32 pci_space; -unsigned long long pci_addr, cpu_addr, pci_next, cpu_next, size;unsigned long long isa_mb =0 ;struct resource *res; +struct of_pci_range range; +struct of_pci_range_parser parser;pr_info ("PCI host bridge %s %s ranges:\n" , dev->full_name, primary ?"(primary)" :"" ); -/* Get ranges property */ - ranges =of_get_property (dev,"ranges" , &rlen); -if (ranges ==NULL ) +/* Check for ranges property */ +if (of_pci_range_parser_init (&parser, dev))return ; -/* Parse it */ pr_debug ("Parsing ranges property...\n" ); -while ((rlen -= np *4 ) >=0 ) { +for_each_of_pci_range (&parser, &range) {/* Read next ranges element */ - pci_space = ranges[0 ]; - pci_addr =of_read_number (ranges +1 ,2 ); - cpu_addr =of_translate_address (dev, ranges +3 ); - size =of_read_number (ranges + pna +3 ,2 ); - -pr_debug ("pci_space: 0x%08x pci_addr:0x%016llx " , - pci_space, pci_addr); -pr_debug ("cpu_addr:0x%016llx size:0x%016llx\n" , - cpu_addr, size); - - ranges += np; +pr_debug ("pci_space: 0x%08x pci_addr: 0x%016llx " , + range.pci_space, range.pci_addr); +pr_debug ("cpu_addr: 0x%016llx size: 0x%016llx\n" , + range.cpu_addr, range.size);/* If we failed translation or got a zero-sized region * (some FW try to feed us with non sensical zero sized regions * such as power3 which look like some kind of attempt * at exposing the VGA memory hole) */ -if (cpu_addr ==OF_BAD_ADDR || size ==0 ) +if (range.cpu_addr ==OF_BAD_ADDR || range.size ==0 )continue ; -/* Now consume following elements while they are contiguous */ -for (; rlen >= np *sizeof (u32); - ranges += np, rlen -= np *4 ) { -if (ranges[0 ] != pci_space) -break ; - pci_next =of_read_number (ranges +1 ,2 ); - cpu_next =of_translate_address (dev, ranges +3 ); -if (pci_next != pci_addr + size || - cpu_next != cpu_addr + size) -break ; - size +=of_read_number (ranges + pna +3 ,2 ); - } -/* Act based on address space type */ res =NULL ; -switch ((pci_space >>24 ) &0x3 ) { -case 1 :/* PCI IO space */ +switch (range.flags &IORESOURCE_TYPE_BITS ) { +case IORESOURCE_IO :pr_info (" IO 0x%016llx..0x%016llx -> 0x%016llx\n" , - cpu_addr, cpu_addr + size -1 , pci_addr); + range.cpu_addr, range.cpu_addr + range.size -1 , + range.pci_addr);/* We support only one IO range */ if (hose->pci_io_size) {@@ -151,11 +127,12 @@ void pci_process_bridge_OF_ranges(struct pci_controller *hose, }#if (!IS_ENABLED (CONFIG_64BIT ))/* On 32 bits, limit I/O space to 16MB */ -if (size >0x01000000 ) - size =0x01000000 ; +if (range.size >0x01000000 ) + range.size =0x01000000 ;/* 32 bits needs to map IOs here */ - hose->io_base_virt =ioremap (cpu_addr, size); + hose->io_base_virt =ioremap (range.cpu_addr, + range.size);/* Expect trouble if pci_addr is not 0 */ if (primary)@@ -165,19 +142,21 @@ void pci_process_bridge_OF_ranges(struct pci_controller *hose,/* pci_io_size and io_base_phys always represent IO * space starting at 0 so we factor in pci_addr */ - hose->pci_io_size = pci_addr + size; - hose->io_base_phys = cpu_addr - pci_addr; + hose->pci_io_size = range.pci_addr + range.size; + hose->io_base_phys = range.cpu_addr - range.pci_addr;/* Build resource */ res = &hose->io_resource; - res->flags =IORESOURCE_IO ; - res->start = pci_addr; + range.cpu_addr = range.pci_addr; +break ; -case 2 :/* PCI Memory space */ -case 3 :/* PCI 64 bits Memory space */ + +case IORESOURCE_MEM :pr_info (" MEM 0x%016llx..0x%016llx -> 0x%016llx %s\n" , - cpu_addr, cpu_addr + size -1 , pci_addr, - (pci_space &0x40000000 ) ?"Prefetch" :"" ); + range.cpu_addr, range.cpu_addr + range.size -1 , + range.pci_addr, + (range.pci_space &0x40000000 ) ? +"Prefetch" :"" );/* We support only 3 memory ranges */ if (memno >=3 ) {@@ -185,13 +164,13 @@ void pci_process_bridge_OF_ranges(struct pci_controller *hose,continue ; }/* Handles ISA memory hole space here */ -if (pci_addr ==0 ) { - isa_mb = cpu_addr; +if (range.pci_addr ==0 ) { + isa_mb = range.cpu_addr; isa_hole = memno;if (primary || isa_mem_base ==0 ) - isa_mem_base = cpu_addr; - hose->isa_mem_phys = cpu_addr; - hose->isa_mem_size = size; + isa_mem_base = range.cpu_addr; + hose->isa_mem_phys = range.cpu_addr; + hose->isa_mem_size = range.size; }/* We get the PCI/Mem offset from the first range or @@ -199,30 +178,24 @@ void pci_process_bridge_OF_ranges(struct pci_controller *hose,* hole. If they don't match, bugger. */ if (memno ==0 || - (isa_hole >=0 && pci_addr !=0 && + (isa_hole >=0 && range.pci_addr !=0 && hose->pci_mem_offset == isa_mb)) - hose->pci_mem_offset = cpu_addr - pci_addr; -else if (pci_addr !=0 && - hose->pci_mem_offset != cpu_addr - pci_addr) { + hose->pci_mem_offset = range.cpu_addr - + range.pci_addr; +else if (range.pci_addr !=0 && + hose->pci_mem_offset != range.cpu_addr - + range.pci_addr) {pr_info (" \\--> Skipped (offset mismatch) !\n" );continue ; }/* Build resource */ res = &hose->mem_resources[memno++]; - res->flags =IORESOURCE_MEM ; -if (pci_space &0x40000000 ) - res->flags |=IORESOURCE_PREFETCH ; - res->start = cpu_addr; +break ; } -if (res !=NULL ) { - res->name = dev->full_name; - res->end = res->start + size -1 ; - res->parent =NULL ; - res->sibling =NULL ; - res->child =NULL ; - } +if (res !=NULL ) +of_pci_range_to_resource (&range, dev, res); }/* If there's an ISA hole and the pci_mem_offset is -not- matching include/linux/of_address.h +48
-1@@ -4,6 +4,36 @@#include <linux/errno.h> #include <linux/of.h> +struct of_pci_range_parser { +struct device_node *node; +const __be32 *range; +const __be32 *end; +int np; +int pna; +}; + +struct of_pci_range { +u32 pci_space; +u64 pci_addr; +u64 cpu_addr; +u64 size; +u32 flags; +}; + +#define for_each_of_pci_range (parser, range) \ + for (; of_pci_range_parser_one(parser, range);) + +static inline void of_pci_range_to_resource (struct of_pci_range *range, +struct device_node *np, +struct resource *res) +{ + res->flags = range->flags; + res->start = range->cpu_addr; + res->end = range->cpu_addr + range->size -1 ; + res->parent = res->child = res->sibling =NULL ; + res->name = np->full_name; +} +#ifdef CONFIG_OF_ADDRESS extern u64 of_translate_address (struct device_node *np,const __be32 *addr);extern bool of_can_translate_address (struct device_node *dev);@@ -27,6 +57,11 @@ static inline unsigned long pci_address_to_pio(phys_addr_t addr) { return -1; }#define pci_address_to_pio pci_address_to_pio#endif +extern int of_pci_range_parser_init (struct of_pci_range_parser *parser, +struct device_node *node); +extern struct of_pci_range *of_pci_range_parser_one ( +struct of_pci_range_parser *parser, +struct of_pci_range *range);#else /* CONFIG_OF_ADDRESS */ #ifndef of_address_to_resource static inline int of_address_to_resource(struct device_node *dev, int index,@@ -53,6 +88,19 @@ static inline const __be32 *of_get_address(struct device_node *dev, int index, {return NULL ; } + +static inline int of_pci_range_parser_init (struct of_pci_range_parser *parser, +struct device_node *node) +{ +return -1 ; +} + +static inline struct of_pci_range *of_pci_range_parser_one ( +struct of_pci_range_parser *parser, +struct of_pci_range *range) +{ +return NULL ; +}#endif /* CONFIG_OF_ADDRESS */ --1.7.0.4
PATCH v8 3/3 of/pci: mips: convert to common of_pci_range_parser
In reply to Andrew MurrayThis patch converts the pci_load_of_ranges function to use the new common of_pci_range_parser.
--- arch/mips/pci/pci.c | 51 +++++++++++++++++++-------------------------------- 1 files changed, 19 insertions(+), 32 deletions(-)
arch/mips/pci/pci.c +19 -32
@@ -122,51 +122,38 @@ static void pcibios_scanbus(struct pci_controller *hose)#ifdef CONFIG_OF void pci_load_of_ranges (struct pci_controller *hose,struct device_node *node) { -const __be32 *ranges; -int rlen; -int pna =of_n_addr_cells (node); -int np = pna +5 ; +struct of_pci_range range; +struct of_pci_range_parser parser; +u32 res_type;pr_info ("PCI host bridge %s ranges:\n" , node->full_name); - ranges =of_get_property (node,"ranges" , &rlen); -if (ranges ==NULL ) -return ; hose->of_node = node; -while ((rlen -= np *4 ) >=0 ) { -u32 pci_space; +if (of_pci_range_parser_init (&parser, node)) +return ; + +for_each_of_pci_range (&parser, &range) {struct resource *res =NULL ; -u64 addr, size; - - pci_space =be32_to_cpup (&ranges[0 ]); - addr =of_translate_address (node, ranges +3 ); - size =of_read_number (ranges + pna +3 ,2 ); - ranges += np; -switch ((pci_space >>24 ) &0x3 ) { -case 1 :/* PCI IO space */ + +switch (range.flags &IORESOURCE_TYPE_BITS ) { +case IORESOURCE_IO :pr_info (" IO 0x%016llx..0x%016llx\n" , - addr, addr + size -1 ); + range.cpu_addr, + range.cpu_addr + range.size -1 ); hose->io_map_base = - (unsigned long )ioremap (addr, size); + (unsigned long )ioremap (range.cpu_addr, + range.size); res = hose->io_resource; - res->flags =IORESOURCE_IO ;break ; -case 2 :/* PCI Memory space */ -case 3 :/* PCI 64 bits Memory space */ +case IORESOURCE_MEM :pr_info (" MEM 0x%016llx..0x%016llx\n" , - addr, addr + size -1 ); + range.cpu_addr, + range.cpu_addr + range.size -1 ); res = hose->mem_resource; - res->flags =IORESOURCE_MEM ;break ; } -if (res !=NULL ) { - res->start = addr; - res->name = node->full_name; - res->end = res->start + size -1 ; - res->parent =NULL ; - res->sibling =NULL ; - res->child =NULL ; - } +if (res !=NULL ) +of_pci_range_to_resource (&range, node, res); } }#endif
Signature · 1 line
1.7.0.4
Quoted 6 lines · Andrew Murray
This patchset factors out duplicated code associated with parsing PCI DT "ranges" properties across the architectures and introduces a "ranges" parser. This parser "
of_pci_range_parser" can be used directly by ARM host bridge drivers enabling them to obtain ranges from device trees.
Quoted 8 lines
I've included the Reviewed-by, Tested-by and Acked-by's received from v5/v6/v7 in this patchset, earlier versions of this patchset (v3) have been tested-by:
Thierry Reding <[email protected]>
Jingoo Han <[email protected]>I've tested that this patchset builds and runs on ARM and that it builds on PowerPC,
x86_64and MIPS.
Andrew,
Unfortunately, the mvebu/drivers branch containing your series had to be dropped from arm-soc for v3.10. This was not due to your series, but since arm-soc's granularity is branches, your series was caught in the drop.
As the mvebu-pcie driver is now v3.11 material, I have taken the opportunity to upgrade from your v7 patchset to v8. You can find the whole branch at mvebu-next/pcie.
mvebu-next/pcie *will* be rebased onto v3.9 once it drops. Several dependencies will be removed (since they will have been merged into v3.9).
Once the rebase is done, I'll send a pull request to Arnd and Olof so we can get as many cycles on -next as possible.
thx,
Jason.
Quoted 101 lines
Compared to the v7 sent by Andrew Murray, the following changes have been made (please note that the first patch is unchanged from v7):
* Rename
of_pci_range_parsertoof_pci_range_parser_initandof_pci_process_rangestoof_pci_range_parser_oneas suggested by Grant Likely.* Reverted back to using a switch statement instead of if/else in
pci_process_bridge_OF_ranges. Grant Likely highlighted this change from the original code which was unnecessary.* Squashed in a patch provided by Gabor Juhos which fixes build errors on MIPS found in the last patchset.
Compared to the v6 sent by Andrew Murray, the following changes have been made in response to build errors/warnings:
* Inclusion of
linux/of_address.hinof_pci.cas suggested by Michal Simek to prevent compilation failures on Microblaze (and others) and his ack.* Use of externs, static inlines and a typo in
linux/of_address.hin response to linker errors (multiple defination) onx86_64as spotted by a kbuild test robot on (jcooper/linux.git mvebu/drivers)* Add
EXPORT_SYMBOL_GPLtoof_pci_range_parserfunction to be consistent withof_pci_process_rangesfunctionCompared to the v5 sent by Andrew Murray, the following changes have been made:
* Use of
CONFIG_64BITinstead of CONFIG_[a32bitarch] as suggested by Rob Herring indrivers/of/of_pci.c* Added forward declaration of struct
pci_controllerinlinux/of_pci.hto prevent compiler warning as suggested by Thomas Petazzoni* Improved error checking (!range check), removal of unnecessary
be32_to_cpupcall, improved formatting of structof_pci_range_parserlayout and replacement of macro with a static inline. All suggested by Rob Herring.Compared to the v4 (incorrectly labelled v3) sent by Andrew Murray, the following changes have been made:
* Split the patch as suggested by Rob Herring
Compared to the v3 sent by Andrew Murray, the following changes have been made:
* Unify and move duplicate
pci_process_bridge_OF_rangesfunctions todrivers/of/of_pci.cas suggested by Rob Herring* Fix potential build errors with Microblaze/MIPS
Compared to "[PATCH v5 01/17] of/pci: Provide support for parsing PCI DT ranges property", the following changes have been made:
* Correct use of IORESOURCE_* as suggested by Russell King
* Improved interface and naming as suggested by Thierry Reding
Compared to the v2 sent by Andrew Murray, Thomas Petazzoni did:
* Add a
memset()on the structof_pci_range_iterwhen starting the for loop infor_each_pci_range(). Otherwise, with an uninitializedof_pci_range_iter,of_pci_process_ranges()may crash.* Add parenthesis around 'res', 'np' and 'iter' in the
for_each_of_pci_rangemacro definitions. Otherwise, passing something like &foobar as 'res' didn't work.* Rebased on top of 3.9-rc2, which required fixing a few conflicts in the Microblaze code.
v2:
This follows on from suggestions made by Grant Likely (marc.info/?l=linux-kernel&m=136079602806328)Andrew Murray (3):
of/pci: Unifypci_process_bridge_OF_rangesfrom Microblaze and
PowerPC
of/pci: Provide support for parsing PCI DT ranges property of/pci: mips: convert to commonof_pci_range_parserarch/microblaze/include/asm/pci-bridge.h | 5 +- arch/microblaze/pci/pci-common.c | 192 ------------------------------ arch/mips/pci/pci.c | 51 +++----- arch/powerpc/include/asm/pci-bridge.h | 5 +- arch/powerpc/kernel/pci-common.c | 192 ------------------------------ drivers/of/address.c | 67 +++++++++++ drivers/of/of_pci.c | 173 +++++++++++++++++++++++++++ include/linux/of_address.h | 48 ++++++++ include/linux/of_pci.h | 4 + 9 files changed, 313 insertions(+), 424 deletions(-)_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 23 lines · Jason Cooper
Quoted 6 lines · Andrew Murray
This patchset factors out duplicated code associated with parsing PCI DT "ranges" properties across the architectures and introduces a "ranges" parser. This parser "
of_pci_range_parser" can be used directly by ARM host bridge drivers enabling them to obtain ranges from device trees.Quoted 8 lines
I've included the Reviewed-by, Tested-by and Acked-by's received from v5/v6/v7 in this patchset, earlier versions of this patchset (v3) have been tested-by:
Thierry Reding <[email protected]>
Jingoo Han <[email protected]>I've tested that this patchset builds and runs on ARM and that it builds on PowerPC,
x86_64and MIPS.Andrew,
Unfortunately, the mvebu/drivers branch containing your series had to be dropped from arm-soc for v3.10. This was not due to your series, but since arm-soc's granularity is branches, your series was caught in the drop.
Quoted 7 lines
As the mvebu-pcie driver is now v3.11 material, I have taken the opportunity to upgrade from your v7 patchset to v8. You can find the whole branch at mvebu-next/pcie.
mvebu-next/pcie *will* be rebased onto v3.9 once it drops. Several dependencies will be removed (since they will have been merged into v3.9).
s/v3.9/v3.10-rc1/g :)
Quoted 2 lines
Once the rebase is done, I'll send a pull request to Arnd and Olof so we can get as many cycles on -next as possible.
thx,
Jason.