* [PATCH v3 0/3] arm64: dts: add corstone1000 device tree
@ 2022-03-30 13:10 ` Rui Miguel Silva
0 siblings, 0 replies; 22+ messages in thread
From: Rui Miguel Silva @ 2022-03-30 13:10 UTC (permalink / raw)
To: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring,
Krzysztof Kozlowski
Cc: linux-arm-kernel, devicetree, Rui Miguel Silva
Add device tree and correspondent binding for ARM corstone1000
[0] platform for FVP (Fixed Virtual Platform) and FPGA MPS3
prototyping board implementation of this system.
Cheers,
Rui
v2 [2] ->v3:
Rob Herring:
- unevaluatedProperties fix
- running dtbs_check had a fatal error:
dpu-qcm2290.example.dts:23:18: which make it exit before
the smsc,lan91c111 was verified.
Fixed the issue in smsc,lan91c111 example by adding
arm-gic header
Andrew Lunn:
- remove lan91c111 txt file since we are replacing it with a
schema one.
v1 [1] ->v2:
Rob Herring:
- change license to dual
- distinguish cpu entry for fvp and mps3
- mmio nodes in simple-bus
- refactor mhu entries
- add secure-status to secure world only accessible mhu
- add smsc,lan91c111 binding patch to avoid dtbs_check
warnings
Marc Zyngier:
- fixed SPI cpu mask invalid entries
- reduce the mask to the existing cpu count (4->1)
- change one interrupt to symbolic enconding
0: https://documentation-service.arm.com/static/619e02b1f45f0b1fbf3a8f16
1: https://lore.kernel.org/linux-devicetree/20220325133655.4177977-1-rui.silva@linaro.org/
2: https://lore.kernel.org/linux-devicetree/20220329213519.801033-1-rui.silva@linaro.org/
Rui Miguel Silva (3):
dt-bindings: net: smsc,lan91c111 convert to schema
dt-bindings: arm: add corstone1000 platform
arm64: dts: arm: add corstone1000 device tree
.../bindings/arm/arm,corstone1000.yaml | 45 +++++
.../bindings/net/smsc,lan91c111.yaml | 61 +++++++
.../bindings/net/smsc-lan91c111.txt | 17 --
arch/arm64/boot/dts/arm/Makefile | 1 +
arch/arm64/boot/dts/arm/corstone1000-fvp.dts | 27 +++
arch/arm64/boot/dts/arm/corstone1000-mps3.dts | 36 ++++
arch/arm64/boot/dts/arm/corstone1000.dtsi | 161 ++++++++++++++++++
7 files changed, 331 insertions(+), 17 deletions(-)
create mode 100644 Documentation/devicetree/bindings/arm/arm,corstone1000.yaml
create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml
delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt
create mode 100644 arch/arm64/boot/dts/arm/corstone1000-fvp.dts
create mode 100644 arch/arm64/boot/dts/arm/corstone1000-mps3.dts
create mode 100644 arch/arm64/boot/dts/arm/corstone1000.dtsi
--
2.35.1
^ permalink raw reply [flat|nested] 22+ messages in thread* [PATCH v3 0/3] arm64: dts: add corstone1000 device tree @ 2022-03-30 13:10 ` Rui Miguel Silva 0 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-30 13:10 UTC (permalink / raw) To: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski Cc: linux-arm-kernel, devicetree, Rui Miguel Silva Add device tree and correspondent binding for ARM corstone1000 [0] platform for FVP (Fixed Virtual Platform) and FPGA MPS3 prototyping board implementation of this system. Cheers, Rui v2 [2] ->v3: Rob Herring: - unevaluatedProperties fix - running dtbs_check had a fatal error: dpu-qcm2290.example.dts:23:18: which make it exit before the smsc,lan91c111 was verified. Fixed the issue in smsc,lan91c111 example by adding arm-gic header Andrew Lunn: - remove lan91c111 txt file since we are replacing it with a schema one. v1 [1] ->v2: Rob Herring: - change license to dual - distinguish cpu entry for fvp and mps3 - mmio nodes in simple-bus - refactor mhu entries - add secure-status to secure world only accessible mhu - add smsc,lan91c111 binding patch to avoid dtbs_check warnings Marc Zyngier: - fixed SPI cpu mask invalid entries - reduce the mask to the existing cpu count (4->1) - change one interrupt to symbolic enconding 0: https://documentation-service.arm.com/static/619e02b1f45f0b1fbf3a8f16 1: https://lore.kernel.org/linux-devicetree/20220325133655.4177977-1-rui.silva@linaro.org/ 2: https://lore.kernel.org/linux-devicetree/20220329213519.801033-1-rui.silva@linaro.org/ Rui Miguel Silva (3): dt-bindings: net: smsc,lan91c111 convert to schema dt-bindings: arm: add corstone1000 platform arm64: dts: arm: add corstone1000 device tree .../bindings/arm/arm,corstone1000.yaml | 45 +++++ .../bindings/net/smsc,lan91c111.yaml | 61 +++++++ .../bindings/net/smsc-lan91c111.txt | 17 -- arch/arm64/boot/dts/arm/Makefile | 1 + arch/arm64/boot/dts/arm/corstone1000-fvp.dts | 27 +++ arch/arm64/boot/dts/arm/corstone1000-mps3.dts | 36 ++++ arch/arm64/boot/dts/arm/corstone1000.dtsi | 161 ++++++++++++++++++ 7 files changed, 331 insertions(+), 17 deletions(-) create mode 100644 Documentation/devicetree/bindings/arm/arm,corstone1000.yaml create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt create mode 100644 arch/arm64/boot/dts/arm/corstone1000-fvp.dts create mode 100644 arch/arm64/boot/dts/arm/corstone1000-mps3.dts create mode 100644 arch/arm64/boot/dts/arm/corstone1000.dtsi -- 2.35.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* [PATCH v3 1/3] dt-bindings: net: smsc,lan91c111 convert to schema 2022-03-30 13:10 ` Rui Miguel Silva @ 2022-03-30 13:10 ` Rui Miguel Silva -1 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-30 13:10 UTC (permalink / raw) To: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski Cc: linux-arm-kernel, devicetree, Rui Miguel Silva Convert the smsc lan91c9x and lan91c1xx controller device tree bindings documentation to json-schema. Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> --- .../bindings/net/smsc,lan91c111.yaml | 61 +++++++++++++++++++ .../bindings/net/smsc-lan91c111.txt | 17 ------ 2 files changed, 61 insertions(+), 17 deletions(-) create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt diff --git a/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml new file mode 100644 index 000000000000..1730284430bc --- /dev/null +++ b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml @@ -0,0 +1,61 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/net/smsc,lan91c111.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller + +maintainers: + - Nicolas Pitre <nico@fluxnic.net> + +allOf: + - $ref: ethernet-controller.yaml# + +properties: + compatible: + const: smsc,lan91c111 + + reg: + maxItems: 1 + + interrupts: + maxItems: 1 + + reg-shift: true + + reg-io-width: + enum: [ 1, 2, 4 ] + default: 4 + + reset-gpios: + description: GPIO connected to control RESET pin + maxItems: 1 + + power-gpios: + description: GPIO connect to control PWRDEWN pin + maxItems: 1 + + pxa-u16-align4: + description: put in place the workaround the force all u16 writes to be + 32 bits aligned + type: boolean + +required: + - compatible + - reg + - interrupts + +unevaluatedProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/arm-gic.h> + + ethernet@4010000 { + compatible = "smsc,lan91c111"; + reg = <0x40100000 0x10000>; + phy-mode = "mii"; + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; + reg-io-width = <2>; + }; diff --git a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt b/Documentation/devicetree/bindings/net/smsc-lan91c111.txt deleted file mode 100644 index 309e37eb7c7c..000000000000 --- a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt +++ /dev/null @@ -1,17 +0,0 @@ -SMSC LAN91c111 Ethernet mac - -Required properties: -- compatible = "smsc,lan91c111"; -- reg : physical address and size of registers -- interrupts : interrupt connection - -Optional properties: -- phy-device : see ethernet.txt file in the same directory -- reg-io-width : Mask of sizes (in bytes) of the IO accesses that - are supported on the device. Valid value for SMSC LAN91c111 are - 1, 2 or 4. If it's omitted or invalid, the size would be 2 meaning - 16-bit access only. -- power-gpios: GPIO to control the PWRDWN pin -- reset-gpios: GPIO to control the RESET pin -- pxa-u16-align4 : Boolean, put in place the workaround the force all - u16 writes to be 32 bits aligned -- 2.35.1 ^ permalink raw reply related [flat|nested] 22+ messages in thread
* [PATCH v3 1/3] dt-bindings: net: smsc,lan91c111 convert to schema @ 2022-03-30 13:10 ` Rui Miguel Silva 0 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-30 13:10 UTC (permalink / raw) To: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski Cc: linux-arm-kernel, devicetree, Rui Miguel Silva Convert the smsc lan91c9x and lan91c1xx controller device tree bindings documentation to json-schema. Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> --- .../bindings/net/smsc,lan91c111.yaml | 61 +++++++++++++++++++ .../bindings/net/smsc-lan91c111.txt | 17 ------ 2 files changed, 61 insertions(+), 17 deletions(-) create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt diff --git a/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml new file mode 100644 index 000000000000..1730284430bc --- /dev/null +++ b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml @@ -0,0 +1,61 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/net/smsc,lan91c111.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller + +maintainers: + - Nicolas Pitre <nico@fluxnic.net> + +allOf: + - $ref: ethernet-controller.yaml# + +properties: + compatible: + const: smsc,lan91c111 + + reg: + maxItems: 1 + + interrupts: + maxItems: 1 + + reg-shift: true + + reg-io-width: + enum: [ 1, 2, 4 ] + default: 4 + + reset-gpios: + description: GPIO connected to control RESET pin + maxItems: 1 + + power-gpios: + description: GPIO connect to control PWRDEWN pin + maxItems: 1 + + pxa-u16-align4: + description: put in place the workaround the force all u16 writes to be + 32 bits aligned + type: boolean + +required: + - compatible + - reg + - interrupts + +unevaluatedProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/arm-gic.h> + + ethernet@4010000 { + compatible = "smsc,lan91c111"; + reg = <0x40100000 0x10000>; + phy-mode = "mii"; + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; + reg-io-width = <2>; + }; diff --git a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt b/Documentation/devicetree/bindings/net/smsc-lan91c111.txt deleted file mode 100644 index 309e37eb7c7c..000000000000 --- a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt +++ /dev/null @@ -1,17 +0,0 @@ -SMSC LAN91c111 Ethernet mac - -Required properties: -- compatible = "smsc,lan91c111"; -- reg : physical address and size of registers -- interrupts : interrupt connection - -Optional properties: -- phy-device : see ethernet.txt file in the same directory -- reg-io-width : Mask of sizes (in bytes) of the IO accesses that - are supported on the device. Valid value for SMSC LAN91c111 are - 1, 2 or 4. If it's omitted or invalid, the size would be 2 meaning - 16-bit access only. -- power-gpios: GPIO to control the PWRDWN pin -- reset-gpios: GPIO to control the RESET pin -- pxa-u16-align4 : Boolean, put in place the workaround the force all - u16 writes to be 32 bits aligned -- 2.35.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/3] dt-bindings: net: smsc,lan91c111 convert to schema 2022-03-30 13:10 ` Rui Miguel Silva @ 2022-03-31 15:44 ` Andre Przywara -1 siblings, 0 replies; 22+ messages in thread From: Andre Przywara @ 2022-03-31 15:44 UTC (permalink / raw) To: Rui Miguel Silva Cc: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski, linux-arm-kernel, devicetree On Wed, 30 Mar 2022 14:10:51 +0100 Rui Miguel Silva <rui.silva@linaro.org> wrote: Hi, > Convert the smsc lan91c9x and lan91c1xx controller device tree > bindings documentation to json-schema. > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > --- > .../bindings/net/smsc,lan91c111.yaml | 61 +++++++++++++++++++ > .../bindings/net/smsc-lan91c111.txt | 17 ------ > 2 files changed, 61 insertions(+), 17 deletions(-) > create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > diff --git a/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > new file mode 100644 > index 000000000000..1730284430bc > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > @@ -0,0 +1,61 @@ > +# SPDX-License-Identifier: GPL-2.0 > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/net/smsc,lan91c111.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller > + > +maintainers: > + - Nicolas Pitre <nico@fluxnic.net> > + > +allOf: > + - $ref: ethernet-controller.yaml# > + > +properties: > + compatible: > + const: smsc,lan91c111 > + > + reg: > + maxItems: 1 > + > + interrupts: > + maxItems: 1 > + > + reg-shift: true > + > + reg-io-width: > + enum: [ 1, 2, 4 ] The old binding spoke of a possible mask, so you could have "6" here to signify that your hardware can do both 16 and 32-bit accesses, IIUC. And from quickly glancing through the Linux driver it seems to support this idea as well. So shall this be: minimum: 1 maximum: 7 instead? > + default: 4 The old binding said: "If it's omitted or invalid, the size would be 2 meaning 16-bit access only". That's also what the Linux driver implements. So this shall be: "default: 2" then? > + > + reset-gpios: > + description: GPIO connected to control RESET pin > + maxItems: 1 > + > + power-gpios: > + description: GPIO connect to control PWRDEWN pin connected Rest looks fine to me, and passes dt_binding_check. Cheers, Andre > + maxItems: 1 > + > + pxa-u16-align4: > + description: put in place the workaround the force all u16 writes to be > + 32 bits aligned > + type: boolean > + > +required: > + - compatible > + - reg > + - interrupts > + > +unevaluatedProperties: false > + > +examples: > + - | > + #include <dt-bindings/interrupt-controller/arm-gic.h> > + > + ethernet@4010000 { > + compatible = "smsc,lan91c111"; > + reg = <0x40100000 0x10000>; > + phy-mode = "mii"; > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > + reg-io-width = <2>; > + }; > diff --git a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt b/Documentation/devicetree/bindings/net/smsc-lan91c111.txt > deleted file mode 100644 > index 309e37eb7c7c..000000000000 > --- a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt > +++ /dev/null > @@ -1,17 +0,0 @@ > -SMSC LAN91c111 Ethernet mac > - > -Required properties: > -- compatible = "smsc,lan91c111"; > -- reg : physical address and size of registers > -- interrupts : interrupt connection > - > -Optional properties: > -- phy-device : see ethernet.txt file in the same directory > -- reg-io-width : Mask of sizes (in bytes) of the IO accesses that > - are supported on the device. Valid value for SMSC LAN91c111 are > - 1, 2 or 4. If it's omitted or invalid, the size would be 2 meaning > - 16-bit access only. > -- power-gpios: GPIO to control the PWRDWN pin > -- reset-gpios: GPIO to control the RESET pin > -- pxa-u16-align4 : Boolean, put in place the workaround the force all > - u16 writes to be 32 bits aligned _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/3] dt-bindings: net: smsc,lan91c111 convert to schema @ 2022-03-31 15:44 ` Andre Przywara 0 siblings, 0 replies; 22+ messages in thread From: Andre Przywara @ 2022-03-31 15:44 UTC (permalink / raw) To: Rui Miguel Silva Cc: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski, linux-arm-kernel, devicetree On Wed, 30 Mar 2022 14:10:51 +0100 Rui Miguel Silva <rui.silva@linaro.org> wrote: Hi, > Convert the smsc lan91c9x and lan91c1xx controller device tree > bindings documentation to json-schema. > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > --- > .../bindings/net/smsc,lan91c111.yaml | 61 +++++++++++++++++++ > .../bindings/net/smsc-lan91c111.txt | 17 ------ > 2 files changed, 61 insertions(+), 17 deletions(-) > create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > diff --git a/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > new file mode 100644 > index 000000000000..1730284430bc > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > @@ -0,0 +1,61 @@ > +# SPDX-License-Identifier: GPL-2.0 > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/net/smsc,lan91c111.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller > + > +maintainers: > + - Nicolas Pitre <nico@fluxnic.net> > + > +allOf: > + - $ref: ethernet-controller.yaml# > + > +properties: > + compatible: > + const: smsc,lan91c111 > + > + reg: > + maxItems: 1 > + > + interrupts: > + maxItems: 1 > + > + reg-shift: true > + > + reg-io-width: > + enum: [ 1, 2, 4 ] The old binding spoke of a possible mask, so you could have "6" here to signify that your hardware can do both 16 and 32-bit accesses, IIUC. And from quickly glancing through the Linux driver it seems to support this idea as well. So shall this be: minimum: 1 maximum: 7 instead? > + default: 4 The old binding said: "If it's omitted or invalid, the size would be 2 meaning 16-bit access only". That's also what the Linux driver implements. So this shall be: "default: 2" then? > + > + reset-gpios: > + description: GPIO connected to control RESET pin > + maxItems: 1 > + > + power-gpios: > + description: GPIO connect to control PWRDEWN pin connected Rest looks fine to me, and passes dt_binding_check. Cheers, Andre > + maxItems: 1 > + > + pxa-u16-align4: > + description: put in place the workaround the force all u16 writes to be > + 32 bits aligned > + type: boolean > + > +required: > + - compatible > + - reg > + - interrupts > + > +unevaluatedProperties: false > + > +examples: > + - | > + #include <dt-bindings/interrupt-controller/arm-gic.h> > + > + ethernet@4010000 { > + compatible = "smsc,lan91c111"; > + reg = <0x40100000 0x10000>; > + phy-mode = "mii"; > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > + reg-io-width = <2>; > + }; > diff --git a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt b/Documentation/devicetree/bindings/net/smsc-lan91c111.txt > deleted file mode 100644 > index 309e37eb7c7c..000000000000 > --- a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt > +++ /dev/null > @@ -1,17 +0,0 @@ > -SMSC LAN91c111 Ethernet mac > - > -Required properties: > -- compatible = "smsc,lan91c111"; > -- reg : physical address and size of registers > -- interrupts : interrupt connection > - > -Optional properties: > -- phy-device : see ethernet.txt file in the same directory > -- reg-io-width : Mask of sizes (in bytes) of the IO accesses that > - are supported on the device. Valid value for SMSC LAN91c111 are > - 1, 2 or 4. If it's omitted or invalid, the size would be 2 meaning > - 16-bit access only. > -- power-gpios: GPIO to control the PWRDWN pin > -- reset-gpios: GPIO to control the RESET pin > -- pxa-u16-align4 : Boolean, put in place the workaround the force all > - u16 writes to be 32 bits aligned ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/3] dt-bindings: net: smsc,lan91c111 convert to schema 2022-03-31 15:44 ` Andre Przywara @ 2022-03-31 20:11 ` Rui Miguel Silva -1 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-31 20:11 UTC (permalink / raw) To: Andre Przywara Cc: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski, linux-arm-kernel, devicetree Hi Andre, Thanks for your review. On Thu, Mar 31, 2022 at 04:44:52PM +0100, Andre Przywara wrote: > On Wed, 30 Mar 2022 14:10:51 +0100 > Rui Miguel Silva <rui.silva@linaro.org> wrote: > > Hi, > > > Convert the smsc lan91c9x and lan91c1xx controller device tree > > bindings documentation to json-schema. > > > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > > --- > > .../bindings/net/smsc,lan91c111.yaml | 61 +++++++++++++++++++ > > .../bindings/net/smsc-lan91c111.txt | 17 ------ > > 2 files changed, 61 insertions(+), 17 deletions(-) > > create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > > > diff --git a/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > new file mode 100644 > > index 000000000000..1730284430bc > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > @@ -0,0 +1,61 @@ > > +# SPDX-License-Identifier: GPL-2.0 > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/net/smsc,lan91c111.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller > > + > > +maintainers: > > + - Nicolas Pitre <nico@fluxnic.net> > > + > > +allOf: > > + - $ref: ethernet-controller.yaml# > > + > > +properties: > > + compatible: > > + const: smsc,lan91c111 > > + > > + reg: > > + maxItems: 1 > > + > > + interrupts: > > + maxItems: 1 > > + > > + reg-shift: true > > + > > + reg-io-width: > > + enum: [ 1, 2, 4 ] > > The old binding spoke of a possible mask, so you could have "6" here to > signify that your hardware can do both 16 and 32-bit accesses, IIUC. > And from quickly glancing through the Linux driver it seems to support > this idea as well. > So shall this be: > minimum: 1 > maximum: 7 > instead? I see your point, but going down that rabbit hole, in the smc91x.h which define the macros for register access, I see, IIUC: 1. 8 or 16 bit access are mandatory (means value 4 only for reg-io-width is not valid) 2. All 8 and 16 bit are exclusive, so I think value 3 and 7 here don't make sense either. So, possible values enum: [ 1, 2, 5, 6 ] let me know your thoughts on this Cheers, Rui > > > + default: 4 > > The old binding said: "If it's omitted or invalid, the size would be 2 > meaning 16-bit access only". That's also what the Linux driver implements. > So this shall be: "default: 2" then? > > > + > > + reset-gpios: > > + description: GPIO connected to control RESET pin > > + maxItems: 1 > > + > > + power-gpios: > > + description: GPIO connect to control PWRDEWN pin > > connected > > Rest looks fine to me, and passes dt_binding_check. > > Cheers, > Andre > > > + maxItems: 1 > > + > > + pxa-u16-align4: > > + description: put in place the workaround the force all u16 writes to be > > + 32 bits aligned > > + type: boolean > > + > > +required: > > + - compatible > > + - reg > > + - interrupts > > + > > +unevaluatedProperties: false > > + > > +examples: > > + - | > > + #include <dt-bindings/interrupt-controller/arm-gic.h> > > + > > + ethernet@4010000 { > > + compatible = "smsc,lan91c111"; > > + reg = <0x40100000 0x10000>; > > + phy-mode = "mii"; > > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > > + reg-io-width = <2>; > > + }; > > diff --git a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt b/Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > deleted file mode 100644 > > index 309e37eb7c7c..000000000000 > > --- a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > +++ /dev/null > > @@ -1,17 +0,0 @@ > > -SMSC LAN91c111 Ethernet mac > > - > > -Required properties: > > -- compatible = "smsc,lan91c111"; > > -- reg : physical address and size of registers > > -- interrupts : interrupt connection > > - > > -Optional properties: > > -- phy-device : see ethernet.txt file in the same directory > > -- reg-io-width : Mask of sizes (in bytes) of the IO accesses that > > - are supported on the device. Valid value for SMSC LAN91c111 are > > - 1, 2 or 4. If it's omitted or invalid, the size would be 2 meaning > > - 16-bit access only. > > -- power-gpios: GPIO to control the PWRDWN pin > > -- reset-gpios: GPIO to control the RESET pin > > -- pxa-u16-align4 : Boolean, put in place the workaround the force all > > - u16 writes to be 32 bits aligned > ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/3] dt-bindings: net: smsc, lan91c111 convert to schema @ 2022-03-31 20:11 ` Rui Miguel Silva 0 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-31 20:11 UTC (permalink / raw) To: Andre Przywara Cc: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski, linux-arm-kernel, devicetree Hi Andre, Thanks for your review. On Thu, Mar 31, 2022 at 04:44:52PM +0100, Andre Przywara wrote: > On Wed, 30 Mar 2022 14:10:51 +0100 > Rui Miguel Silva <rui.silva@linaro.org> wrote: > > Hi, > > > Convert the smsc lan91c9x and lan91c1xx controller device tree > > bindings documentation to json-schema. > > > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > > --- > > .../bindings/net/smsc,lan91c111.yaml | 61 +++++++++++++++++++ > > .../bindings/net/smsc-lan91c111.txt | 17 ------ > > 2 files changed, 61 insertions(+), 17 deletions(-) > > create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > > > diff --git a/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > new file mode 100644 > > index 000000000000..1730284430bc > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > @@ -0,0 +1,61 @@ > > +# SPDX-License-Identifier: GPL-2.0 > > +%YAML 1.2 > > +--- > > +$id: http://devicetree.org/schemas/net/smsc,lan91c111.yaml# > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > + > > +title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller > > + > > +maintainers: > > + - Nicolas Pitre <nico@fluxnic.net> > > + > > +allOf: > > + - $ref: ethernet-controller.yaml# > > + > > +properties: > > + compatible: > > + const: smsc,lan91c111 > > + > > + reg: > > + maxItems: 1 > > + > > + interrupts: > > + maxItems: 1 > > + > > + reg-shift: true > > + > > + reg-io-width: > > + enum: [ 1, 2, 4 ] > > The old binding spoke of a possible mask, so you could have "6" here to > signify that your hardware can do both 16 and 32-bit accesses, IIUC. > And from quickly glancing through the Linux driver it seems to support > this idea as well. > So shall this be: > minimum: 1 > maximum: 7 > instead? I see your point, but going down that rabbit hole, in the smc91x.h which define the macros for register access, I see, IIUC: 1. 8 or 16 bit access are mandatory (means value 4 only for reg-io-width is not valid) 2. All 8 and 16 bit are exclusive, so I think value 3 and 7 here don't make sense either. So, possible values enum: [ 1, 2, 5, 6 ] let me know your thoughts on this Cheers, Rui > > > + default: 4 > > The old binding said: "If it's omitted or invalid, the size would be 2 > meaning 16-bit access only". That's also what the Linux driver implements. > So this shall be: "default: 2" then? > > > + > > + reset-gpios: > > + description: GPIO connected to control RESET pin > > + maxItems: 1 > > + > > + power-gpios: > > + description: GPIO connect to control PWRDEWN pin > > connected > > Rest looks fine to me, and passes dt_binding_check. > > Cheers, > Andre > > > + maxItems: 1 > > + > > + pxa-u16-align4: > > + description: put in place the workaround the force all u16 writes to be > > + 32 bits aligned > > + type: boolean > > + > > +required: > > + - compatible > > + - reg > > + - interrupts > > + > > +unevaluatedProperties: false > > + > > +examples: > > + - | > > + #include <dt-bindings/interrupt-controller/arm-gic.h> > > + > > + ethernet@4010000 { > > + compatible = "smsc,lan91c111"; > > + reg = <0x40100000 0x10000>; > > + phy-mode = "mii"; > > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > > + reg-io-width = <2>; > > + }; > > diff --git a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt b/Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > deleted file mode 100644 > > index 309e37eb7c7c..000000000000 > > --- a/Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > +++ /dev/null > > @@ -1,17 +0,0 @@ > > -SMSC LAN91c111 Ethernet mac > > - > > -Required properties: > > -- compatible = "smsc,lan91c111"; > > -- reg : physical address and size of registers > > -- interrupts : interrupt connection > > - > > -Optional properties: > > -- phy-device : see ethernet.txt file in the same directory > > -- reg-io-width : Mask of sizes (in bytes) of the IO accesses that > > - are supported on the device. Valid value for SMSC LAN91c111 are > > - 1, 2 or 4. If it's omitted or invalid, the size would be 2 meaning > > - 16-bit access only. > > -- power-gpios: GPIO to control the PWRDWN pin > > -- reset-gpios: GPIO to control the RESET pin > > -- pxa-u16-align4 : Boolean, put in place the workaround the force all > > - u16 writes to be 32 bits aligned > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/3] dt-bindings: net: smsc, lan91c111 convert to schema 2022-03-31 20:11 ` [PATCH v3 1/3] dt-bindings: net: smsc, lan91c111 " Rui Miguel Silva @ 2022-04-06 14:21 ` Rob Herring -1 siblings, 0 replies; 22+ messages in thread From: Rob Herring @ 2022-04-06 14:21 UTC (permalink / raw) To: Rui Miguel Silva Cc: Andre Przywara, Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Krzysztof Kozlowski, linux-arm-kernel, devicetree On Thu, Mar 31, 2022 at 09:11:46PM +0100, Rui Miguel Silva wrote: > Hi Andre, > Thanks for your review. > > On Thu, Mar 31, 2022 at 04:44:52PM +0100, Andre Przywara wrote: > > On Wed, 30 Mar 2022 14:10:51 +0100 > > Rui Miguel Silva <rui.silva@linaro.org> wrote: > > > > Hi, > > > > > Convert the smsc lan91c9x and lan91c1xx controller device tree > > > bindings documentation to json-schema. > > > > > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > > > --- > > > .../bindings/net/smsc,lan91c111.yaml | 61 +++++++++++++++++++ > > > .../bindings/net/smsc-lan91c111.txt | 17 ------ > > > 2 files changed, 61 insertions(+), 17 deletions(-) > > > create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > > delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > > > > > diff --git a/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > > new file mode 100644 > > > index 000000000000..1730284430bc > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > > @@ -0,0 +1,61 @@ > > > +# SPDX-License-Identifier: GPL-2.0 > > > +%YAML 1.2 > > > +--- > > > +$id: http://devicetree.org/schemas/net/smsc,lan91c111.yaml# > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > + > > > +title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller > > > + > > > +maintainers: > > > + - Nicolas Pitre <nico@fluxnic.net> > > > + > > > +allOf: > > > + - $ref: ethernet-controller.yaml# > > > + > > > +properties: > > > + compatible: > > > + const: smsc,lan91c111 > > > + > > > + reg: > > > + maxItems: 1 > > > + > > > + interrupts: > > > + maxItems: 1 > > > + > > > + reg-shift: true > > > + > > > + reg-io-width: > > > + enum: [ 1, 2, 4 ] > > > > The old binding spoke of a possible mask, so you could have "6" here to > > signify that your hardware can do both 16 and 32-bit accesses, IIUC. > > And from quickly glancing through the Linux driver it seems to support > > this idea as well. > > So shall this be: > > minimum: 1 > > maximum: 7 > > instead? > > I see your point, but going down that rabbit hole, in the smc91x.h > which define the macros for register access, I see, IIUC: > 1. 8 or 16 bit access are mandatory (means value 4 only for > reg-io-width is not valid) > 2. All 8 and 16 bit are exclusive, so I think value 3 and 7 here > don't make sense either. > > So, possible values enum: [ 1, 2, 5, 6 ] > > let me know your thoughts on this 'reg-io-width' is a common property and treating it as a mask would be a change. We also have 0 cases of doing that in in-tree dts files. So I would keep this as it was and revisit it if and when needed. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 1/3] dt-bindings: net: smsc,lan91c111 convert to schema @ 2022-04-06 14:21 ` Rob Herring 0 siblings, 0 replies; 22+ messages in thread From: Rob Herring @ 2022-04-06 14:21 UTC (permalink / raw) To: Rui Miguel Silva Cc: Andre Przywara, Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Krzysztof Kozlowski, linux-arm-kernel, devicetree On Thu, Mar 31, 2022 at 09:11:46PM +0100, Rui Miguel Silva wrote: > Hi Andre, > Thanks for your review. > > On Thu, Mar 31, 2022 at 04:44:52PM +0100, Andre Przywara wrote: > > On Wed, 30 Mar 2022 14:10:51 +0100 > > Rui Miguel Silva <rui.silva@linaro.org> wrote: > > > > Hi, > > > > > Convert the smsc lan91c9x and lan91c1xx controller device tree > > > bindings documentation to json-schema. > > > > > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > > > --- > > > .../bindings/net/smsc,lan91c111.yaml | 61 +++++++++++++++++++ > > > .../bindings/net/smsc-lan91c111.txt | 17 ------ > > > 2 files changed, 61 insertions(+), 17 deletions(-) > > > create mode 100644 Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > > delete mode 100644 Documentation/devicetree/bindings/net/smsc-lan91c111.txt > > > > > > diff --git a/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > > new file mode 100644 > > > index 000000000000..1730284430bc > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/net/smsc,lan91c111.yaml > > > @@ -0,0 +1,61 @@ > > > +# SPDX-License-Identifier: GPL-2.0 > > > +%YAML 1.2 > > > +--- > > > +$id: http://devicetree.org/schemas/net/smsc,lan91c111.yaml# > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > + > > > +title: Smart Mixed-Signal Connectivity (SMSC) LAN91C9x/91C1xx Controller > > > + > > > +maintainers: > > > + - Nicolas Pitre <nico@fluxnic.net> > > > + > > > +allOf: > > > + - $ref: ethernet-controller.yaml# > > > + > > > +properties: > > > + compatible: > > > + const: smsc,lan91c111 > > > + > > > + reg: > > > + maxItems: 1 > > > + > > > + interrupts: > > > + maxItems: 1 > > > + > > > + reg-shift: true > > > + > > > + reg-io-width: > > > + enum: [ 1, 2, 4 ] > > > > The old binding spoke of a possible mask, so you could have "6" here to > > signify that your hardware can do both 16 and 32-bit accesses, IIUC. > > And from quickly glancing through the Linux driver it seems to support > > this idea as well. > > So shall this be: > > minimum: 1 > > maximum: 7 > > instead? > > I see your point, but going down that rabbit hole, in the smc91x.h > which define the macros for register access, I see, IIUC: > 1. 8 or 16 bit access are mandatory (means value 4 only for > reg-io-width is not valid) > 2. All 8 and 16 bit are exclusive, so I think value 3 and 7 here > don't make sense either. > > So, possible values enum: [ 1, 2, 5, 6 ] > > let me know your thoughts on this 'reg-io-width' is a common property and treating it as a mask would be a change. We also have 0 cases of doing that in in-tree dts files. So I would keep this as it was and revisit it if and when needed. Rob ^ permalink raw reply [flat|nested] 22+ messages in thread
* [PATCH v3 2/3] dt-bindings: arm: add corstone1000 platform 2022-03-30 13:10 ` Rui Miguel Silva @ 2022-03-30 13:10 ` Rui Miguel Silva -1 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-30 13:10 UTC (permalink / raw) To: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski Cc: linux-arm-kernel, devicetree, Rui Miguel Silva Add bindings to describe the FPGA in a prototyping board (MPS3) implementation and the Fixed Virtual Platform implementation of the ARM Corstone1000 platform. Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> --- .../bindings/arm/arm,corstone1000.yaml | 45 +++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/arm,corstone1000.yaml diff --git a/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml b/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml new file mode 100644 index 000000000000..a77f88223801 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml @@ -0,0 +1,45 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/arm/arm,corstone1000.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: ARM Corstone1000 Device Tree Bindings + +maintainers: + - Vishnu Banavath <vishnu.banavath@arm.com> + - Rui Miguel Silva <rui.silva@linaro.org> + +description: |+ + ARM's Corstone1000 includes pre-verified Corstone SSE-710 subsystem that + provides a flexible compute architecture that combines Cortex‑A and Cortex‑M + processors. + + Support for Cortex‑A32, Cortex‑A35 and Cortex‑A53 processors. Two expansion + systems for M-Class (or other) processors for adding sensors, connectivity, + video, audio and machine learning at the edge System and security IPs to build + a secure SoC for a range of rich IoT applications, for example gateways, smart + cameras and embedded systems. + + Integrated Secure Enclave providing hardware Root of Trust and supporting + seamless integration of the optional CryptoCell™-312 cryptographic + accelerator. + +properties: + $nodename: + const: '/' + compatible: + oneOf: + - description: Corstone1000 MPS3 it has 1 Cortex-A35 CPU core in a FPGA + implementation of the Corstone1000 in the MPS3 prototyping board. See + ARM document DAI0550. + items: + - const: arm,corstone1000-mps3 + - description: Corstone1000 FVP is the Fixed Virtual Platform + implementation of this system. See ARM ecosystems FVP's. + items: + - const: arm,corstone1000-fvp + +additionalProperties: true + +... -- 2.35.1 ^ permalink raw reply related [flat|nested] 22+ messages in thread
* [PATCH v3 2/3] dt-bindings: arm: add corstone1000 platform @ 2022-03-30 13:10 ` Rui Miguel Silva 0 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-30 13:10 UTC (permalink / raw) To: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski Cc: linux-arm-kernel, devicetree, Rui Miguel Silva Add bindings to describe the FPGA in a prototyping board (MPS3) implementation and the Fixed Virtual Platform implementation of the ARM Corstone1000 platform. Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> --- .../bindings/arm/arm,corstone1000.yaml | 45 +++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/arm,corstone1000.yaml diff --git a/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml b/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml new file mode 100644 index 000000000000..a77f88223801 --- /dev/null +++ b/Documentation/devicetree/bindings/arm/arm,corstone1000.yaml @@ -0,0 +1,45 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/arm/arm,corstone1000.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: ARM Corstone1000 Device Tree Bindings + +maintainers: + - Vishnu Banavath <vishnu.banavath@arm.com> + - Rui Miguel Silva <rui.silva@linaro.org> + +description: |+ + ARM's Corstone1000 includes pre-verified Corstone SSE-710 subsystem that + provides a flexible compute architecture that combines Cortex‑A and Cortex‑M + processors. + + Support for Cortex‑A32, Cortex‑A35 and Cortex‑A53 processors. Two expansion + systems for M-Class (or other) processors for adding sensors, connectivity, + video, audio and machine learning at the edge System and security IPs to build + a secure SoC for a range of rich IoT applications, for example gateways, smart + cameras and embedded systems. + + Integrated Secure Enclave providing hardware Root of Trust and supporting + seamless integration of the optional CryptoCell™-312 cryptographic + accelerator. + +properties: + $nodename: + const: '/' + compatible: + oneOf: + - description: Corstone1000 MPS3 it has 1 Cortex-A35 CPU core in a FPGA + implementation of the Corstone1000 in the MPS3 prototyping board. See + ARM document DAI0550. + items: + - const: arm,corstone1000-mps3 + - description: Corstone1000 FVP is the Fixed Virtual Platform + implementation of this system. See ARM ecosystems FVP's. + items: + - const: arm,corstone1000-fvp + +additionalProperties: true + +... -- 2.35.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 22+ messages in thread
* [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree 2022-03-30 13:10 ` Rui Miguel Silva @ 2022-03-30 13:10 ` Rui Miguel Silva -1 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-30 13:10 UTC (permalink / raw) To: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski Cc: linux-arm-kernel, devicetree, Rui Miguel Silva Corstone1000 is a platform from arm, which includes pre verified Corstone SSE710 sub-system that combines Cortex-A and Cortex-M processors [0]. These device trees contains the necessary bits to support the Corstone 1000 FVP (Fixed Virtual Platform) [1] and the FPGA MPS3 board Cortex-A35 implementation at Cortex-A35 host side of this platform. [2] 0: https://documentation-service.arm.com/static/619e02b1f45f0b1fbf3a8f16 1: https://developer.arm.com/tools-and-software/open-source-software/arm-platforms-software/arm-ecosystem-fvps 2: https://documentation-service.arm.com/static/61f3f4d7fa8173727a1b71bf Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> --- arch/arm64/boot/dts/arm/Makefile | 1 + arch/arm64/boot/dts/arm/corstone1000-fvp.dts | 27 +++ arch/arm64/boot/dts/arm/corstone1000-mps3.dts | 36 ++++ arch/arm64/boot/dts/arm/corstone1000.dtsi | 161 ++++++++++++++++++ 4 files changed, 225 insertions(+) create mode 100644 arch/arm64/boot/dts/arm/corstone1000-fvp.dts create mode 100644 arch/arm64/boot/dts/arm/corstone1000-mps3.dts create mode 100644 arch/arm64/boot/dts/arm/corstone1000.dtsi diff --git a/arch/arm64/boot/dts/arm/Makefile b/arch/arm64/boot/dts/arm/Makefile index 4382b73baef5..d908e96d7ddc 100644 --- a/arch/arm64/boot/dts/arm/Makefile +++ b/arch/arm64/boot/dts/arm/Makefile @@ -6,3 +6,4 @@ dtb-$(CONFIG_ARCH_VEXPRESS) += juno.dtb juno-r1.dtb juno-r2.dtb juno-scmi.dtb ju dtb-$(CONFIG_ARCH_VEXPRESS) += rtsm_ve-aemv8a.dtb dtb-$(CONFIG_ARCH_VEXPRESS) += vexpress-v2f-1xv7-ca53x2.dtb dtb-$(CONFIG_ARCH_VEXPRESS) += fvp-base-revc.dtb +dtb-$(CONFIG_ARCH_VEXPRESS) += corstone1000-fvp.dtb corstone1000-mps3.dtb diff --git a/arch/arm64/boot/dts/arm/corstone1000-fvp.dts b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts new file mode 100644 index 000000000000..dea8b5f4d68a --- /dev/null +++ b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts @@ -0,0 +1,27 @@ +// SPDX-License-Identifier: GPL-2.0 or MIT +/* + * Copyright (c) 2022, Arm Limited. All rights reserved. + * Copyright (c) 2022, Linaro Limited. All rights reserved. + * + */ + +/dts-v1/; + +#include "corstone1000.dtsi" + +/ { + model = "ARM Corstone1000 FVP (Fixed Virtual Platform)"; + compatible = "arm,corstone1000-fvp"; + + smsc: ethernet@4010000 { + compatible = "smsc,lan91c111"; + reg = <0x40100000 0x10000>; + phy-mode = "mii"; + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; + reg-io-width = <2>; + }; +}; + +&cpu { + compatible = "arm,armv8"; +}; diff --git a/arch/arm64/boot/dts/arm/corstone1000-mps3.dts b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts new file mode 100644 index 000000000000..9989586db70e --- /dev/null +++ b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts @@ -0,0 +1,36 @@ +// SPDX-License-Identifier: GPL-2.0 or MIT +/* + * Copyright (c) 2022, Arm Limited. All rights reserved. + * Copyright (c) 2022, Linaro Limited. All rights reserved. + * + */ + +/dts-v1/; + +#include "corstone1000.dtsi" + +/ { + model = "ARM Corstone1000 FPGA MPS3 board"; + compatible = "arm,corstone1000-mps3"; + + smsc: ethernet@4010000 { + compatible = "smsc,lan9220", "smsc,lan9115"; + reg = <0x40100000 0x10000>; + phy-mode = "mii"; + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; + reg-io-width = <2>; + smsc,irq-push-pull; + }; + + usb_host: usb@40200000 { + compatible = "nxp,usb-isp1763"; + reg = <0x40200000 0x100000>; + interrupts = <GIC_SPI 114 IRQ_TYPE_LEVEL_HIGH>; + bus-width = <16>; + dr_mode = "host"; + }; +}; + +&cpu { + compatible = "arm,cortex-a35"; +}; diff --git a/arch/arm64/boot/dts/arm/corstone1000.dtsi b/arch/arm64/boot/dts/arm/corstone1000.dtsi new file mode 100644 index 000000000000..194d959de828 --- /dev/null +++ b/arch/arm64/boot/dts/arm/corstone1000.dtsi @@ -0,0 +1,161 @@ +// SPDX-License-Identifier: GPL-2.0 or MIT +/* + * Copyright (c) 2022, Arm Limited. All rights reserved. + * Copyright (c) 2022, Linaro Limited. All rights reserved. + * + */ + +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/ { + interrupt-parent = <&gic>; + #address-cells = <1>; + #size-cells = <1>; + + aliases { + serial0 = &uart0; + serial1 = &uart1; + }; + + chosen { + stdout-path = "serial0:115200n8"; + }; + + cpus { + #address-cells = <1>; + #size-cells = <0>; + + cpu: cpu@0 { + device_type = "cpu"; + reg = <0>; + next-level-cache = <&L2_0>; + }; + }; + + memory@88200000 { + device_type = "memory"; + reg = <0x88200000 0x77e00000>; + }; + + gic: interrupt-controller@1c000000 { + compatible = "arm,gic-400"; + #interrupt-cells = <3>; + #address-cells = <0>; + interrupt-controller; + reg = <0x1c010000 0x1000>, + <0x1c02f000 0x2000>, + <0x1c04f000 0x1000>, + <0x1c06f000 0x2000>; + interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>; + }; + + L2_0: l2-cache0 { + compatible = "cache"; + }; + + refclk100mhz: refclk100mhz { + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <100000000>; + clock-output-names = "apb_pclk"; + }; + + smbclk: refclk24mhzx2 { + /* Reference 24MHz clock x 2 */ + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <48000000>; + clock-output-names = "smclk"; + }; + + timer { + compatible = "arm,armv8-timer"; + interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>, + <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>, + <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>, + <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>; + }; + + uartclk: uartclk { + /* UART clock - 50MHz */ + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <50000000>; + clock-output-names = "uartclk"; + }; + + psci { + compatible = "arm,psci-1.0", "arm,psci-0.2"; + method = "smc"; + }; + + soc { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + interrupt-parent = <&gic>; + ranges; + + timer@1a220000 { + compatible = "arm,armv7-timer-mem"; + reg = <0x1a220000 0x1000>; + #address-cells = <1>; + #size-cells = <1>; + clock-frequency = <50000000>; + ranges; + + frame@1a230000 { + frame-number = <0>; + interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>; + reg = <0x1a230000 0x1000>; + }; + }; + + uart0: serial@1a510000 { + compatible = "arm,pl011", "arm,primecell"; + reg = <0x1a510000 0x1000>; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&uartclk>, <&refclk100mhz>; + clock-names = "uartclk", "apb_pclk"; + }; + + uart1: serial@1a520000 { + compatible = "arm,pl011", "arm,primecell"; + reg = <0x1a520000 0x1000>; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&uartclk>, <&refclk100mhz>; + clock-names = "uartclk", "apb_pclk"; + }; + + mhu_hse1: mailbox@1b820000 { + compatible = "arm,mhuv2-tx", "arm,primecell"; + reg = <0x1b820000 0x1000>; + clocks = <&refclk100mhz>; + clock-names = "apb_pclk"; + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <2>; + arm,mhuv2-protocols = <0 0>; + secure-status = "okay"; /* secure-world-only */ + status = "disabled"; + }; + + mhu_seh1: mailbox@1b830000 { + compatible = "arm,mhuv2-rx", "arm,primecell"; + reg = <0x1b830000 0x1000>; + clocks = <&refclk100mhz>; + clock-names = "apb_pclk"; + interrupts = <GIC_SPI 46 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <2>; + arm,mhuv2-protocols = <0 0>; + secure-status = "okay"; /* secure-world-only */ + status = "disabled"; + }; + }; +}; -- 2.35.1 ^ permalink raw reply related [flat|nested] 22+ messages in thread
* [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree @ 2022-03-30 13:10 ` Rui Miguel Silva 0 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-30 13:10 UTC (permalink / raw) To: Liviu Dudau, Sudeep Holla, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski Cc: linux-arm-kernel, devicetree, Rui Miguel Silva Corstone1000 is a platform from arm, which includes pre verified Corstone SSE710 sub-system that combines Cortex-A and Cortex-M processors [0]. These device trees contains the necessary bits to support the Corstone 1000 FVP (Fixed Virtual Platform) [1] and the FPGA MPS3 board Cortex-A35 implementation at Cortex-A35 host side of this platform. [2] 0: https://documentation-service.arm.com/static/619e02b1f45f0b1fbf3a8f16 1: https://developer.arm.com/tools-and-software/open-source-software/arm-platforms-software/arm-ecosystem-fvps 2: https://documentation-service.arm.com/static/61f3f4d7fa8173727a1b71bf Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> --- arch/arm64/boot/dts/arm/Makefile | 1 + arch/arm64/boot/dts/arm/corstone1000-fvp.dts | 27 +++ arch/arm64/boot/dts/arm/corstone1000-mps3.dts | 36 ++++ arch/arm64/boot/dts/arm/corstone1000.dtsi | 161 ++++++++++++++++++ 4 files changed, 225 insertions(+) create mode 100644 arch/arm64/boot/dts/arm/corstone1000-fvp.dts create mode 100644 arch/arm64/boot/dts/arm/corstone1000-mps3.dts create mode 100644 arch/arm64/boot/dts/arm/corstone1000.dtsi diff --git a/arch/arm64/boot/dts/arm/Makefile b/arch/arm64/boot/dts/arm/Makefile index 4382b73baef5..d908e96d7ddc 100644 --- a/arch/arm64/boot/dts/arm/Makefile +++ b/arch/arm64/boot/dts/arm/Makefile @@ -6,3 +6,4 @@ dtb-$(CONFIG_ARCH_VEXPRESS) += juno.dtb juno-r1.dtb juno-r2.dtb juno-scmi.dtb ju dtb-$(CONFIG_ARCH_VEXPRESS) += rtsm_ve-aemv8a.dtb dtb-$(CONFIG_ARCH_VEXPRESS) += vexpress-v2f-1xv7-ca53x2.dtb dtb-$(CONFIG_ARCH_VEXPRESS) += fvp-base-revc.dtb +dtb-$(CONFIG_ARCH_VEXPRESS) += corstone1000-fvp.dtb corstone1000-mps3.dtb diff --git a/arch/arm64/boot/dts/arm/corstone1000-fvp.dts b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts new file mode 100644 index 000000000000..dea8b5f4d68a --- /dev/null +++ b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts @@ -0,0 +1,27 @@ +// SPDX-License-Identifier: GPL-2.0 or MIT +/* + * Copyright (c) 2022, Arm Limited. All rights reserved. + * Copyright (c) 2022, Linaro Limited. All rights reserved. + * + */ + +/dts-v1/; + +#include "corstone1000.dtsi" + +/ { + model = "ARM Corstone1000 FVP (Fixed Virtual Platform)"; + compatible = "arm,corstone1000-fvp"; + + smsc: ethernet@4010000 { + compatible = "smsc,lan91c111"; + reg = <0x40100000 0x10000>; + phy-mode = "mii"; + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; + reg-io-width = <2>; + }; +}; + +&cpu { + compatible = "arm,armv8"; +}; diff --git a/arch/arm64/boot/dts/arm/corstone1000-mps3.dts b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts new file mode 100644 index 000000000000..9989586db70e --- /dev/null +++ b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts @@ -0,0 +1,36 @@ +// SPDX-License-Identifier: GPL-2.0 or MIT +/* + * Copyright (c) 2022, Arm Limited. All rights reserved. + * Copyright (c) 2022, Linaro Limited. All rights reserved. + * + */ + +/dts-v1/; + +#include "corstone1000.dtsi" + +/ { + model = "ARM Corstone1000 FPGA MPS3 board"; + compatible = "arm,corstone1000-mps3"; + + smsc: ethernet@4010000 { + compatible = "smsc,lan9220", "smsc,lan9115"; + reg = <0x40100000 0x10000>; + phy-mode = "mii"; + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; + reg-io-width = <2>; + smsc,irq-push-pull; + }; + + usb_host: usb@40200000 { + compatible = "nxp,usb-isp1763"; + reg = <0x40200000 0x100000>; + interrupts = <GIC_SPI 114 IRQ_TYPE_LEVEL_HIGH>; + bus-width = <16>; + dr_mode = "host"; + }; +}; + +&cpu { + compatible = "arm,cortex-a35"; +}; diff --git a/arch/arm64/boot/dts/arm/corstone1000.dtsi b/arch/arm64/boot/dts/arm/corstone1000.dtsi new file mode 100644 index 000000000000..194d959de828 --- /dev/null +++ b/arch/arm64/boot/dts/arm/corstone1000.dtsi @@ -0,0 +1,161 @@ +// SPDX-License-Identifier: GPL-2.0 or MIT +/* + * Copyright (c) 2022, Arm Limited. All rights reserved. + * Copyright (c) 2022, Linaro Limited. All rights reserved. + * + */ + +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/ { + interrupt-parent = <&gic>; + #address-cells = <1>; + #size-cells = <1>; + + aliases { + serial0 = &uart0; + serial1 = &uart1; + }; + + chosen { + stdout-path = "serial0:115200n8"; + }; + + cpus { + #address-cells = <1>; + #size-cells = <0>; + + cpu: cpu@0 { + device_type = "cpu"; + reg = <0>; + next-level-cache = <&L2_0>; + }; + }; + + memory@88200000 { + device_type = "memory"; + reg = <0x88200000 0x77e00000>; + }; + + gic: interrupt-controller@1c000000 { + compatible = "arm,gic-400"; + #interrupt-cells = <3>; + #address-cells = <0>; + interrupt-controller; + reg = <0x1c010000 0x1000>, + <0x1c02f000 0x2000>, + <0x1c04f000 0x1000>, + <0x1c06f000 0x2000>; + interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>; + }; + + L2_0: l2-cache0 { + compatible = "cache"; + }; + + refclk100mhz: refclk100mhz { + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <100000000>; + clock-output-names = "apb_pclk"; + }; + + smbclk: refclk24mhzx2 { + /* Reference 24MHz clock x 2 */ + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <48000000>; + clock-output-names = "smclk"; + }; + + timer { + compatible = "arm,armv8-timer"; + interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>, + <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>, + <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>, + <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(1) | + IRQ_TYPE_LEVEL_LOW)>; + }; + + uartclk: uartclk { + /* UART clock - 50MHz */ + compatible = "fixed-clock"; + #clock-cells = <0>; + clock-frequency = <50000000>; + clock-output-names = "uartclk"; + }; + + psci { + compatible = "arm,psci-1.0", "arm,psci-0.2"; + method = "smc"; + }; + + soc { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + interrupt-parent = <&gic>; + ranges; + + timer@1a220000 { + compatible = "arm,armv7-timer-mem"; + reg = <0x1a220000 0x1000>; + #address-cells = <1>; + #size-cells = <1>; + clock-frequency = <50000000>; + ranges; + + frame@1a230000 { + frame-number = <0>; + interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>; + reg = <0x1a230000 0x1000>; + }; + }; + + uart0: serial@1a510000 { + compatible = "arm,pl011", "arm,primecell"; + reg = <0x1a510000 0x1000>; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&uartclk>, <&refclk100mhz>; + clock-names = "uartclk", "apb_pclk"; + }; + + uart1: serial@1a520000 { + compatible = "arm,pl011", "arm,primecell"; + reg = <0x1a520000 0x1000>; + interrupt-parent = <&gic>; + interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>; + clocks = <&uartclk>, <&refclk100mhz>; + clock-names = "uartclk", "apb_pclk"; + }; + + mhu_hse1: mailbox@1b820000 { + compatible = "arm,mhuv2-tx", "arm,primecell"; + reg = <0x1b820000 0x1000>; + clocks = <&refclk100mhz>; + clock-names = "apb_pclk"; + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <2>; + arm,mhuv2-protocols = <0 0>; + secure-status = "okay"; /* secure-world-only */ + status = "disabled"; + }; + + mhu_seh1: mailbox@1b830000 { + compatible = "arm,mhuv2-rx", "arm,primecell"; + reg = <0x1b830000 0x1000>; + clocks = <&refclk100mhz>; + clock-names = "apb_pclk"; + interrupts = <GIC_SPI 46 IRQ_TYPE_LEVEL_HIGH>; + #mbox-cells = <2>; + arm,mhuv2-protocols = <0 0>; + secure-status = "okay"; /* secure-world-only */ + status = "disabled"; + }; + }; +}; -- 2.35.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 22+ messages in thread
* Re: [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree 2022-03-30 13:10 ` Rui Miguel Silva @ 2022-03-31 10:48 ` Sudeep Holla -1 siblings, 0 replies; 22+ messages in thread From: Sudeep Holla @ 2022-03-31 10:48 UTC (permalink / raw) To: Rui Miguel Silva Cc: Liviu Dudau, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski, Sudeep Holla, linux-arm-kernel, devicetree On Wed, Mar 30, 2022 at 02:10:53PM +0100, Rui Miguel Silva wrote: > Corstone1000 is a platform from arm, which includes pre > verified Corstone SSE710 sub-system that combines Cortex-A and > Cortex-M processors [0]. > > These device trees contains the necessary bits to support the > Corstone 1000 FVP (Fixed Virtual Platform) [1] and the > FPGA MPS3 board Cortex-A35 implementation at Cortex-A35 host > side of this platform. [2] > I prefer not to have these static URLs in the commit log or in the files as they tend to get stale soon. > 0: https://documentation-service.arm.com/static/619e02b1f45f0b1fbf3a8f16 https://developer.arm.com/documentation/102360/0000 > 1: https://developer.arm.com/tools-and-software/open-source-software/arm-platforms-software/arm-ecosystem-fvps > 2: https://documentation-service.arm.com/static/61f3f4d7fa8173727a1b71bf https://developer.arm.com/documentation/dai0550/c/ Please use the above alternatives instead. > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > --- > arch/arm64/boot/dts/arm/Makefile | 1 + > arch/arm64/boot/dts/arm/corstone1000-fvp.dts | 27 +++ > arch/arm64/boot/dts/arm/corstone1000-mps3.dts | 36 ++++ > arch/arm64/boot/dts/arm/corstone1000.dtsi | 161 ++++++++++++++++++ > 4 files changed, 225 insertions(+) > create mode 100644 arch/arm64/boot/dts/arm/corstone1000-fvp.dts > create mode 100644 arch/arm64/boot/dts/arm/corstone1000-mps3.dts > create mode 100644 arch/arm64/boot/dts/arm/corstone1000.dtsi > > diff --git a/arch/arm64/boot/dts/arm/Makefile b/arch/arm64/boot/dts/arm/Makefile > index 4382b73baef5..d908e96d7ddc 100644 > --- a/arch/arm64/boot/dts/arm/Makefile > +++ b/arch/arm64/boot/dts/arm/Makefile > @@ -6,3 +6,4 @@ dtb-$(CONFIG_ARCH_VEXPRESS) += juno.dtb juno-r1.dtb juno-r2.dtb juno-scmi.dtb ju > dtb-$(CONFIG_ARCH_VEXPRESS) += rtsm_ve-aemv8a.dtb > dtb-$(CONFIG_ARCH_VEXPRESS) += vexpress-v2f-1xv7-ca53x2.dtb > dtb-$(CONFIG_ARCH_VEXPRESS) += fvp-base-revc.dtb > +dtb-$(CONFIG_ARCH_VEXPRESS) += corstone1000-fvp.dtb corstone1000-mps3.dtb > diff --git a/arch/arm64/boot/dts/arm/corstone1000-fvp.dts b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts > new file mode 100644 > index 000000000000..dea8b5f4d68a > --- /dev/null > +++ b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts > @@ -0,0 +1,27 @@ > +// SPDX-License-Identifier: GPL-2.0 or MIT > +/* > + * Copyright (c) 2022, Arm Limited. All rights reserved. > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > + * > + */ > + > +/dts-v1/; > + > +#include "corstone1000.dtsi" > + > +/ { > + model = "ARM Corstone1000 FVP (Fixed Virtual Platform)"; > + compatible = "arm,corstone1000-fvp"; > + > + smsc: ethernet@4010000 { > + compatible = "smsc,lan91c111"; > + reg = <0x40100000 0x10000>; > + phy-mode = "mii"; > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > + reg-io-width = <2>; > + }; > +}; > + > +&cpu { > + compatible = "arm,armv8"; I see the publicly available model contains Cortex-A35, looks like FVP does model the core and is not same as AEMs. So you can move this to dtsi IMO. > +}; > diff --git a/arch/arm64/boot/dts/arm/corstone1000-mps3.dts b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts > new file mode 100644 > index 000000000000..9989586db70e > --- /dev/null > +++ b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts > @@ -0,0 +1,36 @@ > +// SPDX-License-Identifier: GPL-2.0 or MIT > +/* > + * Copyright (c) 2022, Arm Limited. All rights reserved. > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > + * > + */ > + > +/dts-v1/; > + > +#include "corstone1000.dtsi" > + > +/ { > + model = "ARM Corstone1000 FPGA MPS3 board"; > + compatible = "arm,corstone1000-mps3"; > + > + smsc: ethernet@4010000 { > + compatible = "smsc,lan9220", "smsc,lan9115"; > + reg = <0x40100000 0x10000>; > + phy-mode = "mii"; > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > + reg-io-width = <2>; > + smsc,irq-push-pull; > + }; > + > + usb_host: usb@40200000 { > + compatible = "nxp,usb-isp1763"; > + reg = <0x40200000 0x100000>; > + interrupts = <GIC_SPI 114 IRQ_TYPE_LEVEL_HIGH>; > + bus-width = <16>; > + dr_mode = "host"; > + }; > +}; > + > +&cpu { > + compatible = "arm,cortex-a35"; > +}; > diff --git a/arch/arm64/boot/dts/arm/corstone1000.dtsi b/arch/arm64/boot/dts/arm/corstone1000.dtsi > new file mode 100644 > index 000000000000..194d959de828 > --- /dev/null > +++ b/arch/arm64/boot/dts/arm/corstone1000.dtsi > @@ -0,0 +1,161 @@ > +// SPDX-License-Identifier: GPL-2.0 or MIT > +/* > + * Copyright (c) 2022, Arm Limited. All rights reserved. > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > + * > + */ > + > +#include <dt-bindings/interrupt-controller/arm-gic.h> > + > +/ { > + interrupt-parent = <&gic>; > + #address-cells = <1>; > + #size-cells = <1>; > + > + aliases { > + serial0 = &uart0; > + serial1 = &uart1; > + }; > + > + chosen { > + stdout-path = "serial0:115200n8"; > + }; > + > + cpus { > + #address-cells = <1>; > + #size-cells = <0>; > + > + cpu: cpu@0 { > + device_type = "cpu"; > + reg = <0>; > + next-level-cache = <&L2_0>; > + }; > + }; > + > + memory@88200000 { > + device_type = "memory"; > + reg = <0x88200000 0x77e00000>; > + }; > + > + gic: interrupt-controller@1c000000 { > + compatible = "arm,gic-400"; > + #interrupt-cells = <3>; > + #address-cells = <0>; > + interrupt-controller; > + reg = <0x1c010000 0x1000>, > + <0x1c02f000 0x2000>, > + <0x1c04f000 0x1000>, > + <0x1c06f000 0x2000>; > + interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>; > + }; > + > + L2_0: l2-cache0 { > + compatible = "cache"; Any other properties ? > + }; > + > + refclk100mhz: refclk100mhz { > + compatible = "fixed-clock"; > + #clock-cells = <0>; > + clock-frequency = <100000000>; > + clock-output-names = "apb_pclk"; > + }; > + > + smbclk: refclk24mhzx2 { > + /* Reference 24MHz clock x 2 */ > + compatible = "fixed-clock"; > + #clock-cells = <0>; > + clock-frequency = <48000000>; > + clock-output-names = "smclk"; > + }; > + > + timer { > + compatible = "arm,armv8-timer"; > + interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>, > + <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>, > + <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>, > + <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>; > + }; > + > + uartclk: uartclk { > + /* UART clock - 50MHz */ > + compatible = "fixed-clock"; > + #clock-cells = <0>; > + clock-frequency = <50000000>; > + clock-output-names = "uartclk"; > + }; > + > + psci { > + compatible = "arm,psci-1.0", "arm,psci-0.2"; > + method = "smc"; > + }; > + > + soc { > + compatible = "simple-bus"; > + #address-cells = <1>; > + #size-cells = <1>; > + interrupt-parent = <&gic>; > + ranges; > + > + timer@1a220000 { > + compatible = "arm,armv7-timer-mem"; > + reg = <0x1a220000 0x1000>; > + #address-cells = <1>; > + #size-cells = <1>; > + clock-frequency = <50000000>; > + ranges; > + > + frame@1a230000 { > + frame-number = <0>; > + interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>; > + reg = <0x1a230000 0x1000>; > + }; > + }; > + > + uart0: serial@1a510000 { > + compatible = "arm,pl011", "arm,primecell"; > + reg = <0x1a510000 0x1000>; > + interrupt-parent = <&gic>; Are these really needed even if there is only one interrupt controller in the system ? > + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&uartclk>, <&refclk100mhz>; > + clock-names = "uartclk", "apb_pclk"; > + }; > + > + uart1: serial@1a520000 { > + compatible = "arm,pl011", "arm,primecell"; > + reg = <0x1a520000 0x1000>; > + interrupt-parent = <&gic>; > + interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&uartclk>, <&refclk100mhz>; > + clock-names = "uartclk", "apb_pclk"; > + }; > + > + mhu_hse1: mailbox@1b820000 { > + compatible = "arm,mhuv2-tx", "arm,primecell"; > + reg = <0x1b820000 0x1000>; > + clocks = <&refclk100mhz>; > + clock-names = "apb_pclk"; > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > + #mbox-cells = <2>; > + arm,mhuv2-protocols = <0 0>; > + secure-status = "okay"; /* secure-world-only */ Please drop the above. Though I see it is in the binding, no one uses it in the kernel and I prefer not to have this. -- Regards, Sudeep ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree @ 2022-03-31 10:48 ` Sudeep Holla 0 siblings, 0 replies; 22+ messages in thread From: Sudeep Holla @ 2022-03-31 10:48 UTC (permalink / raw) To: Rui Miguel Silva Cc: Liviu Dudau, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski, Sudeep Holla, linux-arm-kernel, devicetree On Wed, Mar 30, 2022 at 02:10:53PM +0100, Rui Miguel Silva wrote: > Corstone1000 is a platform from arm, which includes pre > verified Corstone SSE710 sub-system that combines Cortex-A and > Cortex-M processors [0]. > > These device trees contains the necessary bits to support the > Corstone 1000 FVP (Fixed Virtual Platform) [1] and the > FPGA MPS3 board Cortex-A35 implementation at Cortex-A35 host > side of this platform. [2] > I prefer not to have these static URLs in the commit log or in the files as they tend to get stale soon. > 0: https://documentation-service.arm.com/static/619e02b1f45f0b1fbf3a8f16 https://developer.arm.com/documentation/102360/0000 > 1: https://developer.arm.com/tools-and-software/open-source-software/arm-platforms-software/arm-ecosystem-fvps > 2: https://documentation-service.arm.com/static/61f3f4d7fa8173727a1b71bf https://developer.arm.com/documentation/dai0550/c/ Please use the above alternatives instead. > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > --- > arch/arm64/boot/dts/arm/Makefile | 1 + > arch/arm64/boot/dts/arm/corstone1000-fvp.dts | 27 +++ > arch/arm64/boot/dts/arm/corstone1000-mps3.dts | 36 ++++ > arch/arm64/boot/dts/arm/corstone1000.dtsi | 161 ++++++++++++++++++ > 4 files changed, 225 insertions(+) > create mode 100644 arch/arm64/boot/dts/arm/corstone1000-fvp.dts > create mode 100644 arch/arm64/boot/dts/arm/corstone1000-mps3.dts > create mode 100644 arch/arm64/boot/dts/arm/corstone1000.dtsi > > diff --git a/arch/arm64/boot/dts/arm/Makefile b/arch/arm64/boot/dts/arm/Makefile > index 4382b73baef5..d908e96d7ddc 100644 > --- a/arch/arm64/boot/dts/arm/Makefile > +++ b/arch/arm64/boot/dts/arm/Makefile > @@ -6,3 +6,4 @@ dtb-$(CONFIG_ARCH_VEXPRESS) += juno.dtb juno-r1.dtb juno-r2.dtb juno-scmi.dtb ju > dtb-$(CONFIG_ARCH_VEXPRESS) += rtsm_ve-aemv8a.dtb > dtb-$(CONFIG_ARCH_VEXPRESS) += vexpress-v2f-1xv7-ca53x2.dtb > dtb-$(CONFIG_ARCH_VEXPRESS) += fvp-base-revc.dtb > +dtb-$(CONFIG_ARCH_VEXPRESS) += corstone1000-fvp.dtb corstone1000-mps3.dtb > diff --git a/arch/arm64/boot/dts/arm/corstone1000-fvp.dts b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts > new file mode 100644 > index 000000000000..dea8b5f4d68a > --- /dev/null > +++ b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts > @@ -0,0 +1,27 @@ > +// SPDX-License-Identifier: GPL-2.0 or MIT > +/* > + * Copyright (c) 2022, Arm Limited. All rights reserved. > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > + * > + */ > + > +/dts-v1/; > + > +#include "corstone1000.dtsi" > + > +/ { > + model = "ARM Corstone1000 FVP (Fixed Virtual Platform)"; > + compatible = "arm,corstone1000-fvp"; > + > + smsc: ethernet@4010000 { > + compatible = "smsc,lan91c111"; > + reg = <0x40100000 0x10000>; > + phy-mode = "mii"; > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > + reg-io-width = <2>; > + }; > +}; > + > +&cpu { > + compatible = "arm,armv8"; I see the publicly available model contains Cortex-A35, looks like FVP does model the core and is not same as AEMs. So you can move this to dtsi IMO. > +}; > diff --git a/arch/arm64/boot/dts/arm/corstone1000-mps3.dts b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts > new file mode 100644 > index 000000000000..9989586db70e > --- /dev/null > +++ b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts > @@ -0,0 +1,36 @@ > +// SPDX-License-Identifier: GPL-2.0 or MIT > +/* > + * Copyright (c) 2022, Arm Limited. All rights reserved. > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > + * > + */ > + > +/dts-v1/; > + > +#include "corstone1000.dtsi" > + > +/ { > + model = "ARM Corstone1000 FPGA MPS3 board"; > + compatible = "arm,corstone1000-mps3"; > + > + smsc: ethernet@4010000 { > + compatible = "smsc,lan9220", "smsc,lan9115"; > + reg = <0x40100000 0x10000>; > + phy-mode = "mii"; > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > + reg-io-width = <2>; > + smsc,irq-push-pull; > + }; > + > + usb_host: usb@40200000 { > + compatible = "nxp,usb-isp1763"; > + reg = <0x40200000 0x100000>; > + interrupts = <GIC_SPI 114 IRQ_TYPE_LEVEL_HIGH>; > + bus-width = <16>; > + dr_mode = "host"; > + }; > +}; > + > +&cpu { > + compatible = "arm,cortex-a35"; > +}; > diff --git a/arch/arm64/boot/dts/arm/corstone1000.dtsi b/arch/arm64/boot/dts/arm/corstone1000.dtsi > new file mode 100644 > index 000000000000..194d959de828 > --- /dev/null > +++ b/arch/arm64/boot/dts/arm/corstone1000.dtsi > @@ -0,0 +1,161 @@ > +// SPDX-License-Identifier: GPL-2.0 or MIT > +/* > + * Copyright (c) 2022, Arm Limited. All rights reserved. > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > + * > + */ > + > +#include <dt-bindings/interrupt-controller/arm-gic.h> > + > +/ { > + interrupt-parent = <&gic>; > + #address-cells = <1>; > + #size-cells = <1>; > + > + aliases { > + serial0 = &uart0; > + serial1 = &uart1; > + }; > + > + chosen { > + stdout-path = "serial0:115200n8"; > + }; > + > + cpus { > + #address-cells = <1>; > + #size-cells = <0>; > + > + cpu: cpu@0 { > + device_type = "cpu"; > + reg = <0>; > + next-level-cache = <&L2_0>; > + }; > + }; > + > + memory@88200000 { > + device_type = "memory"; > + reg = <0x88200000 0x77e00000>; > + }; > + > + gic: interrupt-controller@1c000000 { > + compatible = "arm,gic-400"; > + #interrupt-cells = <3>; > + #address-cells = <0>; > + interrupt-controller; > + reg = <0x1c010000 0x1000>, > + <0x1c02f000 0x2000>, > + <0x1c04f000 0x1000>, > + <0x1c06f000 0x2000>; > + interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>; > + }; > + > + L2_0: l2-cache0 { > + compatible = "cache"; Any other properties ? > + }; > + > + refclk100mhz: refclk100mhz { > + compatible = "fixed-clock"; > + #clock-cells = <0>; > + clock-frequency = <100000000>; > + clock-output-names = "apb_pclk"; > + }; > + > + smbclk: refclk24mhzx2 { > + /* Reference 24MHz clock x 2 */ > + compatible = "fixed-clock"; > + #clock-cells = <0>; > + clock-frequency = <48000000>; > + clock-output-names = "smclk"; > + }; > + > + timer { > + compatible = "arm,armv8-timer"; > + interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>, > + <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>, > + <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>, > + <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(1) | > + IRQ_TYPE_LEVEL_LOW)>; > + }; > + > + uartclk: uartclk { > + /* UART clock - 50MHz */ > + compatible = "fixed-clock"; > + #clock-cells = <0>; > + clock-frequency = <50000000>; > + clock-output-names = "uartclk"; > + }; > + > + psci { > + compatible = "arm,psci-1.0", "arm,psci-0.2"; > + method = "smc"; > + }; > + > + soc { > + compatible = "simple-bus"; > + #address-cells = <1>; > + #size-cells = <1>; > + interrupt-parent = <&gic>; > + ranges; > + > + timer@1a220000 { > + compatible = "arm,armv7-timer-mem"; > + reg = <0x1a220000 0x1000>; > + #address-cells = <1>; > + #size-cells = <1>; > + clock-frequency = <50000000>; > + ranges; > + > + frame@1a230000 { > + frame-number = <0>; > + interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>; > + reg = <0x1a230000 0x1000>; > + }; > + }; > + > + uart0: serial@1a510000 { > + compatible = "arm,pl011", "arm,primecell"; > + reg = <0x1a510000 0x1000>; > + interrupt-parent = <&gic>; Are these really needed even if there is only one interrupt controller in the system ? > + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&uartclk>, <&refclk100mhz>; > + clock-names = "uartclk", "apb_pclk"; > + }; > + > + uart1: serial@1a520000 { > + compatible = "arm,pl011", "arm,primecell"; > + reg = <0x1a520000 0x1000>; > + interrupt-parent = <&gic>; > + interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&uartclk>, <&refclk100mhz>; > + clock-names = "uartclk", "apb_pclk"; > + }; > + > + mhu_hse1: mailbox@1b820000 { > + compatible = "arm,mhuv2-tx", "arm,primecell"; > + reg = <0x1b820000 0x1000>; > + clocks = <&refclk100mhz>; > + clock-names = "apb_pclk"; > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > + #mbox-cells = <2>; > + arm,mhuv2-protocols = <0 0>; > + secure-status = "okay"; /* secure-world-only */ Please drop the above. Though I see it is in the binding, no one uses it in the kernel and I prefer not to have this. -- Regards, Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree 2022-03-31 10:48 ` Sudeep Holla @ 2022-03-31 11:24 ` Rui Miguel Silva -1 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-31 11:24 UTC (permalink / raw) To: Sudeep Holla Cc: Liviu Dudau, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski, linux-arm-kernel, devicetree Hi Sudeep, Thanks for the review. On Thu, Mar 31, 2022 at 11:48:54AM +0100, Sudeep Holla wrote: > On Wed, Mar 30, 2022 at 02:10:53PM +0100, Rui Miguel Silva wrote: > > Corstone1000 is a platform from arm, which includes pre > > verified Corstone SSE710 sub-system that combines Cortex-A and > > Cortex-M processors [0]. > > > > These device trees contains the necessary bits to support the > > Corstone 1000 FVP (Fixed Virtual Platform) [1] and the > > FPGA MPS3 board Cortex-A35 implementation at Cortex-A35 host > > side of this platform. [2] > > > > I prefer not to have these static URLs in the commit log or in the files > as they tend to get stale soon. > > > 0: https://documentation-service.arm.com/static/619e02b1f45f0b1fbf3a8f16 > > https://developer.arm.com/documentation/102360/0000 > > > 1: https://developer.arm.com/tools-and-software/open-source-software/arm-platforms-software/arm-ecosystem-fvps > > 2: https://documentation-service.arm.com/static/61f3f4d7fa8173727a1b71bf > > https://developer.arm.com/documentation/dai0550/c/ > > Please use the above alternatives instead. yeah, makes sense thanks. > > > > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > > --- > > arch/arm64/boot/dts/arm/Makefile | 1 + > > arch/arm64/boot/dts/arm/corstone1000-fvp.dts | 27 +++ > > arch/arm64/boot/dts/arm/corstone1000-mps3.dts | 36 ++++ > > arch/arm64/boot/dts/arm/corstone1000.dtsi | 161 ++++++++++++++++++ > > 4 files changed, 225 insertions(+) > > create mode 100644 arch/arm64/boot/dts/arm/corstone1000-fvp.dts > > create mode 100644 arch/arm64/boot/dts/arm/corstone1000-mps3.dts > > create mode 100644 arch/arm64/boot/dts/arm/corstone1000.dtsi > > > > diff --git a/arch/arm64/boot/dts/arm/Makefile b/arch/arm64/boot/dts/arm/Makefile > > index 4382b73baef5..d908e96d7ddc 100644 > > --- a/arch/arm64/boot/dts/arm/Makefile > > +++ b/arch/arm64/boot/dts/arm/Makefile > > @@ -6,3 +6,4 @@ dtb-$(CONFIG_ARCH_VEXPRESS) += juno.dtb juno-r1.dtb juno-r2.dtb juno-scmi.dtb ju > > dtb-$(CONFIG_ARCH_VEXPRESS) += rtsm_ve-aemv8a.dtb > > dtb-$(CONFIG_ARCH_VEXPRESS) += vexpress-v2f-1xv7-ca53x2.dtb > > dtb-$(CONFIG_ARCH_VEXPRESS) += fvp-base-revc.dtb > > +dtb-$(CONFIG_ARCH_VEXPRESS) += corstone1000-fvp.dtb corstone1000-mps3.dtb > > diff --git a/arch/arm64/boot/dts/arm/corstone1000-fvp.dts b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts > > new file mode 100644 > > index 000000000000..dea8b5f4d68a > > --- /dev/null > > +++ b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts > > @@ -0,0 +1,27 @@ > > +// SPDX-License-Identifier: GPL-2.0 or MIT > > +/* > > + * Copyright (c) 2022, Arm Limited. All rights reserved. > > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > > + * > > + */ > > + > > +/dts-v1/; > > + > > +#include "corstone1000.dtsi" > > + > > +/ { > > + model = "ARM Corstone1000 FVP (Fixed Virtual Platform)"; > > + compatible = "arm,corstone1000-fvp"; > > + > > + smsc: ethernet@4010000 { > > + compatible = "smsc,lan91c111"; > > + reg = <0x40100000 0x10000>; > > + phy-mode = "mii"; > > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > > + reg-io-width = <2>; > > + }; > > +}; > > + > > +&cpu { > > + compatible = "arm,armv8"; > > I see the publicly available model contains Cortex-A35, looks like FVP > does model the core and is not same as AEMs. So you can move this to dtsi IMO. yeah, indeed. > > > +}; > > diff --git a/arch/arm64/boot/dts/arm/corstone1000-mps3.dts b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts > > new file mode 100644 > > index 000000000000..9989586db70e > > --- /dev/null > > +++ b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts > > @@ -0,0 +1,36 @@ > > +// SPDX-License-Identifier: GPL-2.0 or MIT > > +/* > > + * Copyright (c) 2022, Arm Limited. All rights reserved. > > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > > + * > > + */ > > + > > +/dts-v1/; > > + > > +#include "corstone1000.dtsi" > > + > > +/ { > > + model = "ARM Corstone1000 FPGA MPS3 board"; > > + compatible = "arm,corstone1000-mps3"; > > + > > + smsc: ethernet@4010000 { > > + compatible = "smsc,lan9220", "smsc,lan9115"; > > + reg = <0x40100000 0x10000>; > > + phy-mode = "mii"; > > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > > + reg-io-width = <2>; > > + smsc,irq-push-pull; > > + }; > > + > > + usb_host: usb@40200000 { > > + compatible = "nxp,usb-isp1763"; > > + reg = <0x40200000 0x100000>; > > + interrupts = <GIC_SPI 114 IRQ_TYPE_LEVEL_HIGH>; > > + bus-width = <16>; > > + dr_mode = "host"; > > + }; > > +}; > > + > > +&cpu { > > + compatible = "arm,cortex-a35"; > > +}; > > diff --git a/arch/arm64/boot/dts/arm/corstone1000.dtsi b/arch/arm64/boot/dts/arm/corstone1000.dtsi > > new file mode 100644 > > index 000000000000..194d959de828 > > --- /dev/null > > +++ b/arch/arm64/boot/dts/arm/corstone1000.dtsi > > @@ -0,0 +1,161 @@ > > +// SPDX-License-Identifier: GPL-2.0 or MIT > > +/* > > + * Copyright (c) 2022, Arm Limited. All rights reserved. > > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > > + * > > + */ > > + > > +#include <dt-bindings/interrupt-controller/arm-gic.h> > > + > > +/ { > > + interrupt-parent = <&gic>; > > + #address-cells = <1>; > > + #size-cells = <1>; > > + > > + aliases { > > + serial0 = &uart0; > > + serial1 = &uart1; > > + }; > > + > > + chosen { > > + stdout-path = "serial0:115200n8"; > > + }; > > + > > + cpus { > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + cpu: cpu@0 { > > + device_type = "cpu"; > > + reg = <0>; > > + next-level-cache = <&L2_0>; > > + }; > > + }; > > + > > + memory@88200000 { > > + device_type = "memory"; > > + reg = <0x88200000 0x77e00000>; > > + }; > > + > > + gic: interrupt-controller@1c000000 { > > + compatible = "arm,gic-400"; > > + #interrupt-cells = <3>; > > + #address-cells = <0>; > > + interrupt-controller; > > + reg = <0x1c010000 0x1000>, > > + <0x1c02f000 0x2000>, > > + <0x1c04f000 0x1000>, > > + <0x1c06f000 0x2000>; > > + interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>; > > + }; > > + > > + L2_0: l2-cache0 { > > + compatible = "cache"; > > Any other properties ? > > > + }; > > + > > + refclk100mhz: refclk100mhz { > > + compatible = "fixed-clock"; > > + #clock-cells = <0>; > > + clock-frequency = <100000000>; > > + clock-output-names = "apb_pclk"; > > + }; > > + > > + smbclk: refclk24mhzx2 { > > + /* Reference 24MHz clock x 2 */ > > + compatible = "fixed-clock"; > > + #clock-cells = <0>; > > + clock-frequency = <48000000>; > > + clock-output-names = "smclk"; > > + }; > > + > > + timer { > > + compatible = "arm,armv8-timer"; > > + interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>, > > + <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>, > > + <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>, > > + <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>; > > + }; > > + > > + uartclk: uartclk { > > + /* UART clock - 50MHz */ > > + compatible = "fixed-clock"; > > + #clock-cells = <0>; > > + clock-frequency = <50000000>; > > + clock-output-names = "uartclk"; > > + }; > > + > > + psci { > > + compatible = "arm,psci-1.0", "arm,psci-0.2"; > > + method = "smc"; > > + }; > > + > > + soc { > > + compatible = "simple-bus"; > > + #address-cells = <1>; > > + #size-cells = <1>; > > + interrupt-parent = <&gic>; > > + ranges; > > + > > + timer@1a220000 { > > + compatible = "arm,armv7-timer-mem"; > > + reg = <0x1a220000 0x1000>; > > + #address-cells = <1>; > > + #size-cells = <1>; > > + clock-frequency = <50000000>; > > + ranges; > > + > > + frame@1a230000 { > > + frame-number = <0>; > > + interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>; > > + reg = <0x1a230000 0x1000>; > > + }; > > + }; > > + > > + uart0: serial@1a510000 { > > + compatible = "arm,pl011", "arm,primecell"; > > + reg = <0x1a510000 0x1000>; > > + interrupt-parent = <&gic>; > > Are these really needed even if there is only one interrupt controller > in the system ? correct, can be dropped. > > > + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>; > > + clocks = <&uartclk>, <&refclk100mhz>; > > + clock-names = "uartclk", "apb_pclk"; > > + }; > > + > > + uart1: serial@1a520000 { > > + compatible = "arm,pl011", "arm,primecell"; > > + reg = <0x1a520000 0x1000>; > > + interrupt-parent = <&gic>; > > + interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>; > > + clocks = <&uartclk>, <&refclk100mhz>; > > + clock-names = "uartclk", "apb_pclk"; > > + }; > > + > > + mhu_hse1: mailbox@1b820000 { > > + compatible = "arm,mhuv2-tx", "arm,primecell"; > > + reg = <0x1b820000 0x1000>; > > + clocks = <&refclk100mhz>; > > + clock-names = "apb_pclk"; > > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > > + #mbox-cells = <2>; > > + arm,mhuv2-protocols = <0 0>; > > + secure-status = "okay"; /* secure-world-only */ > > Please drop the above. Though I see it is in the binding, no one uses > it in the kernel and I prefer not to have this. the secure partitions in secure world use this mailbox to doorbell the secure enclave so, after talking with Rob he suggested to use this bindings to make this clear. So, I will keep this ones. Cheers, Rui > > -- > Regards, > Sudeep ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree @ 2022-03-31 11:24 ` Rui Miguel Silva 0 siblings, 0 replies; 22+ messages in thread From: Rui Miguel Silva @ 2022-03-31 11:24 UTC (permalink / raw) To: Sudeep Holla Cc: Liviu Dudau, Lorenzo Pieralisi, Rob Herring, Krzysztof Kozlowski, linux-arm-kernel, devicetree Hi Sudeep, Thanks for the review. On Thu, Mar 31, 2022 at 11:48:54AM +0100, Sudeep Holla wrote: > On Wed, Mar 30, 2022 at 02:10:53PM +0100, Rui Miguel Silva wrote: > > Corstone1000 is a platform from arm, which includes pre > > verified Corstone SSE710 sub-system that combines Cortex-A and > > Cortex-M processors [0]. > > > > These device trees contains the necessary bits to support the > > Corstone 1000 FVP (Fixed Virtual Platform) [1] and the > > FPGA MPS3 board Cortex-A35 implementation at Cortex-A35 host > > side of this platform. [2] > > > > I prefer not to have these static URLs in the commit log or in the files > as they tend to get stale soon. > > > 0: https://documentation-service.arm.com/static/619e02b1f45f0b1fbf3a8f16 > > https://developer.arm.com/documentation/102360/0000 > > > 1: https://developer.arm.com/tools-and-software/open-source-software/arm-platforms-software/arm-ecosystem-fvps > > 2: https://documentation-service.arm.com/static/61f3f4d7fa8173727a1b71bf > > https://developer.arm.com/documentation/dai0550/c/ > > Please use the above alternatives instead. yeah, makes sense thanks. > > > > > Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org> > > --- > > arch/arm64/boot/dts/arm/Makefile | 1 + > > arch/arm64/boot/dts/arm/corstone1000-fvp.dts | 27 +++ > > arch/arm64/boot/dts/arm/corstone1000-mps3.dts | 36 ++++ > > arch/arm64/boot/dts/arm/corstone1000.dtsi | 161 ++++++++++++++++++ > > 4 files changed, 225 insertions(+) > > create mode 100644 arch/arm64/boot/dts/arm/corstone1000-fvp.dts > > create mode 100644 arch/arm64/boot/dts/arm/corstone1000-mps3.dts > > create mode 100644 arch/arm64/boot/dts/arm/corstone1000.dtsi > > > > diff --git a/arch/arm64/boot/dts/arm/Makefile b/arch/arm64/boot/dts/arm/Makefile > > index 4382b73baef5..d908e96d7ddc 100644 > > --- a/arch/arm64/boot/dts/arm/Makefile > > +++ b/arch/arm64/boot/dts/arm/Makefile > > @@ -6,3 +6,4 @@ dtb-$(CONFIG_ARCH_VEXPRESS) += juno.dtb juno-r1.dtb juno-r2.dtb juno-scmi.dtb ju > > dtb-$(CONFIG_ARCH_VEXPRESS) += rtsm_ve-aemv8a.dtb > > dtb-$(CONFIG_ARCH_VEXPRESS) += vexpress-v2f-1xv7-ca53x2.dtb > > dtb-$(CONFIG_ARCH_VEXPRESS) += fvp-base-revc.dtb > > +dtb-$(CONFIG_ARCH_VEXPRESS) += corstone1000-fvp.dtb corstone1000-mps3.dtb > > diff --git a/arch/arm64/boot/dts/arm/corstone1000-fvp.dts b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts > > new file mode 100644 > > index 000000000000..dea8b5f4d68a > > --- /dev/null > > +++ b/arch/arm64/boot/dts/arm/corstone1000-fvp.dts > > @@ -0,0 +1,27 @@ > > +// SPDX-License-Identifier: GPL-2.0 or MIT > > +/* > > + * Copyright (c) 2022, Arm Limited. All rights reserved. > > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > > + * > > + */ > > + > > +/dts-v1/; > > + > > +#include "corstone1000.dtsi" > > + > > +/ { > > + model = "ARM Corstone1000 FVP (Fixed Virtual Platform)"; > > + compatible = "arm,corstone1000-fvp"; > > + > > + smsc: ethernet@4010000 { > > + compatible = "smsc,lan91c111"; > > + reg = <0x40100000 0x10000>; > > + phy-mode = "mii"; > > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > > + reg-io-width = <2>; > > + }; > > +}; > > + > > +&cpu { > > + compatible = "arm,armv8"; > > I see the publicly available model contains Cortex-A35, looks like FVP > does model the core and is not same as AEMs. So you can move this to dtsi IMO. yeah, indeed. > > > +}; > > diff --git a/arch/arm64/boot/dts/arm/corstone1000-mps3.dts b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts > > new file mode 100644 > > index 000000000000..9989586db70e > > --- /dev/null > > +++ b/arch/arm64/boot/dts/arm/corstone1000-mps3.dts > > @@ -0,0 +1,36 @@ > > +// SPDX-License-Identifier: GPL-2.0 or MIT > > +/* > > + * Copyright (c) 2022, Arm Limited. All rights reserved. > > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > > + * > > + */ > > + > > +/dts-v1/; > > + > > +#include "corstone1000.dtsi" > > + > > +/ { > > + model = "ARM Corstone1000 FPGA MPS3 board"; > > + compatible = "arm,corstone1000-mps3"; > > + > > + smsc: ethernet@4010000 { > > + compatible = "smsc,lan9220", "smsc,lan9115"; > > + reg = <0x40100000 0x10000>; > > + phy-mode = "mii"; > > + interrupts = <GIC_SPI 116 IRQ_TYPE_LEVEL_HIGH>; > > + reg-io-width = <2>; > > + smsc,irq-push-pull; > > + }; > > + > > + usb_host: usb@40200000 { > > + compatible = "nxp,usb-isp1763"; > > + reg = <0x40200000 0x100000>; > > + interrupts = <GIC_SPI 114 IRQ_TYPE_LEVEL_HIGH>; > > + bus-width = <16>; > > + dr_mode = "host"; > > + }; > > +}; > > + > > +&cpu { > > + compatible = "arm,cortex-a35"; > > +}; > > diff --git a/arch/arm64/boot/dts/arm/corstone1000.dtsi b/arch/arm64/boot/dts/arm/corstone1000.dtsi > > new file mode 100644 > > index 000000000000..194d959de828 > > --- /dev/null > > +++ b/arch/arm64/boot/dts/arm/corstone1000.dtsi > > @@ -0,0 +1,161 @@ > > +// SPDX-License-Identifier: GPL-2.0 or MIT > > +/* > > + * Copyright (c) 2022, Arm Limited. All rights reserved. > > + * Copyright (c) 2022, Linaro Limited. All rights reserved. > > + * > > + */ > > + > > +#include <dt-bindings/interrupt-controller/arm-gic.h> > > + > > +/ { > > + interrupt-parent = <&gic>; > > + #address-cells = <1>; > > + #size-cells = <1>; > > + > > + aliases { > > + serial0 = &uart0; > > + serial1 = &uart1; > > + }; > > + > > + chosen { > > + stdout-path = "serial0:115200n8"; > > + }; > > + > > + cpus { > > + #address-cells = <1>; > > + #size-cells = <0>; > > + > > + cpu: cpu@0 { > > + device_type = "cpu"; > > + reg = <0>; > > + next-level-cache = <&L2_0>; > > + }; > > + }; > > + > > + memory@88200000 { > > + device_type = "memory"; > > + reg = <0x88200000 0x77e00000>; > > + }; > > + > > + gic: interrupt-controller@1c000000 { > > + compatible = "arm,gic-400"; > > + #interrupt-cells = <3>; > > + #address-cells = <0>; > > + interrupt-controller; > > + reg = <0x1c010000 0x1000>, > > + <0x1c02f000 0x2000>, > > + <0x1c04f000 0x1000>, > > + <0x1c06f000 0x2000>; > > + interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>; > > + }; > > + > > + L2_0: l2-cache0 { > > + compatible = "cache"; > > Any other properties ? > > > + }; > > + > > + refclk100mhz: refclk100mhz { > > + compatible = "fixed-clock"; > > + #clock-cells = <0>; > > + clock-frequency = <100000000>; > > + clock-output-names = "apb_pclk"; > > + }; > > + > > + smbclk: refclk24mhzx2 { > > + /* Reference 24MHz clock x 2 */ > > + compatible = "fixed-clock"; > > + #clock-cells = <0>; > > + clock-frequency = <48000000>; > > + clock-output-names = "smclk"; > > + }; > > + > > + timer { > > + compatible = "arm,armv8-timer"; > > + interrupts = <GIC_PPI 13 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>, > > + <GIC_PPI 14 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>, > > + <GIC_PPI 11 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>, > > + <GIC_PPI 10 (GIC_CPU_MASK_SIMPLE(1) | > > + IRQ_TYPE_LEVEL_LOW)>; > > + }; > > + > > + uartclk: uartclk { > > + /* UART clock - 50MHz */ > > + compatible = "fixed-clock"; > > + #clock-cells = <0>; > > + clock-frequency = <50000000>; > > + clock-output-names = "uartclk"; > > + }; > > + > > + psci { > > + compatible = "arm,psci-1.0", "arm,psci-0.2"; > > + method = "smc"; > > + }; > > + > > + soc { > > + compatible = "simple-bus"; > > + #address-cells = <1>; > > + #size-cells = <1>; > > + interrupt-parent = <&gic>; > > + ranges; > > + > > + timer@1a220000 { > > + compatible = "arm,armv7-timer-mem"; > > + reg = <0x1a220000 0x1000>; > > + #address-cells = <1>; > > + #size-cells = <1>; > > + clock-frequency = <50000000>; > > + ranges; > > + > > + frame@1a230000 { > > + frame-number = <0>; > > + interrupts = <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>; > > + reg = <0x1a230000 0x1000>; > > + }; > > + }; > > + > > + uart0: serial@1a510000 { > > + compatible = "arm,pl011", "arm,primecell"; > > + reg = <0x1a510000 0x1000>; > > + interrupt-parent = <&gic>; > > Are these really needed even if there is only one interrupt controller > in the system ? correct, can be dropped. > > > + interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>; > > + clocks = <&uartclk>, <&refclk100mhz>; > > + clock-names = "uartclk", "apb_pclk"; > > + }; > > + > > + uart1: serial@1a520000 { > > + compatible = "arm,pl011", "arm,primecell"; > > + reg = <0x1a520000 0x1000>; > > + interrupt-parent = <&gic>; > > + interrupts = <GIC_SPI 20 IRQ_TYPE_LEVEL_HIGH>; > > + clocks = <&uartclk>, <&refclk100mhz>; > > + clock-names = "uartclk", "apb_pclk"; > > + }; > > + > > + mhu_hse1: mailbox@1b820000 { > > + compatible = "arm,mhuv2-tx", "arm,primecell"; > > + reg = <0x1b820000 0x1000>; > > + clocks = <&refclk100mhz>; > > + clock-names = "apb_pclk"; > > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > > + #mbox-cells = <2>; > > + arm,mhuv2-protocols = <0 0>; > > + secure-status = "okay"; /* secure-world-only */ > > Please drop the above. Though I see it is in the binding, no one uses > it in the kernel and I prefer not to have this. the secure partitions in secure world use this mailbox to doorbell the secure enclave so, after talking with Rob he suggested to use this bindings to make this clear. So, I will keep this ones. Cheers, Rui > > -- > Regards, > Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree 2022-03-31 11:24 ` Rui Miguel Silva @ 2022-04-01 10:53 ` Sudeep Holla -1 siblings, 0 replies; 22+ messages in thread From: Sudeep Holla @ 2022-04-01 10:53 UTC (permalink / raw) To: Rui Miguel Silva Cc: Liviu Dudau, Lorenzo Pieralisi, Sudeep Holla, Rob Herring, Krzysztof Kozlowski, linux-arm-kernel, devicetree On Thu, Mar 31, 2022 at 12:24:14PM +0100, Rui Miguel Silva wrote: > On Thu, Mar 31, 2022 at 11:48:54AM +0100, Sudeep Holla wrote: > > On Wed, Mar 30, 2022 at 02:10:53PM +0100, Rui Miguel Silva wrote: > > > + > > > + mhu_hse1: mailbox@1b820000 { > > > + compatible = "arm,mhuv2-tx", "arm,primecell"; > > > + reg = <0x1b820000 0x1000>; > > > + clocks = <&refclk100mhz>; > > > + clock-names = "apb_pclk"; > > > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > > > + #mbox-cells = <2>; > > > + arm,mhuv2-protocols = <0 0>; > > > + secure-status = "okay"; /* secure-world-only */ > > > > Please drop the above. Though I see it is in the binding, no one uses > > it in the kernel and I prefer not to have this. > > the secure partitions in secure world use this mailbox to > doorbell the secure enclave so, after talking with Rob he suggested to > use this bindings to make this clear. So, I will keep this ones. > Hi Rob, Since this is first user of this binding(which is there for a while, but no users in the kernel code base), are you fine with this ? -- Regards, Sudeep ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree @ 2022-04-01 10:53 ` Sudeep Holla 0 siblings, 0 replies; 22+ messages in thread From: Sudeep Holla @ 2022-04-01 10:53 UTC (permalink / raw) To: Rui Miguel Silva Cc: Liviu Dudau, Lorenzo Pieralisi, Sudeep Holla, Rob Herring, Krzysztof Kozlowski, linux-arm-kernel, devicetree On Thu, Mar 31, 2022 at 12:24:14PM +0100, Rui Miguel Silva wrote: > On Thu, Mar 31, 2022 at 11:48:54AM +0100, Sudeep Holla wrote: > > On Wed, Mar 30, 2022 at 02:10:53PM +0100, Rui Miguel Silva wrote: > > > + > > > + mhu_hse1: mailbox@1b820000 { > > > + compatible = "arm,mhuv2-tx", "arm,primecell"; > > > + reg = <0x1b820000 0x1000>; > > > + clocks = <&refclk100mhz>; > > > + clock-names = "apb_pclk"; > > > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > > > + #mbox-cells = <2>; > > > + arm,mhuv2-protocols = <0 0>; > > > + secure-status = "okay"; /* secure-world-only */ > > > > Please drop the above. Though I see it is in the binding, no one uses > > it in the kernel and I prefer not to have this. > > the secure partitions in secure world use this mailbox to > doorbell the secure enclave so, after talking with Rob he suggested to > use this bindings to make this clear. So, I will keep this ones. > Hi Rob, Since this is first user of this binding(which is there for a while, but no users in the kernel code base), are you fine with this ? -- Regards, Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree 2022-04-01 10:53 ` Sudeep Holla @ 2022-04-06 14:22 ` Rob Herring -1 siblings, 0 replies; 22+ messages in thread From: Rob Herring @ 2022-04-06 14:22 UTC (permalink / raw) To: Sudeep Holla Cc: Rui Miguel Silva, Liviu Dudau, Lorenzo Pieralisi, Krzysztof Kozlowski, linux-arm-kernel, devicetree On Fri, Apr 01, 2022 at 11:53:22AM +0100, Sudeep Holla wrote: > On Thu, Mar 31, 2022 at 12:24:14PM +0100, Rui Miguel Silva wrote: > > On Thu, Mar 31, 2022 at 11:48:54AM +0100, Sudeep Holla wrote: > > > On Wed, Mar 30, 2022 at 02:10:53PM +0100, Rui Miguel Silva wrote: > > > > + > > > > + mhu_hse1: mailbox@1b820000 { > > > > + compatible = "arm,mhuv2-tx", "arm,primecell"; > > > > + reg = <0x1b820000 0x1000>; > > > > + clocks = <&refclk100mhz>; > > > > + clock-names = "apb_pclk"; > > > > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > > > > + #mbox-cells = <2>; > > > > + arm,mhuv2-protocols = <0 0>; > > > > + secure-status = "okay"; /* secure-world-only */ > > > > > > Please drop the above. Though I see it is in the binding, no one uses > > > it in the kernel and I prefer not to have this. > > > > the secure partitions in secure world use this mailbox to > > doorbell the secure enclave so, after talking with Rob he suggested to > > use this bindings to make this clear. So, I will keep this ones. > > > Hi Rob, > > Since this is first user of this binding(which is there for a while, but > no users in the kernel code base), are you fine with this ? The general rule is 'don't put status in examples'. I think the same should apply here as that is outside the scope of the binding. Rob _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree @ 2022-04-06 14:22 ` Rob Herring 0 siblings, 0 replies; 22+ messages in thread From: Rob Herring @ 2022-04-06 14:22 UTC (permalink / raw) To: Sudeep Holla Cc: Rui Miguel Silva, Liviu Dudau, Lorenzo Pieralisi, Krzysztof Kozlowski, linux-arm-kernel, devicetree On Fri, Apr 01, 2022 at 11:53:22AM +0100, Sudeep Holla wrote: > On Thu, Mar 31, 2022 at 12:24:14PM +0100, Rui Miguel Silva wrote: > > On Thu, Mar 31, 2022 at 11:48:54AM +0100, Sudeep Holla wrote: > > > On Wed, Mar 30, 2022 at 02:10:53PM +0100, Rui Miguel Silva wrote: > > > > + > > > > + mhu_hse1: mailbox@1b820000 { > > > > + compatible = "arm,mhuv2-tx", "arm,primecell"; > > > > + reg = <0x1b820000 0x1000>; > > > > + clocks = <&refclk100mhz>; > > > > + clock-names = "apb_pclk"; > > > > + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH>; > > > > + #mbox-cells = <2>; > > > > + arm,mhuv2-protocols = <0 0>; > > > > + secure-status = "okay"; /* secure-world-only */ > > > > > > Please drop the above. Though I see it is in the binding, no one uses > > > it in the kernel and I prefer not to have this. > > > > the secure partitions in secure world use this mailbox to > > doorbell the secure enclave so, after talking with Rob he suggested to > > use this bindings to make this clear. So, I will keep this ones. > > > Hi Rob, > > Since this is first user of this binding(which is there for a while, but > no users in the kernel code base), are you fine with this ? The general rule is 'don't put status in examples'. I think the same should apply here as that is outside the scope of the binding. Rob ^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2022-04-06 16:57 UTC | newest] Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-03-30 13:10 [PATCH v3 0/3] arm64: dts: add corstone1000 device tree Rui Miguel Silva 2022-03-30 13:10 ` Rui Miguel Silva 2022-03-30 13:10 ` [PATCH v3 1/3] dt-bindings: net: smsc,lan91c111 convert to schema Rui Miguel Silva 2022-03-30 13:10 ` Rui Miguel Silva 2022-03-31 15:44 ` Andre Przywara 2022-03-31 15:44 ` Andre Przywara 2022-03-31 20:11 ` Rui Miguel Silva 2022-03-31 20:11 ` [PATCH v3 1/3] dt-bindings: net: smsc, lan91c111 " Rui Miguel Silva 2022-04-06 14:21 ` Rob Herring 2022-04-06 14:21 ` [PATCH v3 1/3] dt-bindings: net: smsc,lan91c111 " Rob Herring 2022-03-30 13:10 ` [PATCH v3 2/3] dt-bindings: arm: add corstone1000 platform Rui Miguel Silva 2022-03-30 13:10 ` Rui Miguel Silva 2022-03-30 13:10 ` [PATCH v3 3/3] arm64: dts: arm: add corstone1000 device tree Rui Miguel Silva 2022-03-30 13:10 ` Rui Miguel Silva 2022-03-31 10:48 ` Sudeep Holla 2022-03-31 10:48 ` Sudeep Holla 2022-03-31 11:24 ` Rui Miguel Silva 2022-03-31 11:24 ` Rui Miguel Silva 2022-04-01 10:53 ` Sudeep Holla 2022-04-01 10:53 ` Sudeep Holla 2022-04-06 14:22 ` Rob Herring 2022-04-06 14:22 ` Rob Herring
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.