From: Shawn Guo <shawnguo@kernel.org>
To: Chester Lin <clin@suse.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
s32@nxp.com, "Li Yang" <leoyang.li@nxp.com>,
"Andreas Färber" <afaerber@suse.de>,
"Matthias Brugger" <mbrugger@suse.com>,
"Radu Nicolae Pirea" <radu-nicolae.pirea@oss.nxp.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
"Krzysztof Kozlowski" <krzk@kernel.org>,
catalin-dan.udma@nxp.com, bogdan.hamciuc@nxp.com,
bogdan.folea@nxp.com, ciprianmarian.costea@nxp.com,
ghennadi.procopciuc@nxp.com, "Ivan T . Ivanov" <iivanov@suse.de>,
"Lee, Chun-Yi" <jlee@suse.com>
Subject: Re: [PATCH v2 0/8] arm64: dts: initial NXP S32G2 support
Date: Mon, 4 Oct 2021 16:11:37 +0800 [thread overview]
Message-ID: <20211004081136.GF15650@dragon> (raw)
In-Reply-To: <20210908064528.922-1-clin@suse.com>
On Wed, Sep 08, 2021 at 02:45:20PM +0800, Chester Lin wrote:
> 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/
>
> Changes in v2:
> - dt-bindings:
> - Rename the compatible vendor string to "nxp," for s32g2.
> - Drop the specific description "S32V234 SoC".
> - Fill my name in the maintainer field. I tried to contact the authors
> of fsl,s32-linflexuart.txt but got no response.
> - Remove redundant minItems/maxItems from compatible properties.
> - Remove the redundant example from fsl,s32-linflexuart.yaml.
> - dtsi/dts:
> - Add a SoC description in s32g2.dtsi.
> - Add an interrupt-affinity to the pmu node.
> - Move the psci node into the "/firmware" node.
> - Remove the redundant properties and white lines in DT.
> - Remove the wrong interrupt specifier from the gic node.
> - Specify the range and cell-size of /soc [0 - 4 GiB].
> - Correct the reserved size of GICR to 512Kbytes [0x80000].
> - Add new Signed-off-by to the DT uart patch.
> - Fix copyright strings.
> - Revise reg properties based on new cell-size.
> - Move the serial/uart aliases from the SoC .dtsi to board .dts files.
> - Correct the model string of RDB2.
> - Add comments for the uart markings on PCB.
> - Adjust RAM size comments of memory nodes.
> - Convert reg addresses of memory nodes into hex format.
> - MAINTAINERS
> - Add information of reviewers.
>
> 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 S32G boards
Applied all, thanks!
prev parent reply other threads:[~2021-10-04 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 6:45 [PATCH v2 0/8] arm64: dts: initial NXP S32G2 support Chester Lin
2021-09-08 6:45 ` [PATCH v2 1/8] dt-bindings: arm: fsl: add NXP S32G2 boards Chester Lin
2021-09-08 6:45 ` [PATCH v2 2/8] dt-bindings: serial: fsl-linflexuart: convert to json-schema format Chester Lin
2021-09-20 22:32 ` Rob Herring
2021-09-08 6:45 ` [PATCH v2 3/8] dt-bindings: serial: fsl-linflexuart: add compatible for S32G2 Chester Lin
2021-09-20 22:32 ` Rob Herring
2021-09-08 6:45 ` [PATCH v2 4/8] arm64: dts: add NXP S32G2 support Chester Lin
2021-09-08 6:45 ` [PATCH v2 5/8] arm64: dts: s32g2: add serial/uart support Chester Lin
2021-09-08 6:45 ` [PATCH v2 6/8] arm64: dts: s32g2: add VNP-EVB and VNP-RDB2 support Chester Lin
2021-09-08 6:45 ` [PATCH v2 7/8] arm64: dts: s32g2: add memory nodes for evb and rdb2 Chester Lin
2021-09-08 6:45 ` [PATCH v2 8/8] MAINTAINERS: add an entry for NXP S32G boards Chester Lin
2021-10-04 8:11 ` Shawn Guo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211004081136.GF15650@dragon \
--to=shawnguo@kernel.org \
--cc=afaerber@suse.de \
--cc=bogdan.folea@nxp.com \
--cc=bogdan.hamciuc@nxp.com \
--cc=catalin-dan.udma@nxp.com \
--cc=ciprianmarian.costea@nxp.com \
--cc=clin@suse.com \
--cc=devicetree@vger.kernel.org \
--cc=ghennadi.procopciuc@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=iivanov@suse.de \
--cc=jlee@suse.com \
--cc=krzk@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mbrugger@suse.com \
--cc=radu-nicolae.pirea@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s32@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).