From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: [PATCH v6 0/5] mainline Protonic boards
Date: Tue, 21 Apr 2020 14:40:52 +0200 [thread overview]
Message-ID: <20200421124057.19238-1-o.rempel@pengutronix.de> (raw)
changes v6:
- move fsl.yaml changes to separate patch
- remove partitions, they are provided by the bootloader
- update flash compatible
- rename can3 to can
- fix fsl,mode
- fix interrupt in the wlan node on PRTI6Q
changes v5:
- PRTI6Q: remove status from the pwm-backlight node
- drop the vendor-prefixes patch, it is already taken by Rob
- add Reviewed-by: Rob Herring <robh@kernel.org>
changes v4:
- VT7: fix typo
changes v3:
- move compatible to the start of node
- move status to the end
- use generic names in compatible
- refactor dts/dtsi
- use alphabet order for pinctrl and phandels
- remove unused or currently not supported nodes
changes v2:
- squash PRTI6Q patches
Oleksij Rempel (5):
ARM: dts: add Protonic PRTI6Q board
ARM: dts: add Protonic WD2 board
ARM: dts: add Protonic VT7 board
ARM: dts: add Protonic RVT board
dt-bindings: arm: fsl: add different Protonic boards
.../devicetree/bindings/arm/fsl.yaml | 4 +
arch/arm/boot/dts/Makefile | 4 +
arch/arm/boot/dts/imx6dl-prtrvt.dts | 182 ++++++
arch/arm/boot/dts/imx6dl-prtvt7.dts | 472 ++++++++++++++++
arch/arm/boot/dts/imx6q-prti6q.dts | 529 ++++++++++++++++++
arch/arm/boot/dts/imx6q-prtwd2.dts | 188 +++++++
arch/arm/boot/dts/imx6qdl-prti6q.dtsi | 174 ++++++
7 files changed, 1553 insertions(+)
create mode 100644 arch/arm/boot/dts/imx6dl-prtrvt.dts
create mode 100644 arch/arm/boot/dts/imx6dl-prtvt7.dts
create mode 100644 arch/arm/boot/dts/imx6q-prti6q.dts
create mode 100644 arch/arm/boot/dts/imx6q-prtwd2.dts
create mode 100644 arch/arm/boot/dts/imx6qdl-prti6q.dtsi
--
2.26.1
next reply other threads:[~2020-04-21 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 12:40 Oleksij Rempel [this message]
2020-04-21 12:40 ` [PATCH v6 1/5] ARM: dts: add Protonic PRTI6Q board Oleksij Rempel
2020-04-22 7:19 ` Marco Felsch
2020-04-21 12:40 ` [PATCH v6 2/5] ARM: dts: add Protonic WD2 board Oleksij Rempel
2020-04-21 12:40 ` [PATCH v6 3/5] ARM: dts: add Protonic VT7 board Oleksij Rempel
2020-04-22 7:04 ` Marco Felsch
2020-04-22 7:11 ` Marco Felsch
2020-04-22 9:38 ` David Jander
2020-04-22 11:20 ` Marco Felsch
2020-04-21 12:40 ` [PATCH v6 4/5] ARM: dts: add Protonic RVT board Oleksij Rempel
2020-04-21 12:40 ` [PATCH v6 5/5] dt-bindings: arm: fsl: add different Protonic boards Oleksij Rempel
2020-05-05 19:00 ` Rob Herring
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=20200421124057.19238-1-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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).