From: Mathieu Othacehe <othacehe@gnu.org>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
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>, Li Yang <leoyang.li@nxp.com>,
Primoz Fiser <primoz.fiser@norik.com>,
Stefan Wahren <wahrenst@gmx.net>,
Christoph Stoidner <c.stoidner@phytec.de>,
Wadim Egorov <w.egorov@phytec.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Mathieu Othacehe <othacehe@gnu.org>
Subject: [PATCH v5 0/3] Add phyBOARD-Segin-i.MX93 support
Date: Wed, 24 Jan 2024 08:49:27 +0100 [thread overview]
Message-ID: <20240124074930.26101-1-othacehe@gnu.org> (raw)
Hello,
This adds support for the phyBOARD-Segin-i.MX93 board.
In this v5, I removed the gpio-line-names that were controversial.
Thanks,
Signed-off-by: Mathieu Othacehe <othacehe@gnu.org>
---
Changes in v5:
- Remove the gpio-line-names
- Fix the product URLs
Changes in v4:
- Add gpio-line-names to gpio-vf610 dt-bindings documentation
- Add the heartbeat SoM LED
- Add support for the FEC ethernet port
- Restore the original authors in the copyright
- Add gpio-line-names for the GPIOs on the X16 header
Changes in v3:
- Update documentation to match PHYTEC naming
- Remove useless properties
- Update pinmux from PHYTEC downstream kernel
Changes in v2:
- Remove useless line
- Add missing reserved-memory entries
v4: https://lore.kernel.org/linux-devicetree/20240122095306.14084-1-othacehe@gnu.org/
Mathieu Othacehe (3):
dt-bindings: arm: fsl: Add phyBOARD-Segin-i.MX93
dt-bindings: gpio: gpio-vf610: add gpio-line-names
arm64: dts: imx93: Add phyBOARD-Segin-i.MX93 support
.../devicetree/bindings/arm/fsl.yaml | 6 +
.../devicetree/bindings/gpio/gpio-vf610.yaml | 2 +
arch/arm64/boot/dts/freescale/Makefile | 1 +
.../dts/freescale/imx93-phyboard-segin.dts | 117 ++++++++++++++++
.../boot/dts/freescale/imx93-phycore-som.dtsi | 126 ++++++++++++++++++
5 files changed, 252 insertions(+)
create mode 100644 arch/arm64/boot/dts/freescale/imx93-phyboard-segin.dts
create mode 100644 arch/arm64/boot/dts/freescale/imx93-phycore-som.dtsi
--
2.41.0
next reply other threads:[~2024-01-24 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 7:49 Mathieu Othacehe [this message]
2024-01-24 7:49 ` [PATCH v5 1/3] dt-bindings: arm: fsl: Add phyBOARD-Segin-i.MX93 Mathieu Othacehe
2024-01-24 9:30 ` Wadim Egorov
2024-02-06 7:31 ` Shawn Guo
2024-01-24 7:49 ` [PATCH v5 2/3] dt-bindings: gpio: gpio-vf610: add gpio-line-names Mathieu Othacehe
2024-01-24 11:31 ` Stefan Wahren
2024-01-24 7:49 ` [PATCH v5 3/3] arm64: dts: imx93: Add phyBOARD-Segin-i.MX93 support Mathieu Othacehe
2024-01-24 9:34 ` Wadim Egorov
2024-02-06 7:31 ` Shawn Guo
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=20240124074930.26101-1-othacehe@gnu.org \
--to=othacehe@gnu.org \
--cc=c.stoidner@phytec.de \
--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=primoz.fiser@norik.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=w.egorov@phytec.de \
--cc=wahrenst@gmx.net \
/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).