From: Abel Vesa <abel.vesa@nxp.com>
To: Lucas Stach <l.stach@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh@kernel.org>
Cc: dl-linux-imx <linux-imx@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Aisheng Dong <aisheng.dong@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
"patchwork-lst@pengutronix.de" <patchwork-lst@pengutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Abel Vesa <abelvesa@linux.com>, Abel Vesa <abel.vesa@nxp.com>
Subject: [PATCH v5 0/6] Add basic support for i.MX8MQ SoC and i.MX8MQ EVK board
Date: Sun, 9 Dec 2018 14:26:05 +0000 [thread overview]
Message-ID: <1544365552-30270-1-git-send-email-abel.vesa@nxp.com> (raw)
Took this from Lucas since he's busy with some other work for the moment and
I thought we might be able to get this ready for the merge window.
Basically is just a respin with a minor fix for a comment from Rob.
Lucas, thanks for all the effort with this.
Changes since v5:
* replaced the name of the node peripherals with soc in dts file
Baruch Siach (2):
arm64: dts: imx8mq: add watchdog devices
arm64: dts: imx8mq-evk: enable watchdog
Lucas Stach (4):
arm64: add basic Kconfig symbols for i.MX8
arm64: add basic DTS for i.MX8MQ
arm64: add support for i.MX8M EVK board
MAINTAINERS: add i.MX8 DT path to i.MX architecture
Documentation/devicetree/bindings/arm/fsl.txt | 8 +
MAINTAINERS | 1 +
arch/arm64/Kconfig.platforms | 14 +
arch/arm64/boot/dts/freescale/Makefile | 2 +
arch/arm64/boot/dts/freescale/imx8mq-evk.dts | 303 ++++++++++++
arch/arm64/boot/dts/freescale/imx8mq-pinfunc.h | 623 +++++++++++++++++++++++++
arch/arm64/boot/dts/freescale/imx8mq.dtsi | 416 +++++++++++++++++
7 files changed, 1367 insertions(+)
create mode 100644 arch/arm64/boot/dts/freescale/imx8mq-evk.dts
create mode 100644 arch/arm64/boot/dts/freescale/imx8mq-pinfunc.h
create mode 100644 arch/arm64/boot/dts/freescale/imx8mq.dtsi
--
2.7.4
next reply other threads:[~2018-12-09 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 14:26 Abel Vesa [this message]
2018-12-09 14:26 ` [PATCH v5 1/6] arm64: add basic Kconfig symbols for i.MX8 Abel Vesa
2018-12-16 9:14 ` Shawn Guo
2018-12-09 14:26 ` [PATCH v5 2/6] arm64: add basic DTS for i.MX8MQ Abel Vesa
2018-12-10 22:18 ` Rob Herring
2018-12-09 14:26 ` [PATCH v5 3/6] arm64: add support for i.MX8M EVK board Abel Vesa
2018-12-16 9:17 ` Shawn Guo
2018-12-09 14:26 ` [PATCH v5 4/6] MAINTAINERS: add i.MX8 DT path to i.MX architecture Abel Vesa
2018-12-09 14:26 ` [PATCH v5 5/6] arm64: dts: imx8mq: add watchdog devices Abel Vesa
2018-12-09 14:26 ` [PATCH v5 6/6] arm64: dts: imx8mq-evk: enable watchdog Abel Vesa
2018-12-11 8:09 ` [PATCH v5 0/6] Add basic support for i.MX8MQ SoC and i.MX8MQ EVK board 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=1544365552-30270-1-git-send-email-abel.vesa@nxp.com \
--to=abel.vesa@nxp.com \
--cc=abelvesa@linux.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-lst@pengutronix.de \
--cc=robh@kernel.org \
--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).