From: Josua Mayer <josua@solid-run.com>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Josua Mayer <josua@solid-run.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Li Yang <leoyang.li@nxp.com>
Subject: [PATCH v5 0/4] arm64: dts: freescale: Add support for LX2162 SoM & Clearfog Board
Date: Fri, 18 Aug 2023 13:10:12 +0200 [thread overview]
Message-ID: <20230818111016.11271-1-josua@solid-run.com> (raw)
Add support for the SolidRun LX2162A System on Module (SoM), and the
Clearfog evaluation board.
This patch-set introduces:
- dt node for lx2160a serdes block #2
- dtsi for lx2162a system on module
- dts for lx2162 clearfog
Firstly Please note that checkpatch was complaining about the EEPROMS:
- DT compatible string "st,24c02" appears un-documented
- DT compatible string "st,24c2048" appears un-documented
- DT compatible string "atmel,24c2048" appears un-documented
However to my eyes these *are* already documented in at24.yaml,
and are also used in existing device-tree.
checkpatch is also complaining about various parts of lx2160a.dtsi,
as well as the use of "sfp" property in dpmac nodes - which are common
across layerscape based dts.
Secondly the MAINTAINERS file has not been modified.
Is it required I add myself or *someone* for these new dts?
Changes since v4:
- extended commit hash reference to 12 characters in description
Changes since v3:
- moved status properties to be last
- changed ethernet-phy on som from /delete-node/ to disabled,
Changes since v2:
- fixed property order in som dts such that compatible is first property
- added reviewed-by tags to bindings patches
Changes since v1:
- fixed DT binding changes to not break existing boards
- explained new board / som DT binding in commit message
- added missing DT binding for dpaa2 mac "phys" property
- reordered "compatible" and "reg" properties: first "compatible", then "reg"
- replaced chip-specific DT node names with generic ones
Josua Mayer (4):
arm64: dts: lx2160a: describe the SerDes block #2
dt-bindings: net: dpaa2 mac: add phys property
dt-bindings: arm: Add SolidRun LX2162A SoM & Clearfog Board
arm64: dts: freescale: Add support for LX2162 SoM & Clearfog Board
.../devicetree/bindings/arm/fsl.yaml | 9 +-
.../bindings/net/fsl,qoriq-mc-dpmac.yaml | 4 +
arch/arm64/boot/dts/freescale/Makefile | 1 +
.../arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 6 +
.../dts/freescale/fsl-lx2162a-clearfog.dts | 373 ++++++++++++++++++
.../dts/freescale/fsl-lx2162a-sr-som.dtsi | 73 ++++
6 files changed, 465 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/boot/dts/freescale/fsl-lx2162a-clearfog.dts
create mode 100644 arch/arm64/boot/dts/freescale/fsl-lx2162a-sr-som.dtsi
Cc: Shawn Guo <shawnguo@kernel.org>
Cc: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
Cc: Fabio Estevam <festevam@gmail.com>
Cc: NXP Linux Team <linux-imx@nxp.com>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Conor Dooley <conor+dt@kernel.org>
Cc: Li Yang <leoyang.li@nxp.com>
--
2.35.3
next reply other threads:[~2023-08-18 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 11:10 Josua Mayer [this message]
2023-08-18 11:10 ` [PATCH v5 1/4] arm64: dts: lx2160a: describe the SerDes block #2 Josua Mayer
2023-09-17 14:33 ` Josua Mayer
2023-08-18 11:10 ` [PATCH v5 2/4] dt-bindings: net: dpaa2 mac: add phys property Josua Mayer
2023-08-18 11:10 ` [PATCH v5 3/4] dt-bindings: arm: Add SolidRun LX2162A SoM & Clearfog Board Josua Mayer
2023-08-18 11:10 ` [PATCH v5 4/4] arm64: dts: freescale: Add support for LX2162 " Josua Mayer
2023-09-24 13:51 ` Shawn Guo
2023-10-01 10:21 ` Josua Mayer
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=20230818111016.11271-1-josua@solid-run.com \
--to=josua@solid-run.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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).