From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2018-06-18 04:58:58
This series fixes a few things in some Aspeed BMC device trees:
- Fix an error in a memory reserve address on Romulus systems
- Update AST2400 and AST2500 device-trees to add a label to the
SRAM node and add the coprocessor interrupts controller node
along with a binding.
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2018-06-18 04:58:59
The reserved memory for the VGA frame buffer is at the wrong address
for this system.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
---
arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -0,0 +1,35 @@+* Aspeed AST2400 and AST2500 coprocessor interrupt controller++This file describes the bindings for the interrupt controller present+in the AST2400 and AST2500 BMC SoCs which provides interrupt to the+ColdFire coprocessor.++It is not a normal interrupt controller and it would be rather+inconvenient to create an interrupt tree for it as it somewhat shares+some of the same sources as the main ARM interrupt controller but with+different numbers.++The AST2500 supports a SW generated interrupt++Required properties:+- reg: address and length of the register for the device.+- compatible: "aspeed,cvic" and one of:+ "aspeed,ast2400-cvic"+ or+ "aspeed,ast2500-cvic"++- valid-sources: One cell, bitmap of supported sources for the implementation++Optional properties;+- copro-sw-interrupts: List of interrupt numbers that can be used as+ SW interrupts from the ARM to the coprocessor.+ (AST2500 only)++Example:++ cvic: copro-interrupt-controller@1e6c2000 {+ compatible = "aspeed,ast2500-cvic";+ valid-sources = <0xffffffff>;+ copro-sw-interrupts = <1>;+ reg = <0x1e6c2000 0x80>;+ };
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2018-06-18 04:59:01
Add the missing node for the CVIC (the coprocessor interrupt
controller) and add a label to the SRAM node so it can be
referenced from the board device-tree file.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/arm/boot/dts/aspeed-g5.dtsi | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2018-06-18 04:59:02
Add the missing node for the CVIC (the coprocessor interrupt
controller) and add a label to the SRAM node so it can be
referenced from the board device-tree file.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---
arch/arm/boot/dts/aspeed-g4.dtsi | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2018-06-18 05:16:50
On Mon, 2018-06-18 at 14:58 +1000, Benjamin Herrenschmidt wrote:
The reserved memory for the VGA frame buffer is at the wrong address
for this system.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Note: These are pre-reqs for subsequent work, so if they are accepted,
I will put them in the fsi tree that I send to Greg (though it can also
be in an ARM soc tree).
Let me know if you prefer that I create a topic branch to pull on both
sides on k.org
Is there a reason you didn't put this in bindings/interrupt-controller?
Aside from that this looks good.
quoted hunk
@@ -0,0 +1,35 @@+* Aspeed AST2400 and AST2500 coprocessor interrupt controller++This file describes the bindings for the interrupt controller present+in the AST2400 and AST2500 BMC SoCs which provides interrupt to the+ColdFire coprocessor.++It is not a normal interrupt controller and it would be rather+inconvenient to create an interrupt tree for it as it somewhat shares+some of the same sources as the main ARM interrupt controller but with+different numbers.++The AST2500 supports a SW generated interrupt++Required properties:+- reg: address and length of the register for the device.+- compatible: "aspeed,cvic" and one of:+ "aspeed,ast2400-cvic"+ or+ "aspeed,ast2500-cvic"++- valid-sources: One cell, bitmap of supported sources for the implementation++Optional properties;+- copro-sw-interrupts: List of interrupt numbers that can be used as+ SW interrupts from the ARM to the coprocessor.+ (AST2500 only)++Example:++ cvic: copro-interrupt-controller@1e6c2000 {+ compatible = "aspeed,ast2500-cvic";+ valid-sources = <0xffffffff>;+ copro-sw-interrupts = <1>;+ reg = <0x1e6c2000 0x80>;+ };--
Is there a reason you didn't put this in bindings/interrupt-controller?
Well, I don't call it interrupt-controller anymore, it's not an
interrupt controller for the main CPU so I decided to leave it out.
If you (or somebody) has strong feeling about it, I can call it
interrupt-controller again and move it back there :)
Aside from that this looks good.
quoted
@@ -0,0 +1,35 @@+* Aspeed AST2400 and AST2500 coprocessor interrupt controller++This file describes the bindings for the interrupt controller present+in the AST2400 and AST2500 BMC SoCs which provides interrupt to the+ColdFire coprocessor.++It is not a normal interrupt controller and it would be rather+inconvenient to create an interrupt tree for it as it somewhat shares+some of the same sources as the main ARM interrupt controller but with+different numbers.++The AST2500 supports a SW generated interrupt++Required properties:+- reg: address and length of the register for the device.+- compatible: "aspeed,cvic" and one of:+ "aspeed,ast2400-cvic"+ or+ "aspeed,ast2500-cvic"++- valid-sources: One cell, bitmap of supported sources for the implementation++Optional properties;+- copro-sw-interrupts: List of interrupt numbers that can be used as+ SW interrupts from the ARM to the coprocessor.+ (AST2500 only)++Example:++ cvic: copro-interrupt-controller@1e6c2000 {+ compatible = "aspeed,ast2500-cvic";+ valid-sources = <0xffffffff>;+ copro-sw-interrupts = <1>;+ reg = <0x1e6c2000 0x80>;+ };--
@@ -0,0 +1,35 @@+* Aspeed AST2400 and AST2500 coprocessor interrupt controller++This file describes the bindings for the interrupt controller present+in the AST2400 and AST2500 BMC SoCs which provides interrupt to the+ColdFire coprocessor.++It is not a normal interrupt controller and it would be rather+inconvenient to create an interrupt tree for it as it somewhat shares+some of the same sources as the main ARM interrupt controller but with+different numbers.++The AST2500 supports a SW generated interrupt++Required properties:+- reg: address and length of the register for the device.+- compatible: "aspeed,cvic" and one of:+ "aspeed,ast2400-cvic"+ or+ "aspeed,ast2500-cvic"++- valid-sources: One cell, bitmap of supported sources for the implementation
aspeed,valid-sources
This could use a better description. I thought this was which bits to
use for s/w irq, but then I read the next property...
Alternatively, why can't this be implied by the compatible?
+
+Optional properties;
+- copro-sw-interrupts: List of interrupt numbers that can be used as
+ SW interrupts from the ARM to the coprocessor.
+ (AST2500 only)
+
+Example:
+
+ cvic: copro-interrupt-controller@1e6c2000 {
+ compatible = "aspeed,ast2500-cvic";
+ valid-sources = <0xffffffff>;
+ copro-sw-interrupts = <1>;
+ reg = <0x1e6c2000 0x80>;
+ };
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
@@ -0,0 +1,35 @@+* Aspeed AST2400 and AST2500 coprocessor interrupt controller++This file describes the bindings for the interrupt controller present+in the AST2400 and AST2500 BMC SoCs which provides interrupt to the+ColdFire coprocessor.++It is not a normal interrupt controller and it would be rather+inconvenient to create an interrupt tree for it as it somewhat shares+some of the same sources as the main ARM interrupt controller but with+different numbers.++The AST2500 supports a SW generated interrupt++Required properties:+- reg: address and length of the register for the device.+- compatible: "aspeed,cvic" and one of:+ "aspeed,ast2400-cvic"+ or+ "aspeed,ast2500-cvic"++- valid-sources: One cell, bitmap of supported sources for the implementation
aspeed,valid-sources
This could use a better description. I thought this was which bits to
use for s/w irq, but then I read the next property...
Alternatively, why can't this be implied by the compatible?
It could, I'm happy to drop it, I don't actually use it in SW.
Cheers,
Ben.
quoted
+
+Optional properties;
+- copro-sw-interrupts: List of interrupt numbers that can be used as
+ SW interrupts from the ARM to the coprocessor.
+ (AST2500 only)
+
+Example:
+
+ cvic: copro-interrupt-controller@1e6c2000 {
+ compatible = "aspeed,ast2500-cvic";
+ valid-sources = <0xffffffff>;
+ copro-sw-interrupts = <1>;
+ reg = <0x1e6c2000 0x80>;
+ };
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel