of: Add support for named irq and reg
Subsystems (2)
cover of: Add support for named irq and reg
Hi Grant & Rob,
Following the previous patch submission [1], here is an updated series that adds the support for both reg and irq names.
A small improvement is done as well on the property with multiple strings helper function.
Please note that I've just realized that Russell's concern with the /proc/iomem readability might not even be valid in the DT case. I might be wrong, but it looks like devices created by of_device_alloc does not seems to call the insert_resource. It means that the /proc/iomem is mostly empty when the devices are created from device tree blob. I'm not sure it was done on purpose, but even if this is not the case, the fact is that this /proc/iomem entry does not seems to be used extensively.
That does not mean it cannot be improved, but it should change the urgency to fix that with regards to that series.
This series is based on 3.2-rc4 and is available here:git://gitorious.org/omap-pm/linux.git for_3.3/resource-names
Comments are welcome.
Auto comment: I'm not super happy with these new properties name because it is not really consistent. If you have any better idea, do not hesitate.
Thanks,
Benoit
[1] http://www.mail-archive.com/linux-omap at vger.kernel.org/msg57881.html
Benoit Cousson (3):
of/base: Take NULL string into account for property with multiple strings of/address: Add reg-names property to name an iomem resource of/irq: Add interrupts-names property to name an irq resource
.../devicetree/bindings/interrupts-names.txt | 50 ++++++++++++++++++++ Documentation/devicetree/bindings/reg-names.txt | 48 +++++++++++++++++++ drivers/of/address.c | 16 ++++-- drivers/of/base.c | 8 +-- drivers/of/irq.c | 11 ++++- 5 files changed, 122 insertions(+), 11 deletions(-) create mode 100644 Documentation/devicetree/bindings/interrupts-names.txt create mode 100644 Documentation/devicetree/bindings/reg-names.txt
PATCH 1/3 of/base: Take NULL string into account for property with multiple strings
The current implementation just ignore any NULL string inserted in a multiple strings property.
In some cases we can have a property with a fix number of strings but not necessarily used, like for example in a list of valid pinmux modes.
prop = "uart_rx", "uart_tx", "", "", "safe_mode";
Do no skip NULL string and take them into account in of_property_read_string_index and of_property_count_strings.
--- drivers/of/base.c | 8 +++----- 1 files changed, 3 insertions(+), 5 deletions(-)
drivers/of/base.c +3 -5
@@ -752,7 +752,7 @@ int of_property_read_string_index(struct device_node *np, const char *propname,for (i =0 ; total < prop->length; total += l, p += l) { l =strlen (p) +1 ; -if ((*p !=0 ) && (i++ == index)) { +if (i++ == index) { *output = p;return 0 ; }
@@ -790,11 +790,9 @@ int of_property_count_strings(struct device_node *np, const char *propname) p = prop->value; -for (i =0 ; total < prop->length; total += l, p += l) { +for (i =0 ; total < prop->length; total += l, p += l, i++) l =strlen (p) +1 ; -if (*p !=0 ) - i++; - } +return i; }EXPORT_SYMBOL_GPL (of_property_count_strings);
Signature · 1 line
1.7.0.4
PATCH 1/3 of/base: Take NULL string into account for property with multiple strings
Quoted 7 lines · Benoit Cousson
The current implementation just ignore any NULL string inserted in a multiple strings property.
In some cases we can have a property with a fix number of strings but not necessarily used, like for example in a list of valid pinmux modes.prop = "
uart_rx", "uart_tx", "", "", "safe_mode";
Quoted 7 lines
Do no skip NULL string and take them into account in
of_property_read_string_indexandof_property_count_strings.Reported-by Tony Lindgren <[email protected]>Signed-off-by Benoit Cousson <[email protected]>Cc Grant Likely <[email protected]>Cc Rob Herring <[email protected]>
This fix should be merged before people start doing workarounds in drivers for this:
Quoted 34 lines
--- drivers/of/base.c | 8 +++----- 1 files changed, 3 insertions(+), 5 deletions(-)drivers/of/base.c +3
-5@@ -752,7 +752,7 @@ int of_property_read_string_index(struct device_node *np, const char *propname,for (i =0 ; total < prop->length; total += l, p += l) { l =strlen (p) +1 ; -if ((*p !=0 ) && (i++ == index)) { +if (i++ == index) { *output = p;return 0 ; }@@ -790,11 +790,9 @@ int of_property_count_strings(struct device_node *np, const char *propname) p = prop->value; -for (i =0 ; total < prop->length; total += l, p += l) { +for (i =0 ; total < prop->length; total += l, p += l, i++) l =strlen (p) +1 ; -if (*p !=0 ) - i++; - } +return i; }EXPORT_SYMBOL_GPL (of_property_count_strings);Signature · 1 line
1.7.0.4
Rob Herring
AppliedPATCH 1/3 of/base: Take NULL string into account for property with multiple strings
In reply to Benoit CoussonQuoted 7 lines · Benoit Cousson
The current implementation just ignore any NULL string inserted in a multiple strings property.
In some cases we can have a property with a fix number of strings but not necessarily used, like for example in a list of valid pinmux modes.prop = "
uart_rx", "uart_tx", "", "", "safe_mode";
Quoted 7 lines
Do no skip NULL string and take them into account in
of_property_read_string_indexandof_property_count_strings.Reported-by Tony Lindgren <[email protected]>Signed-off-by Benoit Cousson <[email protected]>Cc Grant Likely <[email protected]>Cc Rob Herring <[email protected]>
Applied. The others need Grant's agreement.
Rob
Quoted 31 lines
--- drivers/of/base.c | 8 +++----- 1 files changed, 3 insertions(+), 5 deletions(-)drivers/of/base.c +3
-5@@ -752,7 +752,7 @@ int of_property_read_string_index(struct device_node *np, const char *propname,for (i =0 ; total < prop->length; total += l, p += l) { l =strlen (p) +1 ; -if ((*p !=0 ) && (i++ == index)) { +if (i++ == index) { *output = p;return 0 ; }@@ -790,11 +790,9 @@ int of_property_count_strings(struct device_node *np, const char *propname) p = prop->value; -for (i =0 ; total < prop->length; total += l, p += l) { +for (i =0 ; total < prop->length; total += l, p += l, i++) l =strlen (p) +1 ; -if (*p !=0 ) - i++; - } +return i; }EXPORT_SYMBOL_GPL (of_property_count_strings);
PATCH 1/3 of/base: Take NULL string into account for property with multiple strings
Hi Grant,
Quoted 11 lines · Rob Herring
Quoted 10 lines · Benoit Cousson
The current implementation just ignore any NULL string inserted in a multiple strings property.
In some cases we can have a property with a fix number of strings but not necessarily used, like for example in a list of valid pinmux modes.prop = "uart_rx", "uart_tx", "", "", "safe_mode";Do no skip NULL string and take them into account in
of_property_read_string_indexandof_property_count_strings.
Quoted 6 lines
Quoted 4 lines
Reported-by Tony Lindgren<[email protected]>Signed-off-by Benoit Cousson<[email protected]>Cc Grant Likely<[email protected]>Cc Rob Herring<[email protected]>Applied. The others need Grant's agreement.
New year gentle ping.
Thanks,
Benoit
PATCH 1/3 of/base: Take NULL string into account for property with multiple strings
Quoted 14 lines · Benoit
Hi Grant,
Quoted 11 lines · Rob Herring
Quoted 10 lines · Benoit Cousson
The current implementation just ignore any NULL string inserted in a multiple strings property.
In some cases we can have a property with a fix number of strings but not necessarily used, like for example in a list of valid pinmux modes.prop = "
uart_rx", "uart_tx", "", "", "safe_mode";Do no skip NULL string and take them into account in
of_property_read_string_indexandof_property_count_strings.
Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Reported-by Tony Lindgren<[email protected]>Signed-off-by Benoit Cousson<[email protected]>Cc Grant Likely<[email protected]>Cc Rob Herring<[email protected]>Applied. The others need Grant's agreement.
New year gentle ping.
merged both; should appear in linux-next tomorrow.
g.
PATCH 2/3 of/address: Add reg-names property to name an iomem resource
In reply to Benoit CoussonIn a HW system, resources in general have name to identify them. The is the case as well for IOMEM resources filled by DT "reg" entries. The current DT mechanism is relying on the "reg" order to identify the proper resource. This is error prone and not the natural way to retrieve an information in general.
Moreover, the Linux resource system does support a name and an API to allow a driver to retrieve the resource using the name instead of an index.
Add a reg-names property to allow the possiblity to provide a name to any reg entries.
If the name is available, use it to name the resource, otherwise keep the legacy device name.
--- Documentation/devicetree/bindings/reg-names.txt | 48 +++++++++++++++++++++++ drivers/of/address.c | 16 +++++-- 2 files changed, 59 insertions(+), 5 deletions(-) create mode 100644 Documentation/devicetree/bindings/reg-names.txt
Documentation/devicetree/bindings/reg-names.txt new file +48 -0
@@ -0,0 +1,48 @@ +reg-names property + +In a HW system, resources in general have name to identify them. +The is the case as well for register entries. +The current DT mechanism is relying on the "reg" order to identify +the proper resource. The reg-names is adding the possiblity to +provide a name to reg entries. + +Usage: + +This attribute must be used along with a regular reg entry. If not +it will be simply ignored. +The number of entry must match otherwise the default device name will +be used to as the resource name. + + +Example: + + +l4-abe { + compatible = "simple-bus"; + #address-cells = <2>; + #size-cells = <1>; + ranges = <0 0 0x48000000 0x00001000>, /* MPU path */ + <1 0 0x49000000 0x00001000>; /* L3 path */ + mcasp { + compatible = "ti,mcasp"; + reg = <0 0x10 0x10>, <0 0x20 0x10>, + <1 0x10 0x10>, <1 0x20 0x10>; + reg-names = "mpu", "dat", + "dma", "dma_dat"; + }; + + timer { + compatible = "ti,timer"; + reg = <0 0x40 0x10>, <1 0x40 0x10>; + reg-names = "mpu", "dma"; + }; +}; + + +usb { + compatible = "ti,usb-host"; + reg = <0x4a064000 0x800>, <0x4a064800 0x200>, + <0x4a064c00 0x200>; + reg-names = "config", "ohci", "ehci"; +}; +
drivers/of/address.c +11 -5
@@ -14,7 +14,7 @@static struct of_bus *of_match_bus (struct device_node *np);static int __of_address_to_resource (struct device_node *dev,const __be32 *addrp,u64 size,unsigned int flags, -struct resource *r); +const char *name,struct resource *r);/* Debug utility */ #ifdef DEBUG
@@ -215,7 +215,7 @@ int of_pci_address_to_resource(struct device_node *dev, int bar, addrp =of_get_pci_address (dev, bar, &size, &flags);if (addrp ==NULL )return -EINVAL ; - return __of_address_to_resource(dev, addrp, size, flags, r); + return __of_address_to_resource(dev, addrp, size, flags, NULL, r); }EXPORT_SYMBOL_GPL (of_pci_address_to_resource);#endif /* CONFIG_PCI */
@@ -529,7 +529,7 @@ EXPORT_SYMBOL(of_get_address);static int __of_address_to_resource (struct device_node *dev,const __be32 *addrp,u64 size,unsigned int flags, -struct resource *r) +const char *name,struct resource *r) {u64 taddr;
@@ -551,7 +551,8 @@ static int __of_address_to_resource(struct device_node *dev, r->end = taddr + size -1 ; } r->flags = flags; - r->name = dev->full_name; + r->name = name ? name : dev->full_name; +return 0 ; }
@@ -569,11 +570,16 @@ int of_address_to_resource(struct device_node *dev, int index,const __be32 *addrp;u64 size;unsigned int flags; +const char *name =NULL ; addrp =of_get_address (dev, index, &size, &flags);if (addrp ==NULL )return -EINVAL ; -return __of_address_to_resource (dev, addrp, size, flags, r); + +/* Get optional "reg-names" property to add a name to a resource */ +of_property_read_string_index (dev,"reg-names" , index, &name); + +return __of_address_to_resource (dev, addrp, size, flags, name, r); }EXPORT_SYMBOL_GPL (of_address_to_resource);
Signature · 1 line
1.7.0.4
PATCH 3/3 of/irq: Add interrupts-names property to name an irq resource
In reply to Benoit CoussonIn a HW system, resources in general have name to identify them. The is the case as well for IORESOURCE_IRQ resources filled by DT "interrupts" entries.
The current DT mechanism is relying on the "interrupts" order to identify the proper resource. This is error prone and not the natural way to retrieve an information in general.
Moreover, the resource does support a name and an API is available to allow a driver to retrieve the resource using the name instead of an index.
Add a interrupts-names property to allow the possiblity to provide a name to any interrupts entries.
If the name is available, use it to name the resource, otherwise keep the legacy device full name.
--- .../devicetree/bindings/interrupts-names.txt | 50 ++++++++++++++++++++ drivers/of/irq.c | 11 ++++- 2 files changed, 60 insertions(+), 1 deletions(-) create mode 100644 Documentation/devicetree/bindings/interrupts-names.txt
Documentation/devicetree/bindings/interrupts-names.txt new file +50 -0
@@ -0,0 +1,50 @@ +interrupts-names property + +In a HW system, physical resources in general have name to identify them. +The is the case as well for interrupt lines. +The current DT mechanism is relying on the "interrupts" order to identify +the proper resource. The interrupts-names is adding the possiblity to +provide a name to interrupts entries. + +Usage: + +This attribute must be used along with a regular interrupts entry. If not +it will be simply ignored. + + +Example: + + +l4-abe { + compatible = "simple-bus"; + #address-cells = <2>; + #size-cells = <1>; + ranges = <0 0 0x48000000 0x00001000>, /* MPU path */ + <1 0 0x49000000 0x00001000>; /* L3 path */ + mcasp { + compatible = "ti,mcasp"; + reg = <0 0x10 0x10>, <0 0x20 0x10>, + <1 0x10 0x10>, <1 0x20 0x10>; + reg-names = "mpu", "dat", + "dma", "dma_dat"; + interrupts = <11>, <12>; + interrupts-names = "rx", "tx"; + }; + + timer { + compatible = "ti,timer"; + reg = <0 0x40 0x10>, <1 0x40 0x10>; + reg-names = "mpu", "dma"; + }; +}; + + +usb { + compatible = "ti,usb-host"; + reg = <0x4a064000 0x800>, <0x4a064800 0x200>, + <0x4a064c00 0x200>; + reg-names = "config", "ohci", "ehci"; + interrupts = <14>, <15>; + interrupts-names = "ohci", "ehci"; +}; +
drivers/of/irq.c +10 -1
@@ -346,9 +346,18 @@ int of_irq_to_resource(struct device_node *dev, int index, struct resource *r)/* Only dereference the resource if both the * resource and the irq are valid. */ if (r && irq !=NO_IRQ ) { +const char *name =NULL ; + +/* +* Get optional "interrupts-names" property to add a name +* to the resource. +*/ +of_property_read_string_index (dev,"interrupts-names" , index, + &name); + r->start = r->end = irq; r->flags =IORESOURCE_IRQ ; - r->name = dev->full_name; + r->name = name ? name : dev->full_name; }return irq;
Signature · 1 line
1.7.0.4
Grant Likely
AppliedPATCH 3/3 of/irq: Add interrupts-names property to name an irq resource
Quoted 6 lines · Benoit Cousson
In a HW system, resources in general have name to identify them. The is the case as well for
IORESOURCE_IRQresources filled by DT "interrupts" entries.
The current DT mechanism is relying on the "interrupts" order to identify the proper resource. This is error prone and not the natural way to retrieve an information in general.
I do not agree with this assessment. interrupt property order has worked quite well for a very long time. There are some uses cases that want to access it by-name, but I expect accessing by-index to continue to be the preferred method. I'm going to drop this paragraph from the commit text.
Quoted 26 lines
Moreover, the resource does support a name and an API is available to allow a driver to retrieve the resource using the name instead of an index.
Add a interrupts-names property to allow the possiblity to provide a name to any interrupts entries.
If the name is available, use it to name the resource, otherwise keep the legacy device full name.Signed-off-by Benoit Cousson <[email protected]>Cc Grant Likely <[email protected]>Cc Rob Herring <[email protected]>--- .../devicetree/bindings/interrupts-names.txt | 50 ++++++++++++++++++++ drivers/of/irq.c | 11 ++++- 2 files changed, 60 insertions(+), 1 deletions(-) create mode 100644 Documentation/devicetree/bindings/interrupts-names.txtDocumentation/devicetree/bindings/interrupts-names.txt new file +2
-0@@ -0,0 +1,50 @@ +interrupts-names property +
Documentation/devicetree/bindings/interrupts-names.txt line 12
Quoted 10 lines
Documentation/devicetree/bindings/interrupts-names.txt new file +10
-0+In a HW system, physical resources in general have name to identify them. +The is the case as well for interrupt lines. +The current DT mechanism is relying on the "interrupts" order to identify +the proper resource. The interrupts-names is adding the possiblity to +provide a name to interrupts entries. + +Usage: + +This attribute must be used along with a regular interrupts entry. If not +it will be simply ignored.
This documentation is pretty much identical to the reg-names property description. I'll merge the two into a single file.
Quoted 9 lines
Documentation/devicetree/bindings/interrupts-names.txt new file +9
-0+ + +Example: + + +l4-abe { + compatible = "simple-bus"; + #address-cells = <2>; + #size-cells = <1>;
Documentation/devicetree/bindings/interrupts-names.txt line 31
Quoted 10 lines
Documentation/devicetree/bindings/interrupts-names.txt new file +10
-0+ ranges = <0 0 0x48000000 0x00001000>, /* MPU path */ + <1 0 0x49000000 0x00001000>; /* L3 path */ + mcasp { + compatible = "ti,mcasp"; + reg = <0 0x10 0x10>, <0 0x20 0x10>, + <1 0x10 0x10>, <1 0x20 0x10>; + reg-names = "mpu", "dat", + "dma", "dma_dat"; + interrupts = <11>, <12>; + interrupts-names = "rx", "tx";
Nitpick: I'm going to change the property name to "interrupt-names" (dropping the 's' from interrupts). After playing with the clock binding (clocks vs. clock-names) and looking at what could be done with the gpio binding (gpios vs. gpio-names), I think it 'feels' more consistent to drop the s.
Merged, thanks.
Quoted 51 lines
Documentation/devicetree/bindings/interrupts-names.txt new file +19
-0+ }; + + timer { + compatible = "ti,timer"; + reg = <0 0x40 0x10>, <1 0x40 0x10>; + reg-names = "mpu", "dma"; + }; +}; + + +usb { + compatible = "ti,usb-host"; + reg = <0x4a064000 0x800>, <0x4a064800 0x200>, + <0x4a064c00 0x200>; + reg-names = "config", "ohci", "ehci"; + interrupts = <14>, <15>; + interrupts-names = "ohci", "ehci"; +}; +drivers/of/irq.c +10
-1@@ -346,9 +346,18 @@ int of_irq_to_resource(struct device_node *dev, int index, struct resource *r)/* Only dereference the resource if both the * resource and the irq are valid. */ if (r && irq !=NO_IRQ ) { +const char *name =NULL ; + +/* +* Get optional "interrupts-names" property to add a name +* to the resource. +*/ +of_property_read_string_index (dev,"interrupts-names" , index, + &name); + r->start = r->end = irq; r->flags =IORESOURCE_IRQ ; - r->name = dev->full_name; + r->name = name ? name : dev->full_name; }return irq;Signature · 7 lines
1.7.0.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel at lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH 3/3 of/irq: Add interrupts-names property to name an irq resource
Hi Grant,
Quoted 8 lines · Grant Likely
Quoted 6 lines · Benoit Cousson
In a HW system, resources in general have name to identify them. The is the case as well for
IORESOURCE_IRQresources filled by DT "interrupts" entries.
The current DT mechanism is relying on the "interrupts" order to identify the proper resource. This is error prone and not the natural way to retrieve an information in general.
Quoted 5 lines
I do not agree with this assessment. interrupt property order has worked quite well for a very long time. There are some uses cases that want to access it by-name, but I expect accessing by-index to continue to be the preferred method. I'm going to drop this paragraph from the commit text.
OK, fair enough. My point was when the HW description is providing names to list several IRQ resources, giving a number instead is error prone. If, on the other side, the spec is providing something like IRQ_A, B or C, then yes, the by-index is the natural one.
Considering that most IPs will anyway only have one IRQ line, the by-index method will be the most widely used.
Quoted 31 lines
Quoted 31 lines
Moreover, the resource does support a name and an API is available to allow a driver to retrieve the resource using the name instead of an index.
Add a interrupts-names property to allow the possiblity to provide a name to any interrupts entries.
If the name is available, use it to name the resource, otherwise keep the legacy device full name.Signed-off-by Benoit Cousson<[email protected]>Cc Grant Likely<[email protected]>Cc Rob Herring<[email protected]>--- .../devicetree/bindings/interrupts-names.txt | 50 ++++++++++++++++++++ drivers/of/irq.c | 11 ++++- 2 files changed, 60 insertions(+), 1 deletions(-)create mode 100644
Documentation/devicetree/bindings/interrupts-names.txtDocumentation/devicetree/bindings/interrupts-names.txt new file +7
-0@@ -0,0 +1,50 @@ +interrupts-names property + +In a HW system, physical resources in general have name to identify them. +The is the case as well for interrupt lines. +The current DT mechanism is relying on the "interrupts" order to identify +the proper resource. The interrupts-names is adding the possiblity to +provide a name to interrupts entries.
Quoted 8 lines
Documentation/devicetree/bindings/interrupts-names.txt line 12
Quoted 5 lines
Documentation/devicetree/bindings/interrupts-names.txt new file +5
-0+ +Usage: + +This attribute must be used along with a regular interrupts entry. If not +it will be simply ignored.This documentation is pretty much identical to the reg-names property description. I'll merge the two into a single file.
OK.
Quoted 18 lines
Quoted 18 lines
Documentation/devicetree/bindings/interrupts-names.txt new file +17
-0+ + +Example: + + +l4-abe { + compatible = "simple-bus"; + #address-cells =<2>; + #size-cells =<1>; + ranges =<0 0 0x48000000 0x00001000>, /* MPU path */ + <1 0 0x49000000 0x00001000>; /* L3 path */ + mcasp { + compatible = "ti,mcasp"; + reg =<0 0x10 0x10>,<0 0x20 0x10>, + <1 0x10 0x10>,<1 0x20 0x10>; + reg-names = "mpu", "dat", + "dma", "dma_dat";
Quoted 8 lines
Documentation/devicetree/bindings/interrupts-names.txt line 31
Quoted 2 lines
Documentation/devicetree/bindings/interrupts-names.txt new file +2
-0+ interrupts =<11>,<12>; + interrupts-names = "rx", "tx";Nitpick: I'm going to change the property name to "interrupt-names" (dropping the 's' from interrupts). After playing with the clock binding (clocks vs. clock-names) and looking at what could be done with the gpio binding (gpios vs. gpio-names), I think it 'feels' more consistent to drop the s.
Fully agree, I made a comment on that in the cover-letter because I was not fully happy with that either.
Quoted 1 line
Merged, thanks.
Cool, thanks.
Regards,
Benoit
cover of: Add support for named irq and reg
In reply to Benoit CoussonHi Grant and Rob,
Gentle ping: Do you have some comment on that series?
Thanks,
Benoit
Quoted 46 lines · Benoit Cousson
Hi Grant& Rob,
Following the previous patch submission [1], here is an updated series that adds the support for both reg and irq names.
A small improvement is done as well on the property with multiple strings helper function.Please note that I've just realized that Russell's concern with the
/proc/iomemreadability might not even be valid in the DT case. I might be wrong, but it looks like devices created byof_device_allocdoes not seems to call theinsert_resource. It means that the/proc/iomemis mostly empty when the devices are created from device tree blob. I'm not sure it was done on purpose, but even if this is not the case, the fact is that this/proc/iomementry does not seems to be used extensively.
That does not mean it cannot be improved, but it should change the urgency to fix that with regards to that series.This series is based on 3.2-rc4 and is available here:
git://gitorious.org/omap-pm/linux.gitfor_3.3/resource-namesComments are welcome.
Auto comment: I'm not super happy with these new properties name because it is not really consistent. If you have any better idea, do not hesitate.
Thanks,
Benoit[1] http://www.mail-archive.com/linux-omap at vger.kernel.org/msg57881.html
Benoit Cousson (3):
of/base: Take NULL string into account for property with multiple strings of/address: Add reg-names property to name an iomem resource of/irq: Add interrupts-names property to name an irq resource.../devicetree/bindings/interrupts-names.txt | 50 ++++++++++++++++++++ Documentation/devicetree/bindings/reg-names.txt | 48 +++++++++++++++++++ drivers/of/address.c | 16 ++++-- drivers/of/base.c | 8 +-- drivers/of/irq.c | 11 ++++- 5 files changed, 122 insertions(+), 11 deletions(-)create mode 100644
Documentation/devicetree/bindings/interrupts-names.txtcreate mode 100644Documentation/devicetree/bindings/reg-names.txt