arm64: dts: initial NXP S32G2 support
Subsystems (6)
cover arm64: dts: initial NXP S32G2 support
Hello,
Here I'd like to propose a patchset, which is initial upstream support for NXP S32G2. S32G is a processor family developed by NXP for automotive solutions, such as vehicle networking and automotive high-performance processing. This series focuses on S32G2, which is the latest generation we can find at the moment. As the first round to support S32G2, this patchset only enables basic components and interfaces the SoC must have while kernel booting, which aims to have minimum hardware enablement for these two boards, S32G-VNP-EVB and S32G-VNP-RDB2. The concepts of how these boards work are originated from the downstream kernel tree[1] developed by NXP, which provides lots of details about the SoC S32G274A and its integrated boards. This series has been verified with downstream ATF[2] & U-Boot[3] based on the ATF boot flow.
Thanks,
Chester
[1] https://source.codeaurora.org/external/autobsps32/linux/
[2] https://source.codeaurora.org/external/autobsps32/arm-trusted-firmware/
[3] https://source.codeaurora.org/external/autobsps32/u-boot/
Chester Lin (8):
dt-bindings: arm: fsl: add NXP S32G2 boards
dt-bindings: serial: fsl-linflexuart: convert to json-schema format
dt-bindings: serial: fsl-linflexuart: Add compatible for S32G2
arm64: dts: add NXP S32G2 support
arm64: dts: s32g2: add serial/uart support
arm64: dts: s32g2: add VNP-EVB and VNP-RDB2 support
arm64: dts: s32g2: add memory nodes for evb and rdb2
MAINTAINERS: Add an entry for NXP S32G2 boards
.../devicetree/bindings/arm/fsl.yaml | 7 + .../bindings/serial/fsl,s32-linflexuart.txt | 22 --- .../bindings/serial/fsl,s32-linflexuart.yaml | 66 +++++++++ MAINTAINERS | 6 + arch/arm64/boot/dts/freescale/Makefile | 2 + arch/arm64/boot/dts/freescale/s32g2.dtsi | 129 ++++++++++++++++++ .../arm64/boot/dts/freescale/s32g274a-evb.dts | 29 ++++ .../boot/dts/freescale/s32g274a-rdb2.dts | 33 +++++ 8 files changed, 272 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsi create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-evb.dts create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts
Signature · 1 line
2.30.0
PATCH 1/8 dt-bindings: arm: fsl: add NXP S32G2 boards
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)
Documentation/devicetree/bindings/arm/fsl.yaml +7 -0
@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160a + - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2 + - const: fsl,s32g2 + - description: S32V234 based Boards items: - enum:
Signature · 1 line
2.30.0
Re: [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards
Hello Rob and NXP,
Quoted 13 lines · Chester Lin
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
Signed-off-by Chester Lin <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/devicetree/bindings/arm/fsl.yaml +0
-0
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 990
Quoted 8 lines
Documentation/devicetree/bindings/arm/fsl.yaml +5
-0@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160a + - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2
@Rob: Should for new boards the description: syntax be used also for enums? Or just at SoC level, and for board enums still traditional # comments?
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 991
Quoted 1 line
Documentation/devicetree/bindings/arm/fsl.yaml +1
-0+ - const: fsl,s32g2
@NXP: Is it sufficient here to have s32g2, or should we call this s32g274a and adjust the description above to S32G274A?
Related, is the trailing A for Arm, like for the Layerscape chips? I.e., not for Alpha or rev.A or something that will change for non-eval chips?
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 995
Quoted 4 lines
Documentation/devicetree/bindings/arm/fsl.yaml +1
-0+ - description: S32V234 based Boards items: - enum:
Otherwise,
Thanks,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Rob Herring
maintainerRe: [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards
Quoted 19 lines · Andreas Färber
Hello Rob and NXP,
Quoted 16 lines · Chester Lin
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
Signed-off-by Chester Lin <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/devicetree/bindings/arm/fsl.yaml +0
-0@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160a
Quoted 9 lines
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 990
Quoted 5 lines
Documentation/devicetree/bindings/arm/fsl.yaml +5
-0+ - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2@Rob: Should for new boards the description: syntax be used also for enums? Or just at SoC level, and for board enums still traditional # comments?
It's up to how the platform wants to do it.
Rob
Re: [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards
In reply to Chester LinQuoted 13 lines · Chester Lin
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
Signed-off-by Chester Lin <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/devicetree/bindings/arm/fsl.yaml +0
-0
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 991
Quoted 9 lines
Documentation/devicetree/bindings/arm/fsl.yaml +6
-0@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160a + - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2 + - const: fsl,s32g2
Given this is an entirely different family from i.MX and new?, shouldn't it use 'nxp' instead of 'fsl'? Either way,
Rob
Re: [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards
Quoted 17 lines · Rob Herring
Quoted 16 lines · Chester Lin
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
Signed-off-by Chester Lin <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/devicetree/bindings/arm/fsl.yaml +0
-0@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160a
Quoted 9 lines
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 991
Quoted 6 lines
Documentation/devicetree/bindings/arm/fsl.yaml +6
-0+ - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2 + - const: fsl,s32g2Given this is an entirely different family from i.MX and new?, shouldn't it use 'nxp' instead of 'fsl'? Either way,
It sounds good and Radu from NXP has mentioned a similar idea for the compatible string of linflexuart. To keep the naming consistency, should we change all 'fsl' to 'nxp' as well? For example, we could rename the fsl.yaml to nxp.yaml. However, changing all of them would cause some impacts, which will need more verifications on new strings. Otherwise we would have to tolerate the naming differences only used by s32g2.
Thanks,
Chester
Quoted 5 lines
Acked-by Rob Herring <[email protected]>Rob
Re: [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards
Hi Chester,
Quoted 28 lines · Chester Lin
Quoted 17 lines · Rob Herring
Quoted 16 lines · Chester Lin
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
Signed-off-by Chester Lin <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/devicetree/bindings/arm/fsl.yaml +0
-0@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160aQuoted 9 lines
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 991
Quoted 6 lines
Documentation/devicetree/bindings/arm/fsl.yaml +6
-0+ - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2 + - const: fsl,s32g2Given this is an entirely different family from i.MX and new?, shouldn't it use 'nxp' instead of 'fsl'? Either way,
Quoted 3 lines
It sounds good and Radu from NXP has mentioned a similar idea for the compatible string of linflexuart. To keep the naming consistency, should we change all 'fsl' to 'nxp' as well?
I assume that question was just unclearly phrased, so for the record:
ABI stability rules forbid us from changing "all 'fsl'" in compatible strings or property names.
Deployed firmware providing mainline-merged platforms with DTBs using fsl prefix (e.g., the quoted LX2160A) needs to continue working with newer drivers, and deployed mainline Linux should continue working after firmware updates that modify the DTB provided to Linux.
So, if NXP wants to use nxp prefix for new S32G bindings, you can do that for your additions only, but for LINFlexD UART (3/8) you will still need to use fsl for the "historical" S32V binding used as fallback.
Please keep S32G consistent with itself - so if we decide on nxp here, we should apply it to SoC, boards, LINFlexD and any future peripherals.
Quoted 2 lines
For example, we could rename the
fsl.yaml
tonxp.yaml.
Since other people might be contributing i.MX boards etc. to that file, better not make your patch series conflict with other people's patches, so that it can get merged and we can move on to the next patchsets.
The schema filename is not ABI, so it can be renamed later.
The .dtb path may become ABI (e.g., U-Boot $fdtfile), thus my comment about consciously deciding between freescale/ vs. nxp/ subdirectory.
Quoted 3 lines
However, changing all of them would cause some impacts, which will need more verifications on new strings. Otherwise we would have to tolerate the naming differences only used by s32g2.
I fear tolerating the mess one way or another is the only viable way. Otherwise both bindings and drivers would need duplication for backwards compatibility, for no good reason - Freescale was acquired back in 2015.
Cheers,
Andreas
Signature · 9 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg) _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Re: [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards
Quoted 41 lines · Andreas Färber
Hi Chester,
Quoted 28 lines · Chester Lin
Quoted 17 lines · Rob Herring
Quoted 16 lines · Chester Lin
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
Signed-off-by Chester Lin <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/devicetree/bindings/arm/fsl.yaml +0
-0@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160aQuoted 9 lines
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 991
Quoted 6 lines
Documentation/devicetree/bindings/arm/fsl.yaml +6
-0+ - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2 + - const: fsl,s32g2Given this is an entirely different family from i.MX and new?, shouldn't it use 'nxp' instead of 'fsl'? Either way,
Quoted 3 lines
It sounds good and Radu from NXP has mentioned a similar idea for the compatible string of linflexuart. To keep the naming consistency, should we change all 'fsl' to 'nxp' as well?
I assume that question was just unclearly phrased, so for the record:
ABI stability rules forbid us from changing "all 'fsl'" in compatible strings or property names.
Quoted 6 lines
Deployed firmware providing mainline-merged platforms with DTBs using fsl prefix (e.g., the quoted LX2160A) needs to continue working with newer drivers, and deployed mainline Linux should continue working after firmware updates that modify the DTB provided to Linux.
This is a new platform/SoC therefore there is no ABI. There is no requirement in the kernel that a new ABI (which you define in this patchset in the bindings) should be compatible with something somewhere. It's some misunderstanding of stable ABI. Therefore all new compatibles are allowed to be nxp, not fsl.
No one here proposed renaming existing compatibles from fsl tro nxp. We talk about new ones.
Different question of course whether you want to be nice to some existing out-of-tree users... but then have in mind that we don't care about out of tree. :) Anyway being nice to out-of-tree is not part of ABI. It's just being nice and useful.
Best regards,
Krzysztof
Re: [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards
Hi Krzysztof,
Quoted 46 lines · Krzysztof Kozlowski
Quoted 38 lines · Andreas Färber
Quoted 28 lines · Chester Lin
Quoted 17 lines · Rob Herring
Quoted 16 lines · Chester Lin
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
Signed-off-by Chester Lin <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/devicetree/bindings/arm/fsl.yaml +0
-0@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160aQuoted 9 lines
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 991
Quoted 6 lines
Documentation/devicetree/bindings/arm/fsl.yaml +6
-0+ - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2 + - const: fsl,s32g2Given this is an entirely different family from i.MX and new?, shouldn't it use 'nxp' instead of 'fsl'? Either way,
Quoted 3 lines
It sounds good and Radu from NXP has mentioned a similar idea for the compatible string of linflexuart. To keep the naming consistency, should we change all 'fsl' to 'nxp' as well?
I assume that question was just unclearly phrased, so for the record:
ABI stability rules forbid us from changing "all 'fsl'" in compatible strings or property names.
Quoted 6 lines
Deployed firmware providing mainline-merged platforms with DTBs using fsl prefix (e.g., the quoted LX2160A) needs to continue working with newer drivers, and deployed mainline Linux should continue working after firmware updates that modify the DTB provided to Linux.
Quoted 8 lines
This is a new platform/SoC therefore there is no ABI. There is no requirement in the kernel that a new ABI (which you define in this patchset in the bindings) should be compatible with something somewhere. It's some misunderstanding of stable ABI. Therefore all new compatibles are allowed to be nxp, not fsl.
No one here proposed renaming existing compatibles from fsl tro nxp. We talk about new ones.
Chester seemingly did: "all 'fsl' ... as well", not "all new 'fsl'" ones, in the patch context of existing fsl.yaml. Like I said, it may just have been unluckily worded.
Therefore my saying that it does contain tons of non-new SoC/platform bindings that he's not allowed to break by changing them.
Quoted 4 lines
Different question of course whether you want to be nice to some existing out-of-tree users... but then have in mind that we don't care about out of tree. :) Anyway being nice to out-of-tree is not part of ABI. It's just being nice and useful.
Nobody is suggesting new S32G ABI be compatible with downstream BSPs. These patches and changes we're discussing already differ from the BSP.
My point was that as soon as we merge S32G into mainline, it will become ABI and shouldn't be changed incompatibly anymore once in a release.
These automotive platforms don't run off-the-shelf distros yet and will need to get their bootloaders upstreamed, too. In particular we'll need mainline TF-A to merge the SCMI implementation before we can rely on it here in the kernel for a clk driver; that's holding up MMC and Ethernet.
Best regards,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards
In reply to Rob HerringQuoted 17 lines · Rob Herring
Quoted 16 lines · Chester Lin
Add bindings for S32G2's evaluation board (S32G-VNP-EVB) and reference design 2 board ( S32G-VNP-RDB2).
Signed-off-by Chester Lin <[email protected]>--- Documentation/devicetree/bindings/arm/fsl.yaml | 7 +++++++ 1 file changed, 7 insertions(+)Documentation/devicetree/bindings/arm/fsl.yaml +0
-0@@ -983,6 +983,13 @@ properties: - const: solidrun,lx2160a-cex7 - const: fsl,lx2160a
Quoted 9 lines
Documentation/devicetree/bindings/arm/fsl.yaml properties: · line 991
Quoted 6 lines
Documentation/devicetree/bindings/arm/fsl.yaml +6
-0+ - description: S32G2 based Boards + items: + - enum: + - fsl,s32g274a-evb + - fsl,s32g274a-rdb2 + - const: fsl,s32g2Given this is an entirely different family from i.MX and new?, shouldn't it use 'nxp' instead of 'fsl'?
S32V also still used fsl prefix, despite the company name long being NXP (same for several Layerscape and i.MX models).
If, as Radu indicated on 3/8, NXP wants to make that switch now for S32G then I see no reason against nxp. I verified that it's already defined:
However, should the matching .dts[i] files using nxp prefix (4-6/8) then still go under dts/freescale/, or should they go to a new dts/nxp/ then? That would separate it from S32V. Intel did do a switch from dts/altera/ to dts/intel/ at some point, so there's precedence for either, I guess. No idea whether anything might break if we moved S32V alongside S32G.
Similarly, the easiest and most merge-friendly would be to leave arm/fsl.yaml and add the nxp-prefixed S32G2 there, as done here. If NXP want to rename fsl.yaml to nxp.yaml in a general housekeeping effort, that could be done independently, outside Chester's patchset.
Quoted 3 lines
Either way,
Acked-by Rob Herring <[email protected]>
Thanks,
Andreas
Signature · 9 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg) _______________________________________________ linux-arm-kernel mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
PATCH 2/8 dt-bindings: serial: fsl-linflexuart: convert to json-schema format
In reply to Chester LinConvert the FSL LINFlexD UART binding to json-schema.
--- .../bindings/serial/fsl,s32-linflexuart.txt | 22 --------- .../bindings/serial/fsl,s32-linflexuart.yaml | 48 +++++++++++++++++++ 2 files changed, 48 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt deleted +0 -22
@@ -1,22 +0,0 @@ -* Freescale LINFlexD UART - -The LINFlexD controller implements several LIN protocol versions, as well as -support for full-duplex UART communication through 8-bit and 9-bit frames. - -See chapter 47 ("LINFlexD") in the reference manual[1]. - -Required properties: -- compatible : - - "fsl,s32v234-linflexuart" for LINFlexD configured in UART mode, which - is compatible with the one integrated on S32V234 SoC -- reg : Address and length of the register set for the device -- interrupts : Should contain uart interrupt - -Example: -uart0: serial@40053000 { - compatible = "fsl,s32v234-linflexuart"; - reg = <0x0 0x40053000 0x0 0x1000>; - interrupts = <0 59 4>; -}; - -[1] https://www.nxp.com/webapp/Download?colCode=S32V234RM
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +48 -0
48 lines not on this page · raw message
Signature · 1 line
2.30.0
Re: [PATCH 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format
Quoted 9 lines · Chester Lin
Convert the FSL LINFlexD UART binding to json-schema.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.txt | 22 --------- .../bindings/serial/fsl,s32-linflexuart.yaml | 48 +++++++++++++++++++ 2 files changed, 48 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml
Thanks for your effort, Chester.
Quoted 34 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt deleted +0
-22@@ -1,22 +0,0 @@ -* Freescale LINFlexD UART - -The LINFlexD controller implements several LIN protocol versions, as well as -support for full-duplex UART communication through 8-bit and 9-bit frames. - -See chapter 47 ("LINFlexD") in the reference manual[1]. - -Required properties: -- compatible : - - "fsl,s32v234-linflexuart" for LINFlexD configured in UART mode, which - is compatible with the one integrated on S32V234 SoC -- reg : Address and length of the register set for the device -- interrupts : Should contain uart interrupt - -Example: -uart0: serial@40053000 { - compatible = "fsl,s32v234-linflexuart"; - reg = <0x0 0x40053000 0x0 0x1000>; - interrupts = <0 59 4>; -}; - -[1] https://www.nxp.com/webapp/Download?colCode=S32V234RMDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +0
-0
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 1
Quoted 1 line
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +1
-0@@ -0,0 +1,48 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
Since this is dual-licensed and BSD-2-Clause would seem compatible with GPLv3, this could probably be s/GPL-2.0-only/GPL-2.0-or-later/ ? Not a blocker.
Quoted 6 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +6
-0+%YAML 1.2 +--- +$id: http://devicetree.org/schemas/serial/fsl,s32-linflexuart.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Freescale LINFlexD UART
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 17
Quoted 10 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +10
-0+ +description: | + The LINFlexD controller implements several LIN protocol versions, as well + as support for full-duplex UART communication through 8-bit and 9-bit + frames. See chapter 47 ("LINFlexD") in the reference manual + https://www.nxp.com/webapp/Download?colCode=S32V234RM. + +maintainers: + - Greg Kroah-Hartman <[email protected]> + - Rob Herring <[email protected]>
@Shawn: I assume we need both of them to ack this (or an S32V maintainer to volunteer), since they were not named in the .txt file before?
Quoted 21 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +21
-0+ +allOf: + - $ref: "serial.yaml" + +properties: + compatible: + description: The LINFlexD controller on S32V234 SoC, which can be + configured in UART mode. + items: + - const: fsl,s32v234-linflexuart + + reg: + maxItems: 1 + + interrupts: + maxItems: 1 + +required: + - compatible + - reg + - interrupts
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 48
Quoted 10 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +10
-0+ +unevaluatedProperties: false + +examples: + - | + serial@40053000 { + compatible = "fsl,s32v234-linflexuart"; + reg = <0x40053000 0x1000>; + interrupts = <0 59 4>; + };
Otherwise looking sane,
Thanks,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format
Hi Andreas,
Quoted 44 lines · Andreas Färber
Quoted 9 lines · Chester Lin
Convert the FSL LINFlexD UART binding to json-schema.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.txt | 22 --------- .../bindings/serial/fsl,s32-linflexuart.yaml | 48 +++++++++++++++++++ 2 files changed, 48 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yamlThanks for your effort, Chester.
Quoted 31 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt deleted +0
-22@@ -1,22 +0,0 @@ -* Freescale LINFlexD UART - -The LINFlexD controller implements several LIN protocol versions, as well as -support for full-duplex UART communication through 8-bit and 9-bit frames. - -See chapter 47 ("LINFlexD") in the reference manual[1]. - -Required properties: -- compatible : - - "fsl,s32v234-linflexuart" for LINFlexD configured in UART mode, which - is compatible with the one integrated on S32V234 SoC -- reg : Address and length of the register set for the device -- interrupts : Should contain uart interrupt - -Example: -uart0: serial@40053000 { - compatible = "fsl,s32v234-linflexuart"; - reg = <0x0 0x40053000 0x0 0x1000>; - interrupts = <0 59 4>; -}; - -[1] https://www.nxp.com/webapp/Download?colCode=S32V234RMDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +0
-0
Quoted 8 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 1
Quoted 4 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +1
-0@@ -0,0 +1,48 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)Since this is dual-licensed and BSD-2-Clause would seem compatible with GPLv3, this could probably be s/GPL-2.0-only/GPL-2.0-or-later/ ? Not a blocker.
There's no license identifier in the original file so it's not a problem to choose "GPL-2.0-or-later".
Quoted 66 lines
Quoted 7 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +6
-0+%YAML 1.2 +--- +$id: http://devicetree.org/schemas/serial/fsl,s32-linflexuart.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Freescale LINFlexD UARTDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 17
Quoted 10 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +10
-0+ +description: | + The LINFlexD controller implements several LIN protocol versions, as well + as support for full-duplex UART communication through 8-bit and 9-bit + frames. See chapter 47 ("LINFlexD") in the reference manual + https://www.nxp.com/webapp/Download?colCode=S32V234RM. + +maintainers: + - Greg Kroah-Hartman <[email protected]> + - Rob Herring <[email protected]>@Shawn: I assume we need both of them to ack this (or an S32V maintainer to volunteer), since they were not named in the .txt file before?
Quoted 21 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +21
-0+ +allOf: + - $ref: "serial.yaml" + +properties: + compatible: + description: The LINFlexD controller on S32V234 SoC, which can be + configured in UART mode. + items: + - const: fsl,s32v234-linflexuart + + reg: + maxItems: 1 + + interrupts: + maxItems: 1 + +required: + - compatible + - reg + - interruptsDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 48
Quoted 10 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +10
-0+ +unevaluatedProperties: false + +examples: + - | + serial@40053000 { + compatible = "fsl,s32v234-linflexuart"; + reg = <0x40053000 0x1000>; + interrupts = <0 59 4>; + };Otherwise looking sane,
Reviewed-by Andreas Färber <[email protected]>Thanks,
AndreasSignature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format
Quoted 56 lines · Chester Lin
Hi Andreas,
Quoted 44 lines · Andreas Färber
Quoted 9 lines · Chester Lin
Convert the FSL LINFlexD UART binding to json-schema.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.txt | 22 --------- .../bindings/serial/fsl,s32-linflexuart.yaml | 48 +++++++++++++++++++ 2 files changed, 48 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yamlThanks for your effort, Chester.
Quoted 31 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt deleted +0
-22@@ -1,22 +0,0 @@ -* Freescale LINFlexD UART - -The LINFlexD controller implements several LIN protocol versions, as well as -support for full-duplex UART communication through 8-bit and 9-bit frames. - -See chapter 47 ("LINFlexD") in the reference manual[1]. - -Required properties: -- compatible : - - "fsl,s32v234-linflexuart" for LINFlexD configured in UART mode, which - is compatible with the one integrated on S32V234 SoC -- reg : Address and length of the register set for the device -- interrupts : Should contain uart interrupt - -Example: -uart0: serial@40053000 { - compatible = "fsl,s32v234-linflexuart"; - reg = <0x0 0x40053000 0x0 0x1000>; - interrupts = <0 59 4>; -}; - -[1] https://www.nxp.com/webapp/Download?colCode=S32V234RMDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +0
-0Quoted 8 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 1
Quoted 4 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +1
-0@@ -0,0 +1,48 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)Since this is dual-licensed and BSD-2-Clause would seem compatible with GPLv3, this could probably be s/GPL-2.0-only/GPL-2.0-or-later/ ? Not a blocker.
Quoted 2 lines
There's no license identifier in the original file so it's not a problem to choose "GPL-2.0-or-later".
That is not entirely correct. If there is no explicit license in the file, it's kernel's default so GPL-2.0-only. You cannot relicense derivative work without getting permission from authors and copyright holders.
However if you did not copy the text/description from original bindings, your work won't be derivative so you can relicense it.
Best regards,
Krzysztof
Re: [PATCH 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format
Quoted 60 lines · Krzysztof Kozlowski
Quoted 56 lines · Chester Lin
Hi Andreas,
Quoted 44 lines · Andreas Färber
Quoted 9 lines · Chester Lin
Convert the FSL LINFlexD UART binding to json-schema.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.txt | 22 --------- .../bindings/serial/fsl,s32-linflexuart.yaml | 48 +++++++++++++++++++ 2 files changed, 48 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yamlThanks for your effort, Chester.
Quoted 31 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt deleted +0
-22@@ -1,22 +0,0 @@ -* Freescale LINFlexD UART - -The LINFlexD controller implements several LIN protocol versions, as well as -support for full-duplex UART communication through 8-bit and 9-bit frames. - -See chapter 47 ("LINFlexD") in the reference manual[1]. - -Required properties: -- compatible : - - "fsl,s32v234-linflexuart" for LINFlexD configured in UART mode, which - is compatible with the one integrated on S32V234 SoC -- reg : Address and length of the register set for the device -- interrupts : Should contain uart interrupt - -Example: -uart0: serial@40053000 { - compatible = "fsl,s32v234-linflexuart"; - reg = <0x0 0x40053000 0x0 0x1000>; - interrupts = <0 59 4>; -}; - -[1] https://www.nxp.com/webapp/Download?colCode=S32V234RMDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +0
-0Quoted 8 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 1
Quoted 4 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +1
-0@@ -0,0 +1,48 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)Since this is dual-licensed and BSD-2-Clause would seem compatible with GPLv3, this could probably be s/GPL-2.0-only/GPL-2.0-or-later/ ? Not a blocker.
Quoted 2 lines
There's no license identifier in the original file so it's not a problem to choose "GPL-2.0-or-later".
Quoted 8 lines
That is not entirely correct. If there is no explicit license in the file, it's kernel's default so GPL-2.0-only. You cannot relicense derivative work without getting permission from authors and copyright holders.
However if you did not copy the text/description from original bindings, your work won't be derivative so you can relicense it.
Sorry for my misunderstanding and thanks for the reminder.
Regards,
Chester
Rob Herring
maintainerRe: [PATCH 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format
Quoted 66 lines · Chester Lin
Quoted 65 lines · Krzysztof Kozlowski
Quoted 56 lines · Chester Lin
Hi Andreas,
Quoted 44 lines · Andreas Färber
Quoted 9 lines · Chester Lin
Convert the FSL LINFlexD UART binding to json-schema.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.txt | 22 --------- .../bindings/serial/fsl,s32-linflexuart.yaml | 48 +++++++++++++++++++ 2 files changed, 48 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yamlThanks for your effort, Chester.
Quoted 31 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt deleted +0
-22@@ -1,22 +0,0 @@ -* Freescale LINFlexD UART - -The LINFlexD controller implements several LIN protocol versions, as well as -support for full-duplex UART communication through 8-bit and 9-bit frames. - -See chapter 47 ("LINFlexD") in the reference manual[1]. - -Required properties: -- compatible : - - "fsl,s32v234-linflexuart" for LINFlexD configured in UART mode, which - is compatible with the one integrated on S32V234 SoC -- reg : Address and length of the register set for the device -- interrupts : Should contain uart interrupt - -Example: -uart0: serial@40053000 { - compatible = "fsl,s32v234-linflexuart"; - reg = <0x0 0x40053000 0x0 0x1000>; - interrupts = <0 59 4>; -}; - -[1] https://www.nxp.com/webapp/Download?colCode=S32V234RMDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +0
-0Quoted 8 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 1
Quoted 4 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +1
-0@@ -0,0 +1,48 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)Since this is dual-licensed and BSD-2-Clause would seem compatible with GPLv3, this could probably be s/GPL-2.0-only/GPL-2.0-or-later/ ? Not a blocker.
Quoted 2 lines
There's no license identifier in the original file so it's not a problem to choose "GPL-2.0-or-later".
That is not entirely correct. If there is no explicit license in the file, it's kernel's default so GPL-2.0-only. You cannot relicense derivative work without getting permission from authors and copyright holders.
Quoted 5 lines
Quoted 3 lines
However if you did not copy the text/description from original bindings, your work won't be derivative so you can relicense it.
Sorry for my misunderstanding and thanks for the reminder.
TBC, please try and get permission to relicense. The single author was from NXP so changing the license here just needs the okay from any NXP employee.
But use 'GPL-2.0-only' not 'GPL-2.0-or-later' please. As gregkh says, are you okay with GPLv4, v5, etc.?
Rob
Rob Herring
maintainerRe: [PATCH 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format
In reply to Chester LinQuoted 51 lines · Chester Lin
Convert the FSL LINFlexD UART binding to json-schema.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.txt | 22 --------- .../bindings/serial/fsl,s32-linflexuart.yaml | 48 +++++++++++++++++++ 2 files changed, 48 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yamlDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt deleted +0
-22@@ -1,22 +0,0 @@ -* Freescale LINFlexD UART - -The LINFlexD controller implements several LIN protocol versions, as well as -support for full-duplex UART communication through 8-bit and 9-bit frames. - -See chapter 47 ("LINFlexD") in the reference manual[1]. - -Required properties: -- compatible : - - "fsl,s32v234-linflexuart" for LINFlexD configured in UART mode, which - is compatible with the one integrated on S32V234 SoC -- reg : Address and length of the register set for the device -- interrupts : Should contain uart interrupt - -Example: -uart0: serial@40053000 { - compatible = "fsl,s32v234-linflexuart"; - reg = <0x0 0x40053000 0x0 0x1000>; - interrupts = <0 59 4>; -}; - -[1] https://www.nxp.com/webapp/Download?colCode=S32V234RMDocumentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +7
-0@@ -0,0 +1,48 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/serial/fsl,s32-linflexuart.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Freescale LINFlexD UART
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 17
Quoted 10 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +10
-0+ +description: | + The LINFlexD controller implements several LIN protocol versions, as well + as support for full-duplex UART communication through 8-bit and 9-bit + frames. See chapter 47 ("LINFlexD") in the reference manual + https://www.nxp.com/webapp/Download?colCode=S32V234RM. + +maintainers: + - Greg Kroah-Hartman <[email protected]> + - Rob Herring <[email protected]>
Someone that cares about this h/w, not who applies patches.
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml line 25
Quoted 8 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +8
-0+ +allOf: + - $ref: "serial.yaml" + +properties: + compatible: + description: The LINFlexD controller on S32V234 SoC, which can be + configured in UART mode.
Drop 'on S32V234 SoC' so we're not editting for every new SoC.
Quoted 27 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml new file +23
-0+ items: + - const: fsl,s32v234-linflexuart + + reg: + maxItems: 1 + + interrupts: + maxItems: 1 + +required: + - compatible + - reg + - interrupts + +unevaluatedProperties: false + +examples: + - | + serial@40053000 { + compatible = "fsl,s32v234-linflexuart"; + reg = <0x40053000 0x1000>; + interrupts = <0 59 4>; + };Signature · 1 line
2.30.0
PATCH 3/8 dt-bindings: serial: fsl-linflexuart: Add compatible for S32G2
In reply to Chester LinAdd a compatible string for the uart binding of NXP S32G2 platforms. Here we use "s32v234-linflexuart" as fallback since the current linflexuart driver still works on S32G2.
--- .../bindings/serial/fsl,s32-linflexuart.yaml | 26 ++++++++++++++++--- 1 file changed, 22 insertions(+), 4 deletions(-)
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +22 -4
@@ -21,10 +21,20 @@ allOf: properties: compatible: - description: The LINFlexD controller on S32V234 SoC, which can be - configured in UART mode. - items: - - const: fsl,s32v234-linflexuart + minItems: 1 + maxItems: 2 + oneOf: + - description: The LINFlexD controller on S32G2 SoC, which can be + configured in UART mode. + items: + - enum: + - fsl,s32g2-linflexuart + - const: fsl,s32v234-linflexuart + + - description: The LINFlexD controller on S32V234 SoC, which can be + configured in UART mode. + items: + - const: fsl,s32v234-linflexuart reg: maxItems: 1
@@ -41,8 +51,16 @@ unevaluatedProperties: false examples: - | + /* S32V234 */ serial@40053000 { compatible = "fsl,s32v234-linflexuart"; reg = <0x40053000 0x1000>; interrupts = <0 59 4>; }; + + /* S32G2 */ + serial@401c8000 { + compatible = "fsl,s32g2-linflexuart", "fsl,s32v234-linflexuart"; + reg = <0x401c8000 0x3000>; + interrupts = <0 82 1>; + };
Signature · 1 line
2.30.0
Re: [PATCH 3/8] dt-bindings: serial: fsl-linflexuart: Add compatible for S32G2
Quoted 14 lines · Chester Lin
Add a compatible string for the uart binding of NXP S32G2 platforms. Here we use "s32v234-linflexuart" as fallback since the current linflexuart driver still works on S32G2.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.yaml | 26 ++++++++++++++++--- 1 file changed, 22 insertions(+), 4 deletions(-)Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +0
-0
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml allOf: · line 25
Quoted 9 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +2
-4@@ -21,10 +21,20 @@ allOf: properties: compatible: - description: The LINFlexD controller on S32V234 SoC, which can be - configured in UART mode. - items: - - const: fsl,s32v234-linflexuart + minItems: 1 + maxItems: 2
Are these necessary for oneOf?
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml allOf: · line 32
Quoted 7 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +7
-0+ oneOf: + - description: The LINFlexD controller on S32G2 SoC, which can be + configured in UART mode. + items: + - enum: + - fsl,s32g2-linflexuart + - const: fsl,s32v234-linflexuart
This reads inconsistent to me: Either this oneOf is for S32G2 only, then please turn the enum into a const. Or change the description to "on SoCs compatible with S32V234" if we expect the enum list to grow.
I believe the idea here was to avoid unnecessary driver compatible and earlycon compatible additions, while preparing for eventual quirks specific to S32G2.
@NXP: Should this be s32g2- like above or s32g274a- specifically? Do you agree this is a useful thing to prepare here, as opposed to using only s32v234- in the s32g2* DT?
I assume the ordering is done alphabetically as S32G < S32V; alternatively we might order S32V234 first and then the compatible ones.
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml allOf: · line 37
Quoted 5 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +5
-0+ + - description: The LINFlexD controller on S32V234 SoC, which can be + configured in UART mode. + items: + - const: fsl,s32v234-linflexuart
To minimize this S32G2 patch, would it be valid to do oneOf for the single S32V in the preceding patch already? Then we would avoid the text movement and re-indentation above and more easily see the lines newly getting added for S32G2.
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml unevaluatedProperties: false · line 54
Quoted 8 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +1
-0reg: maxItems: 1@@ -41,8 +51,16 @@ unevaluatedProperties: false examples: - | + /* S32V234 */
Could this be:
- description: S32V234
|
?
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml unevaluatedProperties: false · line 61
Quoted 7 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +2
-0serial@40053000 { compatible = "fsl,s32v234-linflexuart"; reg = <0x40053000 0x1000>; interrupts = <0 59 4>; }; + + /* S32G2 */
This should not be part of the S32V example, but a new one:
- |
(or with description, as discussed above)
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml unevaluatedProperties: false · line 63
Quoted 2 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +2
-0+ serial@401c8000 { + compatible = "fsl,s32g2-linflexuart", "fsl,s32v234-linflexuart";
Potentially affected by naming discussions above.
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml unevaluatedProperties: false · line 66
Quoted 3 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +3
-0+ reg = <0x401c8000 0x3000>; + interrupts = <0 82 1>; + };
Regards,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 3/8] dt-bindings: serial: fsl-linflexuart: Add compatible for S32G2
Quoted 55 lines · Andreas Färber
Quoted 23 lines · Chester Lin
Add a compatible string for the uart binding of NXP S32G2 platforms. Here
we use "s32v234-linflexuart" as fallback since the current linflexuart
driver still works on S32G2.Signed-off-by Chester Lin <[email protected]>---
.../bindings/serial/fsl,s32-linflexuart.yaml | 26
++++++++++++++++---1 file changed, 22 insertions(+), 4 deletions(-)(quoted diff) +0
-0
linflexuart.yamlb/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yamlindexacfe34706ccb..e731f3f6cea4100644
--- a/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml
+++ b/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml(quoted diff) +0
-0@@ -21,10 +21,20 @@ allOf:
properties:Quoted 8 lines
compatible:
- description: The LINFlexD controller on S32V234 SoC, which can be
- configured in UART mode.
- items:
- - const: fsl,s32v234-linflexuart
+ minItems: 1
+ maxItems: 2Are these necessary for oneOf?
Quoted 8 lines
+ oneOf:
+ - description: The LINFlexD controller on S32G2 SoC, which can be
+ configured in UART mode.
+ items:
+ - enum:
+ - fsl,s32g2-linflexuart
+ - const: fsl,s32v234-linflexuartThis reads inconsistent to me: Either this oneOf is for S32G2 only, then
please turn the enum into a const. Or change the description to "on SoCs
compatible with S32V234" if we expect the enum list to grow.I believe the idea here was to avoid unnecessary driver compatible and
earlycon compatible additions, while preparing for eventual quirks specific to S32G2.
Quoted 5 lines
@NXP: Should this be s32g2- like above or s32g274a- specifically? Do you
agree this is a useful thing to prepare here, as opposed to using only
s32v234- in the s32g2* DT?
s32g2- is fine, but the vendor should be nxp, not fsl. nxp,s32g2-linflexuart
Quoted 59 lines
I assume the ordering is done alphabetically as S32G < S32V; alternatively we might order S32V234 first and then the compatible ones.
Quoted 6 lines
+
+ - description: The LINFlexD controller on S32V234 SoC, which can be
+ configured in UART mode.
+ items:
+ - const: fsl,s32v234-linflexuartTo minimize this S32G2 patch, would it be valid to do oneOf for the single S32V in the preceding patch already? Then we would avoid the text
movement and re-indentation above and more easily see the lines newly getting added for S32G2.Quoted 8 lines
reg:
maxItems: 1(quoted diff) +0
-0@@ -41,8 +51,16 @@ unevaluatedProperties: false
examples:
- |
+ /* S32V234 */Could this be:
- description: S32V234
|
?Quoted 7 lines
serial@40053000 {
compatible = "fsl,s32v234-linflexuart";
reg = <0x400530000x1000>;
interrupts = <0 59 4>;
};
+
+ /* S32G2 */This should not be part of the S32V example, but a new one:
- |
(or with description, as discussed above)
Quoted 3 lines
+ serial@401c8000 {
+ compatible = "fsl,s32g2-linflexuart", "fsl,s32v234- linflexuart";Potentially affected by naming discussions above.
Quoted 3 lines
+ reg = <
0x401c80000x3000>;
+ interrupts = <0 82 1>;
+ };Regards,
Andreas
Rob Herring
maintainerRe: [PATCH 3/8] dt-bindings: serial: fsl-linflexuart: Add compatible for S32G2
In reply to Andreas FärberQuoted 66 lines · Andreas Färber
Quoted 14 lines · Chester Lin
Add a compatible string for the uart binding of NXP S32G2 platforms. Here we use "s32v234-linflexuart" as fallback since the current linflexuart driver still works on S32G2.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.yaml | 26 ++++++++++++++++--- 1 file changed, 22 insertions(+), 4 deletions(-)Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +0
-0Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml allOf: · line 25
Quoted 9 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +2
-4@@ -21,10 +21,20 @@ allOf: properties: compatible: - description: The LINFlexD controller on S32V234 SoC, which can be - configured in UART mode. - items: - - const: fsl,s32v234-linflexuart + minItems: 1 + maxItems: 2Are these necessary for oneOf?
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml allOf: · line 32
Quoted 7 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +7
-0+ oneOf: + - description: The LINFlexD controller on S32G2 SoC, which can be + configured in UART mode. + items: + - enum: + - fsl,s32g2-linflexuart + - const: fsl,s32v234-linflexuartThis reads inconsistent to me: Either this oneOf is for S32G2 only, then please turn the enum into a const. Or change the description to "on SoCs compatible with S32V234" if we expect the enum list to grow.
I believe the idea here was to avoid unnecessary driver compatible and earlycon compatible additions, while preparing for eventual quirks specific to S32G2.
@NXP: Should this be s32g2- like above or s32g274a- specifically? Do you agree this is a useful thing to prepare here, as opposed to using only s32v234- in the s32g2* DT?
I assume the ordering is done alphabetically as S32G < S32V; alternatively we might order S32V234 first and then the compatible ones.
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml allOf: · line 37
Quoted 5 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +5
-0+ + - description: The LINFlexD controller on S32V234 SoC, which can be + configured in UART mode. + items: + - const: fsl,s32v234-linflexuartTo minimize this S32G2 patch, would it be valid to do oneOf for the single S32V in the preceding patch already? Then we would avoid the text movement and re-indentation above and more easily see the lines newly getting added for S32G2.
Quoted 5 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +0
-0reg: maxItems: 1@@ -41,8 +51,16 @@ unevaluatedProperties: false
Quoted 8 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml unevaluatedProperties: false · line 54
Quoted 3 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +1
-0examples: - | + /* S32V234 */Could this be:
- description: S32V234|?
No, that would not be valid json-schema.
Rob
Rob Herring
maintainerRe: [PATCH 3/8] dt-bindings: serial: fsl-linflexuart: Add compatible for S32G2
In reply to Chester LinQuoted 14 lines · Chester Lin
Add a compatible string for the uart binding of NXP S32G2 platforms. Here we use "s32v234-linflexuart" as fallback since the current linflexuart driver still works on S32G2.
Signed-off-by Chester Lin <[email protected]>--- .../bindings/serial/fsl,s32-linflexuart.yaml | 26 ++++++++++++++++--- 1 file changed, 22 insertions(+), 4 deletions(-)Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +0
-0
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml allOf: · line 25
Quoted 9 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +2
-4@@ -21,10 +21,20 @@ allOf: properties: compatible: - description: The LINFlexD controller on S32V234 SoC, which can be - configured in UART mode. - items: - - const: fsl,s32v234-linflexuart + minItems: 1 + maxItems: 2
minItems/maxItems not needed here.
Quoted 22 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +13
-0+ oneOf: + - description: The LINFlexD controller on S32G2 SoC, which can be + configured in UART mode. + items: + - enum: + - fsl,s32g2-linflexuart + - const: fsl,s32v234-linflexuart + + - description: The LINFlexD controller on S32V234 SoC, which can be + configured in UART mode. + items: + - const: fsl,s32v234-linflexuart reg: maxItems: 1@@ -41,8 +51,16 @@ unevaluatedProperties: false examples: - | + /* S32V234 */ serial@40053000 { compatible = "fsl,s32v234-linflexuart";
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml unevaluatedProperties: false · line 66
Quoted 10 lines
Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml +7
-0reg = <0x40053000 0x1000>; interrupts = <0 59 4>; }; + + /* S32G2 */ + serial@401c8000 { + compatible = "fsl,s32g2-linflexuart", "fsl,s32v234-linflexuart"; + reg = <0x401c8000 0x3000>; + interrupts = <0 82 1>; + };
This doesn't really warrant another example just for a new compatible string.
PATCH 4/8 arm64: dts: add NXP S32G2 support
In reply to Chester LinAdd an initial dtsi file for generic SoC features of NXP S32G2.
--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 98 ++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsi
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +98 -0
@@ -0,0 +1,98 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/* + * Copyright (c) 2021 SUSE LLC + */ + +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/ { + compatible = "fsl,s32g2"; + interrupt-parent = <&gic>; + #address-cells = <2>; + #size-cells = <2>; + + cpus { + #address-cells = <1>; + #size-cells = <0>; + + cpu0: cpu@0 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x0>; + enable-method = "psci"; + next-level-cache = <&cluster0_l2>; + }; + + cpu1: cpu@1 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x1>; + enable-method = "psci"; + next-level-cache = <&cluster0_l2>; + }; + + cpu2: cpu@100 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x100>; + enable-method = "psci"; + next-level-cache = <&cluster1_l2>; + }; + + cpu3: cpu@101 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x101>; + enable-method = "psci"; + next-level-cache = <&cluster1_l2>; + }; + + cluster0_l2: l2-cache0 { + compatible = "cache"; + }; + + cluster1_l2: l2-cache1 { + compatible = "cache"; + }; + }; + + pmu { + compatible = "arm,cortex-a53-pmu"; + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>; + }; + + timer { + compatible = "arm,armv8-timer"; + interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; + }; + + psci { + compatible = "arm,psci-1.0"; + method = "smc"; + }; + + soc { + compatible = "simple-bus"; + interrupt-parent = <&gic>; + #address-cells = <2>; + #size-cells = <2>; + + ranges; + + gic: interrupt-controller@50800000 { + compatible = "arm,gic-v3"; + #interrupt-cells = <3>; + interrupt-controller; + reg = <0 0x50800000 0 0x10000>, + <0 0x50880000 0 0x200000>, + <0 0x50400000 0 0x2000>, + <0 0x50410000 0 0x2000>, + <0 0x50420000 0 0x2000>; + interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) | + IRQ_TYPE_LEVEL_HIGH)>; + }; + }; +};
Signature · 1 line
2.30.0
Re: [PATCH 4/8] arm64: dts: add NXP S32G2 support
Hi Chester et al.,
arch/arm64/boot/dts/freescale/s32g2.dtsi
Quoted 13 lines · Chester Lin
Add an initial dtsi file for generic SoC features of NXP S32G2.
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 98 ++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsiarch/arm64/boot/dts/freescale/s32g2.dtsi new file +0
-0
Note: This DT is for running on the Cortex-A53 cores, but S32G2 also has Cortex-M7 cores. For Vybrid SoCs, DTs later got contributed to also run on its Cortex-M4 core:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf610.dtsi
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf500.dtsi
vs.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf610m4.dtsi
Should we plan for this in our file naming here and in following patches (e.g., s32g2-a53* vs. s32g2-m7*)? To me, a later concatenation of s32g274am7* would look awkward, and s32g274a-m7* would sort between -evb and -rdb2.
arch/arm64/boot/dts/freescale/s32g2.dtsi line 2
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0@@ -0,0 +1,98 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/*
* NXP S32G2 SoC family
*
?
@NXP: Are any models other than 274A in the queue that we should distinguish between s32g2.dtsi and s32g274a.dtsi here already?
Quoted 49 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +49
-0+ * Copyright (c) 2021 SUSE LLC + */ + +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/ { + compatible = "fsl,s32g2"; + interrupt-parent = <&gic>; + #address-cells = <2>; + #size-cells = <2>; + + cpus { + #address-cells = <1>; + #size-cells = <0>; + + cpu0: cpu@0 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x0>; + enable-method = "psci"; + next-level-cache = <&cluster0_l2>; + }; + + cpu1: cpu@1 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x1>; + enable-method = "psci"; + next-level-cache = <&cluster0_l2>; + }; + + cpu2: cpu@100 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x100>; + enable-method = "psci"; + next-level-cache = <&cluster1_l2>; + }; + + cpu3: cpu@101 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x101>; + enable-method = "psci"; + next-level-cache = <&cluster1_l2>; + }; + + cluster0_l2: l2-cache0 { + compatible = "cache";
arch/arm64/boot/dts/freescale/s32g2.dtsi line 61
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +10
-0+ }; + + cluster1_l2: l2-cache1 { + compatible = "cache"; + }; + }; + + pmu { + compatible = "arm,cortex-a53-pmu"; + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>;
interrupt-affinity = <&cpu0>, <&cpu1>, <&cpu2>, <&cpu3>;
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +4
-0+ }; + + timer { + compatible = "arm,armv8-timer";
arch/arm64/boot/dts/freescale/s32g2.dtsi line 75
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +10
-0+ interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; + }; + + psci { + compatible = "arm,psci-1.0"; + method = "smc"; + };
Should we move this into a /firmware node, to group with future OP-TEE?
arch/arm64/boot/dts/freescale/s32g2.dtsi line 79
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +4
-0+ + soc { + compatible = "simple-bus"; + interrupt-parent = <&gic>;
Duplicate, already set on root node.
arch/arm64/boot/dts/freescale/s32g2.dtsi line 81
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0+ #address-cells = <2>; + #size-cells = <2>;
Why? Does it have any peripherals that go beyond 32-bit space? For 64-bit Realtek platforms Rob had asked me to use 1, if possible. I do understand that for /memory nodes we do have high-memory addresses, so 2 for the root node looks correct.
arch/arm64/boot/dts/freescale/s32g2.dtsi line 82
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +1
-0+
Please drop this white line.
arch/arm64/boot/dts/freescale/s32g2.dtsi line 83
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +1
-0+ ranges;
According to Rob, the /soc ranges should exclude any RAM ranges for safety reasons. Compare:
If you're lacking the maximum RAM areas to carve out, NXP is in CC to help out :) and the EVB and RDB2 boards should give you starting numbers that could be enlarged later if needed.
arch/arm64/boot/dts/freescale/s32g2.dtsi line 93
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +10
-0+ + gic: interrupt-controller@50800000 { + compatible = "arm,gic-v3"; + #interrupt-cells = <3>; + interrupt-controller; + reg = <0 0x50800000 0 0x10000>, + <0 0x50880000 0 0x200000>, + <0 0x50400000 0 0x2000>, + <0 0x50410000 0 0x2000>, + <0 0x50420000 0 0x2000>;
Please order reg after compatible by convention, and sort interrupt-controller or at least #interrupt-cells (applying to consumers) last, after the below one applying to this device itself.
arch/arm64/boot/dts/freescale/s32g2.dtsi line 96
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) | + IRQ_TYPE_LEVEL_HIGH)>; + };
CC'ing Marc for additional GIC scrutiny, often the sizes are wrong.
arch/arm64/boot/dts/freescale/s32g2.dtsi line 98
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0+ }; +};
Thanks,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 4/8] arm64: dts: add NXP S32G2 support
Quoted 31 lines · Andreas Färber
Hi Chester et al.,
arch/arm64/boot/dts/freescale/s32g2.dtsi
Quoted 13 lines · Chester Lin
Add an initial dtsi file for generic SoC features of NXP S32G2.
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 98 ++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsiarch/arm64/boot/dts/freescale/s32g2.dtsi new file +0
-0Note: This DT is for running on the Cortex-A53 cores, but S32G2 also has Cortex-M7 cores. For Vybrid SoCs, DTs later got contributed to also run on its Cortex-M4 core:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf610.dtsi
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf500.dtsi
vs.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf610m4.dtsiShould we plan for this in our file naming here and in following patches (e.g., s32g2-a53* vs. s32g2-m7*)? To me, a later concatenation of s32g274am7* would look awkward, and s32g274a-m7* would sort between -evb and -rdb2.
Quoted 7 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 2
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0@@ -0,0 +1,98 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/** NXP S32G2 SoC family
*
?
Will add it.
Quoted 57 lines
@NXP: Are any models other than 274A in the queue that we should distinguish between
s32g2.dtsiands32g274a.dtsihere already?Quoted 53 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +53
-0+ * Copyright (c) 2021 SUSE LLC + */ + +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/ { + compatible = "fsl,s32g2"; + interrupt-parent = <&gic>; + #address-cells = <2>; + #size-cells = <2>; + + cpus { + #address-cells = <1>; + #size-cells = <0>; + + cpu0: cpu@0 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x0>; + enable-method = "psci"; + next-level-cache = <&cluster0_l2>; + }; + + cpu1: cpu@1 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x1>; + enable-method = "psci"; + next-level-cache = <&cluster0_l2>; + }; + + cpu2: cpu@100 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x100>; + enable-method = "psci"; + next-level-cache = <&cluster1_l2>; + }; + + cpu3: cpu@101 { + device_type = "cpu"; + compatible = "arm,cortex-a53"; + reg = <0x101>; + enable-method = "psci"; + next-level-cache = <&cluster1_l2>; + }; + + cluster0_l2: l2-cache0 { + compatible = "cache"; + }; + + cluster1_l2: l2-cache1 { + compatible = "cache";
Quoted 8 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 61
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +6
-0+ }; + }; + + pmu { + compatible = "arm,cortex-a53-pmu"; + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>;interrupt-affinity = <&cpu0>, <&cpu1>, <&cpu2>, <&cpu3>;
Actually I traced the pmu_parse_irqs() and found that this SoC never falls into the pmu_has_irq_affinity() check because it's a percpu IRQ so the flow ends at pmu_parse_percpu_irq(). But it looks good to me to have an interrupt-affinity to indicate that each core has an associated PPI for PMU events as the binding file has suggested.
Quoted 18 lines
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +4
-0+ }; + + timer { + compatible = "arm,armv8-timer";arch/arm64/boot/dts/freescale/s32g2.dtsi line 75
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +10
-0+ interrupts = <GIC_PPI 13 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 14 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 11 IRQ_TYPE_LEVEL_LOW>, + <GIC_PPI 10 IRQ_TYPE_LEVEL_LOW>; + }; + + psci { + compatible = "arm,psci-1.0"; + method = "smc"; + };Should we move this into a /firmware node, to group with future OP-TEE?
So far I can only see a few examples [e.g. ti/k3-*] which add the psci node into /firmware but logically we should do it.
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 79
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +4
-0+ + soc { + compatible = "simple-bus"; + interrupt-parent = <&gic>;Duplicate, already set on root node.
Will remove it.
Quoted 8 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 81
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0+ #address-cells = <2>; + #size-cells = <2>;Why? Does it have any peripherals that go beyond 32-bit space? For 64-bit Realtek platforms Rob had asked me to use 1, if possible. I do understand that for /memory nodes we do have high-memory addresses, so 2 for the root node looks correct.
Actually it's a limitation due to [PATCH 7/8] "arm64: dts: s32g2: add memory nodes for evb and rdb2", which adds memory nodes to indicate maximum system RAM size combined by two separated memory banks, and the second bank starts from the offset 0x880000000 so that's why we need 64-bit address space here. Please feel free to let me know if any suggestion.
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 82
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +1
-0+Please drop this white line.
Will do.
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 83
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +1
-0+ ranges;According to Rob, the /soc ranges should exclude any RAM ranges for safety reasons. Compare:
If you're lacking the maximum RAM areas to carve out, NXP is in CC to help out :) and the EVB and RDB2 boards should give you starting numbers that could be enlarged later if needed.
I added memory nodes in [PATCH 7/8] "arm64: dts: s32g2: add memory nodes for evb and rdb2" to describe maximum RAM areas, which are based on the information we found in NXP BSP and boards.
@NXP: Please feel free to correct me if anything wrong, thanks.
Quoted 16 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 93
Quoted 11 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +10
-0+ + gic: interrupt-controller@50800000 { + compatible = "arm,gic-v3"; + #interrupt-cells = <3>; + interrupt-controller; + reg = <0 0x50800000 0 0x10000>, + <0 0x50880000 0 0x200000>, + <0 0x50400000 0 0x2000>, + <0 0x50410000 0 0x2000>, + <0 0x50420000 0 0x2000>;Please order reg after compatible by convention, and sort interrupt-controller or at least #interrupt-cells (applying to consumers) last, after the below one applying to this device itself.
Will do.
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 96
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) | + IRQ_TYPE_LEVEL_HIGH)>; + };CC'ing Marc for additional GIC scrutiny, often the sizes are wrong.
IIRC, gic-v3 shouldn't have this kind of interrupt specifier. It's my fault and will fix it. Feel free to let me know if any suggestions.
Quoted 12 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 98
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0+ }; +};Thanks,
AndreasSignature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 4/8] arm64: dts: add NXP S32G2 support
Hi Chester,
Quoted 54 lines · Chester Lin
Quoted 29 lines · Andreas Färber
arch/arm64/boot/dts/freescale/s32g2.dtsi
Quoted 13 lines · Chester Lin
Add an initial dtsi file for generic SoC features of NXP S32G2.
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 98 ++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsiarch/arm64/boot/dts/freescale/s32g2.dtsi new file +0
-0Note: This DT is for running on the Cortex-A53 cores, but S32G2 also has Cortex-M7 cores. For Vybrid SoCs, DTs later got contributed to also run on its Cortex-M4 core:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf610.dtsi
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf500.dtsi
vs.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/vf610m4.dtsiShould we plan for this in our file naming here and in following patches (e.g., s32g2-a53* vs. s32g2-m7*)? To me, a later concatenation of s32g274am7* would look awkward, and s32g274a-m7* would sort between -evb and -rdb2.
Quoted 7 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 2
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0@@ -0,0 +1,98 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/** NXP S32G2 SoC family
*
?Will add it.
Quoted 14 lines
@NXP: Are any models other than 274A in the queue that we should distinguish between
s32g2.dtsiands32g274a.dtsihere already?Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +10
-0+ * Copyright (c) 2021 SUSE LLC + */ + +#include <dt-bindings/interrupt-controller/arm-gic.h> + +/ { + compatible = "fsl,s32g2"; + interrupt-parent = <&gic>; + #address-cells = <2>; + #size-cells = <2>;
[...]
Quoted 11 lines
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 61
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ pmu { + compatible = "arm,cortex-a53-pmu"; + interrupts = <GIC_PPI 7 IRQ_TYPE_LEVEL_HIGH>;interrupt-affinity = <&cpu0>, <&cpu1>, <&cpu2>, <&cpu3>;
Actually I traced the
pmu_parse_irqs()and found that this SoC never falls into thepmu_has_irq_affinity()check because it's a percpu IRQ so the flow ends atpmu_parse_percpu_irq(). But it looks good to me to have an interrupt-affinity to indicate that each core has an associated PPI for PMU events as the binding file has suggested.
My comment was based on the DT binding requesting it also for PPI and previous review requests for me to add it elsewhere, so it's quite possible that your code analysis is correct.
FWIW also the cache nodes were not evaluated last time I checked, although the specs do show those nodes and properties.
https://github.com/devicetree-org/devicetree-specification/blob/v0.3/source/devicenodes.rst
Quoted 1 line
Quoted 1 line
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +1
-0+ };
[...]
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ + soc { + compatible = "simple-bus";
[...]
Quoted 8 lines
Quoted 7 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0+ #address-cells = <2>; + #size-cells = <2>;Why? Does it have any peripherals that go beyond 32-bit space? For 64-bit Realtek platforms Rob had asked me to use 1, if possible. I do understand that for /memory nodes we do have high-memory addresses, so 2 for the root node looks correct.
Quoted 5 lines
Actually it's a limitation due to [PATCH 7/8] "arm64: dts: s32g2: add memory nodes for evb and rdb2", which adds memory nodes to indicate maximum system RAM size combined by two separated memory banks, and the second bank starts from the offset
0x880000000so that's why we need 64-bit address space here. Please feel free to let me know if any suggestion.
The /memory nodes are on the root node and thus only use #address-cells and #size-cells from /, not from /soc here. Thus the only criterium is whether something within /soc needs it.
PCI controllers may have 3 address cells, SPI/I2C controllers 1, so you can have multiple sizes within one DT, you just need suitable ranges wherever mappings to the parent address space are needed.
(I thought you had that distinction in an earlier draft I reviewed.)
Similarly, /reserved-memory would be outside the /soc node and use the root node's #(address|size)-cells.
Note: I'm assuming that if someone were to add a DT for the Cortex-M7s, the address space mapping of any shared peripherals will likely differ, as would the interrupts obviously, so I assume no direct .dtsi sharing of /soc sub-nodes could sensibly be applied here.
@NXP: Please correct me if I'm wrong in either M7 not having access to DDR RAM or large enough SRAM for Linux or another DT-consuming OS (and this line of thinking not being applicable then) or you having use cases to factor out some of the /soc sub-nodes for sharing between the two (which would then give another reason for #address-/size-cells = <1> for 32-bit Cortex-M7).
[...]
Quoted 7 lines
Quoted 7 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 83
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +1
-0+ ranges;According to Rob, the /soc ranges should exclude any RAM ranges for safety reasons. Compare:
Quoted 7 lines
Quoted 3 lines
If you're lacking the maximum RAM areas to carve out, NXP is in CC to help out :) and the EVB and RDB2 boards should give you starting numbers that could be enlarged later if needed.
I added memory nodes in [PATCH 7/8] "arm64: dts: s32g2: add memory nodes for evb and rdb2" to describe maximum RAM areas, which are based on the information we found in NXP BSP and boards.
Yes, as discussed in 7/8, you should be using here:
ranges = <0x0 0 0x0 0x80000000>; /* excluding 4 GiB RAM */
https://github.com/devicetree-org/devicetree-specification/blob/v0.3/source/devicetree-basics.rst
Quoted 28 lines
@NXP: Please feel free to correct me if anything wrong, thanks.
Quoted 16 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 93
Quoted 11 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +10
-0+ + gic: interrupt-controller@50800000 { + compatible = "arm,gic-v3"; + #interrupt-cells = <3>; + interrupt-controller; + reg = <0 0x50800000 0 0x10000>, + <0 0x50880000 0 0x200000>, + <0 0x50400000 0 0x2000>, + <0 0x50410000 0 0x2000>, + <0 0x50420000 0 0x2000>;Please order reg after compatible by convention, and sort interrupt-controller or at least #interrupt-cells (applying to consumers) last, after the below one applying to this device itself.
Will do.
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 96
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) | + IRQ_TYPE_LEVEL_HIGH)>; + };CC'ing Marc for additional GIC scrutiny, often the sizes are wrong.
Quoted 2 lines
IIRC, gic-v3 shouldn't have this kind of interrupt specifier. It's my fault and will fix it. Feel free to let me know if any suggestions.
You probably mean the GIC_CPU_MASK_SIMPLE()?
interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH>;
The interrupts property will be used by KVM (or possibly Xen) for vGIC. Please ensure that the Kconfig you use for testing has KVM enabled.
Quoted 2 lines
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +2
-0+ }; +};
Cheers,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Marc Zyngier
maintainerRe: [PATCH 4/8] arm64: dts: add NXP S32G2 support
In reply to Andreas FärberQuoted 17 lines · Andreas Färber
Hi Chester et al.,
Quoted 13 lines · Chester Lin
Add an initial dtsi file for generic SoC features of NXP S32G2.
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 98 ++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsiarch/arm64/boot/dts/freescale/s32g2.dtsi new file +0
-0
[...]
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 90
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +6
-0+ gic: interrupt-controller@50800000 { + compatible = "arm,gic-v3"; + #interrupt-cells = <3>; + interrupt-controller; + reg = <0 0x50800000 0 0x10000>, + <0 0x50880000 0 0x200000>,
That's enough redistributor space for 16 CPUs. However, you only describe 4. Either the number of CPUs is wrong, the size is wrong, or the GIC has been configured for more cores than the SoC has.
Quoted 8 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 93
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ <0 0x50400000 0 0x2000>, + <0 0x50410000 0 0x2000>, + <0 0x50420000 0 0x2000>;Please order reg after compatible by convention, and sort interrupt-controller or at least #interrupt-cells (applying to consumers) last, after the below one applying to this device itself.
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 96
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) | + IRQ_TYPE_LEVEL_HIGH)>; + };CC'ing Marc for additional GIC scrutiny, often the sizes are wrong.
There is more than just sizes. The interrupt specifier for the maintenance interrupt is also wrong.
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Re: [PATCH 4/8] arm64: dts: add NXP S32G2 support
Quoted 22 lines · Marc Zyngier
Quoted 17 lines · Andreas Färber
Hi Chester et al.,
Quoted 13 lines · Chester Lin
Add an initial dtsi file for generic SoC features of NXP S32G2.
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 98 ++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsiarch/arm64/boot/dts/freescale/s32g2.dtsi new file +0
-0[...]
Quoted 10 lines
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 90
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +6
-0+ gic: interrupt-controller@50800000 { + compatible = "arm,gic-v3"; + #interrupt-cells = <3>; + interrupt-controller; + reg = <0 0x50800000 0 0x10000>, + <0 0x50880000 0 0x200000>,That's enough redistributor space for 16 CPUs. However, you only describe 4. Either the number of CPUs is wrong, the size is wrong, or the GIC has been configured for more cores than the SoC has.
Confirmed the SoC can only find 4 redistributors:
localhost:~ # dmesg | grep CPU
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=480 to nr_cpu_ids=4. [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000050880000 [ 0.063865] smp: Bringing up secondary CPUs ... [ 0.068852] Detected VIPT I-cache on CPU1 [ 0.068894] GICv3: CPU1: found redistributor 1 region 0:0x00000000508a0000 [ 0.068963] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.069809] Detected VIPT I-cache on CPU2 [ 0.069851] GICv3: CPU2: found redistributor 100 region 0:0x00000000508c0000 [ 0.069903] CPU2: Booted secondary processor 0x0000000100 [0x410fd034] [ 0.070698] Detected VIPT I-cache on CPU3 [ 0.070722] GICv3: CPU3: found redistributor 101 region 0:0x00000000508e0000 [ 0.070749] CPU3: Booted secondary processor 0x0000000101 [0x410fd034] [ 0.070847] smp: Brought up 1 node, 4 CPUs
<..snip..>
I will correct the size to 0x80000, thanks!
Quoted 15 lines
Quoted 9 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 93
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ <0 0x50400000 0 0x2000>, + <0 0x50410000 0 0x2000>, + <0 0x50420000 0 0x2000>;Please order reg after compatible by convention, and sort interrupt-controller or at least #interrupt-cells (applying to consumers) last, after the below one applying to this device itself.
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 96
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +3
-0+ interrupts = <GIC_PPI 9 (GIC_CPU_MASK_SIMPLE(4) | + IRQ_TYPE_LEVEL_HIGH)>; + };CC'ing Marc for additional GIC scrutiny, often the sizes are wrong.
Quoted 4 lines
There is more than just sizes. The interrupt specifier for the maintenance interrupt is also wrong.
M.
I will remove the wrong interrupt specifier. Thanks!
Chester.
Quoted 4 lines
Signature · 2 lines
-- Without deviation from the norm, progress is not possible.
Marc Zyngier
maintainerRe: [PATCH 4/8] arm64: dts: add NXP S32G2 support
Quoted 56 lines · Chester Lin
Quoted 22 lines · Marc Zyngier
Quoted 17 lines · Andreas Färber
Hi Chester et al.,
Quoted 13 lines · Chester Lin
Add an initial dtsi file for generic SoC features of NXP S32G2.
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 98 ++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsiarch/arm64/boot/dts/freescale/s32g2.dtsi new file +0
-0[...]
Quoted 10 lines
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 90
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +6
-0+ gic: interrupt-controller@50800000 { + compatible = "arm,gic-v3"; + #interrupt-cells = <3>; + interrupt-controller; + reg = <0 0x50800000 0 0x10000>, + <0 0x50880000 0 0x200000>,That's enough redistributor space for 16 CPUs. However, you only describe 4. Either the number of CPUs is wrong, the size is wrong, or the GIC has been configured for more cores than the SoC has.
Confirmed the SoC can only find 4 redistributors:
localhost:~ # dmesg | grep CPU
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=480 to nr_cpu_ids=4. [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000050880000 [ 0.063865] smp: Bringing up secondary CPUs ... [ 0.068852] Detected VIPT I-cache on CPU1 [ 0.068894] GICv3: CPU1: found redistributor 1 region 0:0x00000000508a0000 [ 0.068963] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.069809] Detected VIPT I-cache on CPU2 [ 0.069851] GICv3: CPU2: found redistributor 100 region 0:0x00000000508c0000 [ 0.069903] CPU2: Booted secondary processor 0x0000000100 [0x410fd034] [ 0.070698] Detected VIPT I-cache on CPU3 [ 0.070722] GICv3: CPU3: found redistributor 101 region 0:0x00000000508e0000 [ 0.070749] CPU3: Booted secondary processor 0x0000000101 [0x410fd034] [ 0.070847] smp: Brought up 1 node, 4 CPUs
Quoted 1 line
<..snip..>
That's not the correct way to find out. Each CPU tries to find its matching RD in the region. This doesn't mean there aren't more RDs present in the GIC.
You need to iterate over all the RDs in the region until you find one that has GICR_TYPER.Last == 1. This will give you the actual count. Alternatively, you can check whether the RD at 508e0000 has that bit set. If it doesn't, then you know there are more RDs than CPUs.
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Re: [PATCH 4/8] arm64: dts: add NXP S32G2 support
Hi Marc,
Quoted 64 lines · Marc Zyngier
Quoted 56 lines · Chester Lin
Quoted 22 lines · Marc Zyngier
Quoted 17 lines · Andreas Färber
Hi Chester et al.,
Quoted 13 lines · Chester Lin
Add an initial dtsi file for generic SoC features of NXP S32G2.
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 98 ++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsiarch/arm64/boot/dts/freescale/s32g2.dtsi new file +0
-0[...]
Quoted 10 lines
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi new file +6
-0+ gic: interrupt-controller@50800000 { + compatible = "arm,gic-v3"; + #interrupt-cells = <3>; + interrupt-controller; + reg = <0 0x50800000 0 0x10000>, + <0 0x50880000 0 0x200000>,That's enough redistributor space for 16 CPUs. However, you only describe 4. Either the number of CPUs is wrong, the size is wrong, or the GIC has been configured for more cores than the SoC has.
Confirmed the SoC can only find 4 redistributors:
localhost:~ # dmesg | grep CPU
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=480 to nr_cpu_ids=4. [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000050880000 [ 0.063865] smp: Bringing up secondary CPUs ... [ 0.068852] Detected VIPT I-cache on CPU1 [ 0.068894] GICv3: CPU1: found redistributor 1 region 0:0x00000000508a0000 [ 0.068963] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.069809] Detected VIPT I-cache on CPU2 [ 0.069851] GICv3: CPU2: found redistributor 100 region 0:0x00000000508c0000 [ 0.069903] CPU2: Booted secondary processor 0x0000000100 [0x410fd034] [ 0.070698] Detected VIPT I-cache on CPU3 [ 0.070722] GICv3: CPU3: found redistributor 101 region 0:0x00000000508e0000 [ 0.070749] CPU3: Booted secondary processor 0x0000000101 [0x410fd034] [ 0.070847] smp: Brought up 1 node, 4 CPUsQuoted 1 line
<..snip..>
That's not the correct way to find out. Each CPU tries to find its matching RD in the region. This doesn't mean there aren't more RDs present in the GIC.
Quoted 7 lines
You need to iterate over all the RDs in the region until you find one that has GICR_TYPER.Last == 1. This will give you the actual count. Alternatively, you can check whether the RD at
508e0000has that bit set. If it doesn't, then you know there are more RDs than CPUs.M.
Thanks for your guidance. Not sure if any debug log can be enabled for this check so I temporarily add an ugly message as below:
drivers/irqchip/irq-gic-v3.c +3 -2
@@ -866,10 +866,11 @@ static int __gic_populate_rdist(struct redist_region *region, void __iomem *ptr)gic_data_rdist_rd_base () = ptr;gic_data_rdist ()->phys_base = region->phys_base + offset; -pr_info ("CPU%d: found redistributor %lx region %d:%pa\n" , +pr_info ("CPU%d: found redistributor %lx region %d:%pa last: %d\n" ,smp_processor_id (), mpidr, (int )(region - gic_data.redist_regions), - &gic_data_rdist ()->phys_base); + &gic_data_rdist ()->phys_base, + (typer &GICR_TYPER_LAST ) ?1 :0 );return 0 ; }
The following log shows that the "Last" bit (GICR_TYPER[4]) of RD at 508e0000 has been set.
localhost:~ # dmesg | grep GIC
[ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] GICv3: 544 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000050880000 last: 0 [ 0.078745] GICv3: CPU1: found redistributor 1 region 0:0x00000000508a0000 last: 0 [ 0.089598] GICv3: CPU2: found redistributor 100 region 0:0x00000000508c0000 last: 0 [ 0.100395] GICv3: CPU3: found redistributor 101 region 0:0x00000000508e0000 last: 1
Marc Zyngier
maintainerRe: [PATCH 4/8] arm64: dts: add NXP S32G2 support
Quoted 5 lines · Chester Lin
The following log shows that the "Last" bit (GICR_TYPER[4]) of RD at
508e0000has been set.localhost:~ # dmesg | grep GIC
Quoted 9 lines
[ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] GICv3: 544 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000050880000 last: 0 [ 0.078745] GICv3: CPU1: found redistributor 1 region 0:0x00000000508a0000 last: 0 [ 0.089598] GICv3: CPU2: found redistributor 100 region 0:0x00000000508c0000 last: 0 [ 0.100395] GICv3: CPU3: found redistributor 101 region 0:0x00000000508e0000 last: 1
Looks convincing enough. Trimming the RD range to 512kB is then the right thing to do.
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
PATCH 5/8 arm64: dts: s32g2: add serial/uart support
In reply to Chester LinAdd serial/uart support for NXP S32G2.
--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 31 ++++++++++++++++++++++++ 1 file changed, 31 insertions(+)
arch/arm64/boot/dts/freescale/s32g2.dtsi +31 -0
@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2017-2020 NXP */ #include <dt-bindings/interrupt-controller/arm-gic.h>
@@ -11,6 +12,12 @@ / { #address-cells = <2>; #size-cells = <2>; + aliases { + serial0 = &uart0; + serial1 = &uart1; + serial2 = &uart2; + }; + cpus { #address-cells = <1>; #size-cells = <0>;
@@ -82,6 +89,30 @@ soc { ranges; + uart0: serial@401c8000 { + compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <0 0x401c8000 0 0x3000>; + interrupts = <GIC_SPI 82 IRQ_TYPE_EDGE_RISING>; + status = "disabled"; + }; + + uart1: serial@401cc000 { + compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <0 0x401cc000 0 0x3000>; + interrupts = <GIC_SPI 83 IRQ_TYPE_EDGE_RISING>; + status = "disabled"; + }; + + uart2: serial@402bc000 { + compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <0 0x402bc000 0 0x3000>; + interrupts = <GIC_SPI 84 IRQ_TYPE_EDGE_RISING>; + status = "disabled"; + }; + gic: interrupt-controller@50800000 { compatible = "arm,gic-v3"; #interrupt-cells = <3>;
Signature · 1 line
2.30.0
Re: [PATCH 5/8] arm64: dts: s32g2: add serial/uart support
Hi Chester et al.,
Quoted 1 line · Chester Lin
Add serial/uart support for NXP S32G2.
You might mention here that (following our initial stub) this commit is now apparently based on the CodeAurora BSP branch foo (and therefore adding its last-year copyright below and separate from 4/8).
Quoted 1 line
@NXP: If there are downstream Signed-off-bys that you would like to see included for this portion here, please speak up.
Quoted 10 lines
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g2.dtsi | 31 ++++++++++++++++++++++++ 1 file changed, 31 insertions(+)arch/arm64/boot/dts/freescale/s32g2.dtsi +0
-0
arch/arm64/boot/dts/freescale/s32g2.dtsi line 4
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi +1
-0@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2017-2020 NXP
@NXP: Should this be updated to include 2021 from your latest BSP releases? Do you want it visually aligned by adding the ASCII-art?
arch/arm64/boot/dts/freescale/s32g2.dtsi / { · line 19
Quoted 12 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi +5
-0*/ #include <dt-bindings/interrupt-controller/arm-gic.h>@@ -11,6 +12,12 @@ / { #address-cells = <2>; #size-cells = <2>; + aliases { + serial0 = &uart0; + serial1 = &uart1; + serial2 = &uart2; + };
Note: In the past there had been controversies as to whether to define aliases globally for a SoC or in a .dts specific to a board's usage. In this case it does not seem to matter much, as uart0 is being used as console on the reference boards.
Quoted 25 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi +18
-0+ cpus { #address-cells = <1>; #size-cells = <0>;@@ -82,6 +89,30 @@ soc { ranges; + uart0: serial@401c8000 { + compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <0 0x401c8000 0 0x3000>; + interrupts = <GIC_SPI 82 IRQ_TYPE_EDGE_RISING>; + status = "disabled"; + }; + + uart1: serial@401cc000 { + compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <0 0x401cc000 0 0x3000>; + interrupts = <GIC_SPI 83 IRQ_TYPE_EDGE_RISING>; + status = "disabled"; + }; + + uart2: serial@402bc000 {
arch/arm64/boot/dts/freescale/s32g2.dtsi soc { · line 118
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi +7
-0+ compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <0 0x402bc000 0 0x3000>; + interrupts = <GIC_SPI 84 IRQ_TYPE_EDGE_RISING>; + status = "disabled"; + }; + gic: interrupt-controller@50800000 { compatible = "arm,gic-v3"; #interrupt-cells = <3>;
Regards,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 5/8] arm64: dts: s32g2: add serial/uart support
Hi Andreas
Quoted 12 lines · Andreas Färber
Hi Chester et al.,
Quoted 1 line · Chester Lin
Add serial/uart support for NXP S32G2.
You might mention here that (following our initial stub) this commit is
now apparently based on the CodeAurora BSP branch foo (and therefore adding its last-year copyright below and separate from 4/8).Quoted 1 line
Quoted 3 lines
@NXP: If there are downstream Signed-off-bys that you would like to see
included for this portion here, please speak up.
Larisa signed-off should be added.
Quoted 7 lines
Quoted 7 lines
Signed-off-by Chester Lin <[email protected]>---
arch/arm64/boot/dts/freescale/s32g2.dtsi | 31
++++++++++++++++++++++++1 file changed, 31 insertions(+)
Quoted 13 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi line 4
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi +1
-0@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2017-2020 NXP@NXP: Should this be updated to include 2021 from your latest BSP releases? Do you want it visually aligned by adding the ASCII-art?
Yes for both questions. The copyright year sould be updated to 2021 and should be visually aligned.
Quoted 63 lines
Quoted 7 lines
arch/arm64/boot/dts/freescale/s32g2.dtsi +0
-0*/
#include <dt-bindings/interrupt-controller/arm-gic.h>arch/arm64/boot/dts/freescale/s32g2.dtsi +0
-0@@ -11,6 +12,12 @@ / { #address-cells = <2>; #size-cells = <2>;Quoted 6 lines
+ aliases {
+ serial0 = &uart0;
+ serial1 = &uart1;
+ serial2 = &uart2;
+ };Note: In the past there had been controversies as to whether to define
aliases globally for a SoC or in a .dts specific to a board's usage. In this case it does not seem to matter much, as uart0 is being used as
console on the reference boards.Quoted 30 lines
+
cpus {
#address-cells = <1>;
#size-cells = <0>;arch/arm64/boot/dts/freescale/s32g2.dtsi +0
-0@@ -82,6 +89,30 @@ soc {
ranges;
+ uart0: serial@401c8000 {
+ compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <00x401c800000x3000>; + interrupts = <GIC_SPI82IRQ_TYPE_EDGE_RISING>;
+ status = "disabled";
+ };
+
+ uart1: serial@401cc000 {
+ compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <00x401cc00000x3000>; + interrupts = <GIC_SPI83IRQ_TYPE_EDGE_RISING>;
+ status = "disabled";
+ };
+
+ uart2: serial@402bc000 {
+ compatible = "fsl,s32g2-linflexuart", + "fsl,s32v234-linflexuart"; + reg = <00x402bc00000x3000>;Quoted 8 lines
+ interrupts = <
GIC_SPI84IRQ_TYPE_EDGE_RISING>;
+ status = "disabled"; + };
+
gic: interrupt-controller@50800000 { compatible = "arm,gic-v3"; #interrupt-cells = <3>;Regards,
Andreas
PATCH 6/8 arm64: dts: s32g2: add VNP-EVB and VNP-RDB2 support
In reply to Chester LinAdd initial device-trees of NXP S32G2's Evaluation Board (S32G-VNP-EVB) and Reference Design 2 Board (S32G-VNP-RDB2).
--- arch/arm64/boot/dts/freescale/Makefile | 2 ++ .../arm64/boot/dts/freescale/s32g274a-evb.dts | 21 ++++++++++++++++ .../boot/dts/freescale/s32g274a-rdb2.dts | 25 +++++++++++++++++++ 3 files changed, 48 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-evb.dts create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts
arch/arm64/boot/dts/freescale/Makefile +2 -0
@@ -67,4 +67,6 @@ dtb-$(CONFIG_ARCH_MXC) += imx8qxp-ai_ml.dtb dtb-$(CONFIG_ARCH_MXC) += imx8qxp-colibri-eval-v3.dtb dtb-$(CONFIG_ARCH_MXC) += imx8qxp-mek.dtb +dtb-$(CONFIG_ARCH_S32) += s32g274a-evb.dtb +dtb-$(CONFIG_ARCH_S32) += s32g274a-rdb2.dtb dtb-$(CONFIG_ARCH_S32) += s32v234-evb.dtb
arch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +21 -0
@@ -0,0 +1,21 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/* + * Copyright (c) 2021 SUSE LLC + */ + +/dts-v1/; + +#include "s32g2.dtsi" + +/ { + model = "NXP S32G2 Evaluation Board (S32G-VNP-EVB)"; + compatible = "fsl,s32g274a-evb", "fsl,s32g2"; + + chosen { + stdout-path = "serial0:115200n8"; + }; +}; + +&uart0 { + status = "okay"; +};
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +25 -0
@@ -0,0 +1,25 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/* + * Copyright (c) 2021 SUSE LLC + */ + +/dts-v1/; + +#include "s32g2.dtsi" + +/ { + model = "NXP S32G2 Reference Design 2 (S32G-VNP-RDB2)"; + compatible = "fsl,s32g274a-rdb2", "fsl,s32g2"; + + chosen { + stdout-path = "serial0:115200n8"; + }; +}; + +&uart0 { + status = "okay"; +}; + +&uart1 { + status = "okay"; +};
Signature · 1 line
2.30.0
Re: [PATCH 6/8] arm64: dts: s32g2: add VNP-EVB and VNP-RDB2 support
Hi Chester et al.,
Quoted 2 lines · Chester Lin
Add initial device-trees of NXP S32G2's Evaluation Board (S32G-VNP-EVB) and Reference Design 2 Board (S32G-VNP-RDB2).
"Reference Design Board 2"?
Quoted 15 lines
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/Makefile | 2 ++ .../arm64/boot/dts/freescale/s32g274a-evb.dts | 21 ++++++++++++++++ .../boot/dts/freescale/s32g274a-rdb2.dts | 25 +++++++++++++++++++ 3 files changed, 48 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-evb.dts create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-rdb2.dtsarch/arm64/boot/dts/freescale/Makefile +0
-0
arch/arm64/boot/dts/freescale/Makefile dtb-$(CONFIG_ARCH_MXC) += imx8qxp-ai_ml.dtb · line 71
Quoted 5 lines
arch/arm64/boot/dts/freescale/Makefile +2
-0@@ -67,4 +67,6 @@ dtb-$(CONFIG_ARCH_MXC) += imx8qxp-ai_ml.dtb dtb-$(CONFIG_ARCH_MXC) += imx8qxp-colibri-eval-v3.dtb dtb-$(CONFIG_ARCH_MXC) += imx8qxp-mek.dtb +dtb-$(CONFIG_ARCH_S32) += s32g274a-evb.dtb +dtb-$(CONFIG_ARCH_S32) += s32g274a-rdb2.dtb
@NXP: Note that since there's no distinction between S32V and S32G on the Kconfig level, we decided not to add a white line here. If you wish to visually separate them, that could be changed.
For reference:
speaks about S32 (without V), so did not need to get updated for S32G2.
Quoted 15 lines
arch/arm64/boot/dts/freescale/Makefile +0
-0dtb-$(CONFIG_ARCH_S32) += s32v234-evb.dtbarch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +8
-0@@ -0,0 +1,21 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/* + * Copyright (c) 2021 SUSE LLC + */ + +/dts-v1/; + +#include "s32g2.dtsi"
arch/arm64/boot/dts/freescale/s32g274a-evb.dts line 18
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +10
-0+ +/ { + model = "NXP S32G2 Evaluation Board (S32G-VNP-EVB)"; + compatible = "fsl,s32g274a-evb", "fsl,s32g2"; + + chosen { + stdout-path = "serial0:115200n8"; + }; +}; +
Is there any marking on the PCB that a /* ... */ comment could reference here? Right now uart0 is close to stdout-path above, but that will change once more device nodes get added and enabled alphabetically.
arch/arm64/boot/dts/freescale/s32g274a-evb.dts line 20
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +2
-0+&uart0 { + status = "okay";
No clock-frequency or clocks property needed?
Quoted 8 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +1
-0+};arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +1
-0@@ -0,0 +1,25 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 11
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +10
-0+/* + * Copyright (c) 2021 SUSE LLC + */ + +/dts-v1/; + +#include "s32g2.dtsi" + +/ { + model = "NXP S32G2 Reference Design 2 (S32G-VNP-RDB2)";
"Board" missing.
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 18
Quoted 7 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +7
-0+ compatible = "fsl,s32g274a-rdb2", "fsl,s32g2"; + + chosen { + stdout-path = "serial0:115200n8"; + }; +}; +
Comment please.
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 20
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +2
-0+&uart0 { + status = "okay";
No clock-frequency or clocks property needed?
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 25
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +5
-0+}; + +&uart1 { + status = "okay"; +};
What is uart1? Please add a comment. Does it actually work without clocks property?
Thanks,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 6/8] arm64: dts: s32g2: add VNP-EVB and VNP-RDB2 support
Quoted 7 lines · Andreas Färber
Hi Chester et al.,
Quoted 2 lines · Chester Lin
Add initial device-trees of NXP S32G2's Evaluation Board (S32G-VNP-EVB) and Reference Design 2 Board (S32G-VNP-RDB2).
"Reference Design Board 2"?
It looks better. Will fix it.
Quoted 53 lines
Quoted 16 lines
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/Makefile | 2 ++ .../arm64/boot/dts/freescale/s32g274a-evb.dts | 21 ++++++++++++++++ .../boot/dts/freescale/s32g274a-rdb2.dts | 25 +++++++++++++++++++ 3 files changed, 48 insertions(+) create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-evb.dts create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-rdb2.dtsarch/arm64/boot/dts/freescale/Makefile +0
-0arch/arm64/boot/dts/freescale/Makefile dtb-$(CONFIG_ARCH_MXC) += imx8qxp-ai_ml.dtb · line 71
Quoted 5 lines
arch/arm64/boot/dts/freescale/Makefile +2
-0@@ -67,4 +67,6 @@ dtb-$(CONFIG_ARCH_MXC) += imx8qxp-ai_ml.dtb dtb-$(CONFIG_ARCH_MXC) += imx8qxp-colibri-eval-v3.dtb dtb-$(CONFIG_ARCH_MXC) += imx8qxp-mek.dtb +dtb-$(CONFIG_ARCH_S32) += s32g274a-evb.dtb +dtb-$(CONFIG_ARCH_S32) += s32g274a-rdb2.dtb@NXP: Note that since there's no distinction between S32V and S32G on the
Kconfiglevel, we decided not to add a white line here. If you wish to visually separate them, that could be changed.For reference:
speaks about S32 (without V), so did not need to get updated for S32G2.
Quoted 21 lines
arch/arm64/boot/dts/freescale/Makefile +0
-0dtb-$(CONFIG_ARCH_S32) += s32v234-evb.dtbarch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +14
-0@@ -0,0 +1,21 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/* + * Copyright (c) 2021 SUSE LLC + */ + +/dts-v1/; + +#include "s32g2.dtsi" + +/ { + model = "NXP S32G2 Evaluation Board (S32G-VNP-EVB)"; + compatible = "fsl,s32g274a-evb", "fsl,s32g2"; + + chosen {
Quoted 9 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts line 18
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +4
-0+ stdout-path = "serial0:115200n8"; + }; +}; +Is there any marking on the PCB that a /* ... */ comment could reference here? Right now uart0 is close to stdout-path above, but that will change once more device nodes get added and enabled alphabetically.
Yes, it's marked as "UART J58". Will add it in v2.
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts line 20
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +2
-0+&uart0 { + status = "okay";No clock-frequency or clocks property needed?
As a minimum support patch, it can still reply on TF-A's clock settings so no clock property is required at the moment.
Quoted 12 lines
Quoted 12 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts new file +1
-0+};arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +5
-0@@ -0,0 +1,25 @@ +// SPDX-License-Identifier: GPL-2.0-or-later OR MIT +/* + * Copyright (c) 2021 SUSE LLC + */ +
Quoted 8 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 11
Quoted 6 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +6
-0+/dts-v1/; + +#include "s32g2.dtsi" + +/ { + model = "NXP S32G2 Reference Design 2 (S32G-VNP-RDB2)";"Board" missing.
This model name is based on what I can find on the official main page of RDB2, which is shorter without having an additional "Board" string:
But having a "Board" looks good to me as well.
Quoted 11 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 18
Quoted 8 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +7
-0+ compatible = "fsl,s32g274a-rdb2", "fsl,s32g2"; + + chosen { + stdout-path = "serial0:115200n8"; + }; +}; +Comment please.
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 20
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +2
-0+&uart0 { + status = "okay";No clock-frequency or clocks property needed?
Same as what I have explained in the evb dts.
Quoted 9 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 25
Quoted 5 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts new file +5
-0+}; + +&uart1 { + status = "okay"; +};What is uart1? Please add a comment. Does it actually work without clocks property?
RDB2 has an additional serial port [uart1] on the board. Please see:
https://www.nxp.com/document/guide/get-started-with-the-s32g-reference-design-board-2-for-vehicle-network-processing:GS-S32G-VNP-RDB2
It's the same as the uart0, the uart1 is also driven by the same set of clks [S32GEN1_CLK_LINFLEXD, S32GEN1_CLK_LIN_BAUD] according to the downstream TF-A:
https://source.codeaurora.org/external/autobsps32/arm-trusted-firmware/tree/drivers/nxp/s32g/clk/s32gen1_scmi_ids.c?h=release/bsp29.0-2.3#n44
Quoted 9 lines
Thanks,
AndreasSignature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
PATCH 7/8 arm64: dts: s32g2: add memory nodes for evb and rdb2
In reply to Chester LinAdd memory nodes for S32G-VNP-EVB and S32G-VNP-RDB2 since they have fixed RAM size.
--- arch/arm64/boot/dts/freescale/s32g274a-evb.dts | 8 ++++++++ arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts | 8 ++++++++ 2 files changed, 16 insertions(+)
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +8 -0
@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2019-2020 NXP */ /dts-v1/;
@@ -14,6 +15,13 @@ / { chosen { stdout-path = "serial0:115200n8"; }; + + memory@80000000 { + device_type = "memory"; + /* 4GB RAM */ + reg = <0 0x80000000 0 0x80000000>, + <8 0x80000000 0 0x80000000>; + }; }; &uart0 {
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +8 -0
@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2019-2020 NXP */ /dts-v1/;
@@ -14,6 +15,13 @@ / { chosen { stdout-path = "serial0:115200n8"; }; + + memory@80000000 { + device_type = "memory"; + /* 4GB RAM */ + reg = <0 0x80000000 0 0x80000000>, + <8 0x80000000 0 0x80000000>; + }; }; &uart0 {
Signature · 1 line
2.30.0
Re: [PATCH 7/8] arm64: dts: s32g2: add memory nodes for evb and rdb2
Hi Chester et al.,
Quoted 2 lines · Chester Lin
Add memory nodes for S32G-VNP-EVB and S32G-VNP-RDB2 since they have fixed RAM size.
You can drop "since they have fixed RAM size" - if they didn't, you would simply choose the lowest size and rely on the bootloader (U-Boot) to overwrite it with the actually detected size.
Please expand why this patch is separate - BSP based, I assume?
Quoted 12 lines
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g274a-evb.dts | 8 ++++++++ arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts | 8 ++++++++ 2 files changed, 16 insertions(+)arch/arm64/boot/dts/freescale/s32g274a-evb.dts +0
-0
arch/arm64/boot/dts/freescale/s32g274a-evb.dts line 4
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +1
-0@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2019-2020 NXP
@NXP: Please review year, alignment. Do any Signed-off-bys apply?
arch/arm64/boot/dts/freescale/s32g274a-evb.dts / { · line 21
Quoted 11 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +4
-0*/ /dts-v1/;@@ -14,6 +15,13 @@ / { chosen { stdout-path = "serial0:115200n8"; }; + + memory@80000000 { + device_type = "memory"; + /* 4GB RAM */
This looks strange to me - either put /* 4 GiB RAM */ before the node, three lines above, and/or append comment /* 2 GiB */ on each line below. Note the space, and suggest to be precise about factor 1024 vs. 1000.
arch/arm64/boot/dts/freescale/s32g274a-evb.dts / { · line 22
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +1
-0+ reg = <0 0x80000000 0 0x80000000>,
Note that this gives you the range to use for the .dtsi /soc node:
Address 0x0 with size 0x80000000 gets mapped to 0x0 0x0, excluding the upper 0x80000000 for the RAM here. Or address 0x0 0x0 for two /soc cells if there are high-memory peripherals.
arch/arm64/boot/dts/freescale/s32g274a-evb.dts / { · line 23
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +1
-0+ <8 0x80000000 0 0x80000000>;
Maybe use 0x8 here and 0x0 above? (second 0 stays same, so don't mind)
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 4
Quoted 13 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +1
-0+ }; }; &uart0 {arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +1
-0@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2019-2020 NXP
@NXP: 2021?
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +0
-0*/ /dts-v1/;
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts / { · line 24
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +7
-0@@ -14,6 +15,13 @@ / { chosen { stdout-path = "serial0:115200n8"; }; + + memory@80000000 { + device_type = "memory"; + /* 4GB RAM */ + reg = <0 0x80000000 0 0x80000000>, + <8 0x80000000 0 0x80000000>; + };
Same comments as for EVB.
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts / { · line 27
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +0
-0}; &uart0 {
Regards,
Andreas
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 7/8] arm64: dts: s32g2: add memory nodes for evb and rdb2
Quoted 12 lines · Andreas Färber
Hi Chester et al.,
Quoted 2 lines · Chester Lin
Add memory nodes for S32G-VNP-EVB and S32G-VNP-RDB2 since they have fixed RAM size.
You can drop "since they have fixed RAM size" - if they didn't, you would simply choose the lowest size and rely on the bootloader (U-Boot) to overwrite it with the actually detected size.
Please expand why this patch is separate - BSP based, I assume?
Yes, the information of memory banks is from s32 downstream kernel, which is listed in the board DTs of older releases [bsp27] although newer releases [bsp28 & bsp29] have moved it into s32 downstream u-boot as runtime fdt-fixup. I think we should still reveal this information in kernel DTs in order to have better understanding of system memory ranges that each board can have.
@NXP: Please don't hesitate to let me know if any better idea, thanks!
Quoted 21 lines
Quoted 12 lines
Signed-off-by Chester Lin <[email protected]>--- arch/arm64/boot/dts/freescale/s32g274a-evb.dts | 8 ++++++++ arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts | 8 ++++++++ 2 files changed, 16 insertions(+)arch/arm64/boot/dts/freescale/s32g274a-evb.dts +0
-0arch/arm64/boot/dts/freescale/s32g274a-evb.dts line 4
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +1
-0@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2019-2020 NXP@NXP: Please review year, alignment. Do any Signed-off-bys apply?
Quoted 2 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +0
-0*/
Quoted 14 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts / { · line 21
Quoted 9 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +4
-0/dts-v1/;@@ -14,6 +15,13 @@ / { chosen { stdout-path = "serial0:115200n8"; }; + + memory@80000000 { + device_type = "memory"; + /* 4GB RAM */This looks strange to me - either put /* 4 GiB RAM */ before the node, three lines above, and/or append comment /* 2 GiB */ on each line below. Note the space, and suggest to be precise about factor 1024 vs. 1000.
Thank you for the suggestion.
Quoted 7 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts / { · line 22
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +1
-0+ reg = <0 0x80000000 0 0x80000000>,Note that this gives you the range to use for the .dtsi /soc node:
Address0x0with size0x80000000gets mapped to0x00x0, excluding the upper0x80000000for the RAM here. Or address0x00x0for two /soc cells if there are high-memory peripherals.
I don't know if memory ranges might be changed for new boards or CPU revisions in the future, which means the first memory range might be expanded as well [e.g. 0~4GB]. Based this assumption, I think the size should also be changed accordingly. Not sure if overlays can still work with this case but overwriting all reg properties under /soc could be awful.
However if we only have to think of current hardware spec, it's good to declare "range = <0 0 0 0x80000000>".
Please feel free to let me know if any suggestions, thanks.
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts / { · line 23
Quoted 1 line
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +1
-0+ <8 0x80000000 0 0x80000000>;Maybe use
0x8here and0x0above? (second 0 stays same, so don't mind)
Will fix it.
Quoted 46 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts line 4
Quoted 13 lines
arch/arm64/boot/dts/freescale/s32g274a-evb.dts +1
-0+ }; }; &uart0 {arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +1
-0@@ -1,6 +1,7 @@ // SPDX-License-Identifier: GPL-2.0-or-later OR MIT /* * Copyright (c) 2021 SUSE LLC + * Copyright 2019-2020 NXP@NXP: 2021?
Quoted 4 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +0
-0*/ /dts-v1/;arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts / { · line 24
Quoted 10 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +7
-0@@ -14,6 +15,13 @@ / { chosen { stdout-path = "serial0:115200n8"; }; + + memory@80000000 { + device_type = "memory"; + /* 4GB RAM */ + reg = <0 0x80000000 0 0x80000000>, + <8 0x80000000 0 0x80000000>; + };Same comments as for EVB.
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts / { · line 27
Quoted 3 lines
arch/arm64/boot/dts/freescale/s32g274a-rdb2.dts +0
-0}; &uart0 {Regards,
AndreasSignature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
PATCH 8/8 MAINTAINERS: Add an entry for NXP S32G2 boards
In reply to Chester LinAdd a new entry for the maintenance of NXP S32G2 DT files.
--- MAINTAINERS | 6 ++++++ 1 file changed, 6 insertions(+)
MAINTAINERS +6 -0
@@ -2281,6 +2281,12 @@ F: arch/arm/boot/dts/nuvoton-wpcm450* F: arch/arm/mach-npcm/wpcm450.c F: drivers/*/*wpcm* +ARM/NXP S32G2 ARCHITECTURE +M: Chester Lin <[email protected]> +L: [email protected] (moderated for non-subscribers) +S: Maintained +F: arch/arm64/boot/dts/freescale/s32g2* + ARM/OPENMOKO NEO FREERUNNER (GTA02) MACHINE SUPPORT L: [email protected] (subscribers-only) S: Orphan
Signature · 1 line
2.30.0
Re: [PATCH 8/8] MAINTAINERS: Add an entry for NXP S32G2 boards
Quoted 12 lines · Chester Lin
Add a new entry for the maintenance of NXP S32G2 DT files.
Signed-off-by Chester Lin <[email protected]>--- MAINTAINERS | 6 ++++++ 1 file changed, 6 insertions(+)MAINTAINERS +0
-0
MAINTAINERS F: arch/arm/boot/dts/nuvoton-wpcm450* · line 2288
Quoted 8 lines
MAINTAINERS +5
-0@@ -2281,6 +2281,12 @@ F: arch/arm/boot/dts/nuvoton-wpcm450* F: arch/arm/mach-npcm/wpcm450.c F: drivers/*/*wpcm* +ARM/NXP S32G2 ARCHITECTURE +M: Chester Lin <[email protected]> +L: [email protected] (moderated for non-subscribers) +S: Maintained +F: arch/arm64/boot/dts/freescale/s32g2*
I support the idea of sub-sub-architecture maintainers but I think idea of in-file addresses was preferred:
https://lore.kernel.org/lkml/[email protected]/
Best regards,
Krzysztof
Re: [PATCH 8/8] MAINTAINERS: Add an entry for NXP S32G2 boards
Quoted 16 lines · Krzysztof Kozlowski
Quoted 15 lines · Chester Lin
Add a new entry for the maintenance of NXP S32G2 DT files.
Signed-off-by Chester Lin <[email protected]>--- MAINTAINERS | 6 ++++++ 1 file changed, 6 insertions(+)MAINTAINERS +0
-0@@ -2281,6 +2281,12 @@ F: arch/arm/boot/dts/nuvoton-wpcm450* F: arch/arm/mach-npcm/wpcm450.c F: drivers/*/*wpcm*
Quoted 9 lines
MAINTAINERS F: arch/arm/boot/dts/nuvoton-wpcm450* · line 2288
Quoted 5 lines
MAINTAINERS +5
-0+ARM/NXP S32G2 ARCHITECTURE +M: Chester Lin <[email protected]> +L: [email protected] (moderated for non-subscribers) +S: Maintained +F: arch/arm64/boot/dts/freescale/s32g2*I support the idea of sub-sub-architecture maintainers but I think idea of in-file addresses was preferred:
https://lore.kernel.org/lkml/[email protected]/
Thanks for reminding that the patch didn't land. I just resent it with your Reviewed-by tag added. Thanks!
Shawn
Re: [PATCH 8/8] MAINTAINERS: Add an entry for NXP S32G2 boards
Hello Shawn and Krzysztof,
Quoted 17 lines · Shawn Guo
Quoted 16 lines · Krzysztof Kozlowski
Quoted 15 lines · Chester Lin
Add a new entry for the maintenance of NXP S32G2 DT files.
Signed-off-by Chester Lin <[email protected]>--- MAINTAINERS | 6 ++++++ 1 file changed, 6 insertions(+)MAINTAINERS +0
-0@@ -2281,6 +2281,12 @@ F: arch/arm/boot/dts/nuvoton-wpcm450* F: arch/arm/mach-npcm/wpcm450.c F: drivers/*/*wpcm*
Quoted 1 line
Quoted 1 line
MAINTAINERS F: arch/arm/boot/dts/nuvoton-wpcm450* · line 2284
Quoted 1 line
MAINTAINERS +1
-0+ARM/NXP S32G2 ARCHITECTURE
Suggestion from NXP is to use the broader S32G name.
Quoted 8 lines
Quoted 8 lines
MAINTAINERS F: arch/arm/boot/dts/nuvoton-wpcm450* · line 2288
Quoted 4 lines
MAINTAINERS +4
-0+M: Chester Lin <[email protected]> +L: [email protected] (moderated for non-subscribers) +S: Maintained +F: arch/arm64/boot/dts/freescale/s32g2*I support the idea of sub-sub-architecture maintainers but I think idea of in-file addresses was preferred:
https://lore.kernel.org/lkml/[email protected]/
I had specifically asked Chester to add a MAINTAINERS section.
Is your apparent suggestion of not accepting this MAINTAINERS patch based on the assumption that we're dealing with only one email address in three files? What do you see as the threshold to warrant a section?
From my point of view, above MAINTAINERS entry is incomplete, as we should CC the full team working on S32G for patch review, not just Chester himself.
So that would in my mind have been additional R: and L: entries in that MAINTAINERS section.
Quoted 2 lines
Thanks for reminding that the patch didn't land. I just resent it with your Reviewed-by tag added. Thanks!
Your above patch does not make clear to me what syntax we should use for adding email addresses to .dts[i] files now:
https://lore.kernel.org/lkml/20210809081033.GQ30984@dragon/
Especially when not dealing with file authors.
I get the impression it is not a replacement for an F: wildcard used in MAINTAINERS, but rather a complement?
Please understand that this is not about a single .dts file, as your patch suggests, but about a complete SoC family consisting of s32g*.dts* as well as in the future drivers specific to this platform. It seems way easier to specify the list of maintainers/reviewers in MAINTAINERS once with suitable wildcard paths, than copying them into each and every .dtsi and .dts file and driver .c/.h and later needing to sync multiple places. If a bot or user has fixes or cleanups for the S32G code, we want to know about it, so that NXP can consider it for their BSP branches and SUSE for our SLE branches, and obviously for follow-up patch series that are already in the works and waiting on this one.
Once merged, I would expect Chester or someone from NXP to set up an S32G tree on kernel.org that gets integrated into linux-next and sends pull requests to the SoC tree maintainers without bothering i.MX and Layerscape maintainers. Did you handle that differently for S32V?
Thanks,
Andreas
P.S. Have you checked or considered whether your script change might start to CC non-existing email addresses, since we wouldn't be allowed to remove them from copyright or authorship statements to prevent that?
Signature · 4 lines
SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer HRB 36809 (AG Nürnberg)
Re: [PATCH 8/8] MAINTAINERS: Add an entry for NXP S32G2 boards
Quoted 39 lines · Andreas Färber
Hello Shawn and Krzysztof,
Quoted 17 lines · Shawn Guo
Quoted 16 lines · Krzysztof Kozlowski
Quoted 15 lines · Chester Lin
Add a new entry for the maintenance of NXP S32G2 DT files.
Signed-off-by Chester Lin <[email protected]>--- MAINTAINERS | 6 ++++++ 1 file changed, 6 insertions(+)MAINTAINERS +0
-0@@ -2281,6 +2281,12 @@ F: arch/arm/boot/dts/nuvoton-wpcm450* F: arch/arm/mach-npcm/wpcm450.c F: drivers/*/*wpcm*Quoted 1 line
Quoted 1 line
MAINTAINERS F: arch/arm/boot/dts/nuvoton-wpcm450* · line 2284
Quoted 1 line
MAINTAINERS +1
-0+ARM/NXP S32G2 ARCHITECTURESuggestion from NXP is to use the broader S32G name.
Quoted 8 lines
Quoted 8 lines
MAINTAINERS F: arch/arm/boot/dts/nuvoton-wpcm450* · line 2288
Quoted 4 lines
MAINTAINERS +4
-0+M: Chester Lin <[email protected]> +L: [email protected] (moderated for non-subscribers) +S: Maintained +F: arch/arm64/boot/dts/freescale/s32g2*I support the idea of sub-sub-architecture maintainers but I think idea of in-file addresses was preferred:
https://lore.kernel.org/lkml/[email protected]/I had specifically asked Chester to add a
MAINTAINERSsection.Is your apparent suggestion of not accepting this
MAINTAINERSpatch based on the assumption that we're dealing with only one email address in three files? What do you see as the threshold to warrant a section?
Quoted 5 lines
From my point of view, above
MAINTAINERSentry is incomplete, as we should CC the full team working on S32G for patch review, not just Chester himself.
So that would in my mind have been additional R: and L: entries in thatMAINTAINERSsection.
I assumed this is a sub-sub-architecture (something coming from Layerscape or i.MX) but it seems it's not, therefore I don't mind having separate entry in MAINTAINERS. The idea of in-file maintainers was for specific boards and SoCs belonging to existing sub-architectures.
I agree with your following reasons.
Quoted 30 lines
Quoted 3 lines
Thanks for reminding that the patch didn't land. I just resent it with your Reviewed-by tag added. Thanks!
Your above patch does not make clear to me what syntax we should use for adding email addresses to .dts[i] files now:
https://lore.kernel.org/lkml/20210809081033.GQ30984@dragon/
Especially when not dealing with file authors.
I get the impression it is not a replacement for an F: wildcard used in
MAINTAINERS, but rather a complement?Please understand that this is not about a single .dts file, as your patch suggests, but about a complete SoC family consisting of s32g*.dts* as well as in the future drivers specific to this platform. It seems way easier to specify the list of maintainers/reviewers in
MAINTAINERSonce with suitable wildcard paths, than copying them into each and every .dtsi and .dts file and driver .c/.h and later needing to sync multiple places. If a bot or user has fixes or cleanups for the S32G code, we want to know about it, so that NXP can consider it for their BSP branches and SUSE for our SLE branches, and obviously for follow-up patch series that are already in the works and waiting on this one.Once merged, I would expect Chester or someone from NXP to set up an S32G tree on kernel.org that gets integrated into linux-next and sends pull requests to the SoC tree maintainers without bothering i.MX and Layerscape maintainers. Did you handle that differently for S32V?
Quoted 6 lines
Thanks,
Andreas
P.S. Have you checked or considered whether your script change might start to CC non-existing email addresses, since we wouldn't be allowed to remove them from copyright or authorship statements to prevent that?
The same can happen for DT bindings maintainers.
Best regards,
Krzysztof
Quoted 21 lines · Chester Lin
Hello,
Here I'd like to propose a patchset, which is initial upstream support for NXP S32G2. S32G is a processor family developed by NXP for automotive solutions, such as vehicle networking and automotive high-performance processing. This series focuses on S32G2, which is the latest generation we can find at the moment. As the first round to support S32G2, this patchset only enables basic components and interfaces the SoC must have while kernel booting, which aims to have minimum hardware enablement for these two boards, S32G-VNP-EVB and S32G-VNP-RDB2. The concepts of how these boards work are originated from the downstream kernel tree[1] developed by NXP, which provides lots of details about the SoC S32G274A and its integrated boards. This series has been verified with downstream ATF[2] & U-Boot[3] based on the ATF boot flow.
Thanks,
Chester[1] https://source.codeaurora.org/external/autobsps32/linux/
[2] https://source.codeaurora.org/external/autobsps32/arm-trusted-firmware/
[3] https://source.codeaurora.org/external/autobsps32/u-boot/
Quoted 8 lines
Chester Lin (8):
dt-bindings: arm: fsl: add NXP S32G2 boards
dt-bindings: serial: fsl-linflexuart: convert to json-schema format
dt-bindings: serial: fsl-linflexuart: Add compatible for S32G2
arm64: dts: add NXP S32G2 support
arm64: dts: s32g2: add serial/uart support
arm64: dts: s32g2: add VNP-EVB and VNP-RDB2 support
arm64: dts: s32g2: add memory nodes for evb and rdb2
The dts changes look good to me. I will pick up the series once bindings gets acked by Rob.
Shawn
Quoted 20 lines
MAINTAINERS: Add an entry for NXP S32G2 boards.../devicetree/bindings/arm/fsl.yaml | 7 + .../bindings/serial/fsl,s32-linflexuart.txt | 22 --- .../bindings/serial/fsl,s32-linflexuart.yaml | 66 +++++++++ MAINTAINERS | 6 + arch/arm64/boot/dts/freescale/Makefile | 2 + arch/arm64/boot/dts/freescale/s32g2.dtsi | 129 ++++++++++++++++++ .../arm64/boot/dts/freescale/s32g274a-evb.dts | 29 ++++ .../boot/dts/freescale/s32g274a-rdb2.dts | 33 +++++ 8 files changed, 272 insertions(+), 22 deletions(-) delete mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.txt create mode 100644 Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml create mode 100644 arch/arm64/boot/dts/freescale/s32g2.dtsi create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-evb.dts create mode 100644 arch/arm64/boot/dts/freescale/s32g274a-rdb2.dtsSignature · 1 line
2.30.0