From: Rob Herring <robh@kernel.org>
To: Abel Vesa <abel.vesa@nxp.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Shawn Guo <shawnguo@kernel.org>, 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: Re: [PATCH v5 2/6] arm64: add basic DTS for i.MX8MQ
Date: Mon, 10 Dec 2018 16:18:26 -0600 [thread overview]
Message-ID: <20181210221826.GA21311@bogus> (raw)
In-Reply-To: <1544365552-30270-3-git-send-email-abel.vesa@nxp.com>
On Sun, 9 Dec 2018 14:26:07 +0000, Abel Vesa wrote:
> From: Lucas Stach <l.stach@pengutronix.de>
>
> This adds the basic DTS for the i.MX8MQ.
> For now only the following peripherals are supported:
> - IOMUXC (pin controller)
> - CCM (clock controller)
> - GPIO
> - UART
> - uSDHC (SD/eMMC controller)
> - FEC (ethernet controller)
> - i2c
>
> This is enough to get a very basic board support up and running.
>
> One known limitation is that the driver for the GPC interrupt
> controller is still missing, rendering the CPU sleep states unusable
> as there is nothing waking them up anymore.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> Reviewed-by: Dong Aisheng <Aisheng.dong@nxp.com>
> ---
> Documentation/devicetree/bindings/arm/fsl.txt | 4 +
> arch/arm64/boot/dts/freescale/imx8mq-pinfunc.h | 623 +++++++++++++++++++++++++
> arch/arm64/boot/dts/freescale/imx8mq.dtsi | 392 ++++++++++++++++
> 3 files changed, 1019 insertions(+)
> create mode 100644 arch/arm64/boot/dts/freescale/imx8mq-pinfunc.h
> create mode 100644 arch/arm64/boot/dts/freescale/imx8mq.dtsi
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-12-10 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 14:26 [PATCH v5 0/6] Add basic support for i.MX8MQ SoC and i.MX8MQ EVK board Abel Vesa
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 [this message]
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=20181210221826.GA21311@bogus \
--to=robh@kernel.org \
--cc=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=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).