From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 4/5] arm64: dts: imx: add imx8qxp mek support
Date: Mon, 12 Nov 2018 20:07:04 -0600 [thread overview]
Message-ID: <20181113020704.GA31151@bogus> (raw)
In-Reply-To: <1541864596-15958-5-git-send-email-aisheng.dong@nxp.com>
On Sat, 10 Nov 2018 15:48:23 +0000, "A.s. Dong" wrote:
> i.MX 8QuadXPlus is a quad (4x) Cortex-A35 proccessor with powerful
> graphic and multimedia features. This patch adds imx8qxp mek board
> support.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: devicetree at vger.kernel.org
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Cc: Fabio Estevam <fabio.estevam@nxp.com>
> Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
> ---
> v3->v4:
> * remove un-documented enet phy properties
> v2->v3:
> * Pad names update
> * move memory node to here
> * add no-sd and no-sdio under emmc node
> ---
> Documentation/devicetree/bindings/arm/fsl.txt | 4 +
> arch/arm64/boot/dts/freescale/Makefile | 1 +
> arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 137 ++++++++++++++++++++++++++
> 3 files changed, 142 insertions(+)
> create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp-mek.dts
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-11-13 2:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 15:48 [PATCH V4 0/5] arm64: imx: add imx8qxp support A.s. Dong
2018-11-10 15:48 ` [PATCH V4 1/5] dt-bindings: serial: lpuart: add imx8qxp compatible string A.s. Dong
2018-11-10 15:48 ` [PATCH V4 2/5] arm64: imx: add imx8qxp support A.s. Dong
2018-11-10 15:48 ` [PATCH V4 3/5] arm64: dts: " A.s. Dong
2018-11-13 2:06 ` Rob Herring
2018-11-13 2:18 ` A.s. Dong
2018-11-10 15:48 ` [PATCH V4 4/5] arm64: dts: imx: add imx8qxp mek support A.s. Dong
2018-11-13 2:07 ` Rob Herring [this message]
2018-11-10 15:48 ` [PATCH V4 5/5] defconfig: arm64: add imx8qxp support A.s. Dong
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=20181113020704.GA31151@bogus \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).