linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Aisheng Dong <aisheng.dong@nxp.com>
To: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
	"dongas86@gmail.com" <dongas86@gmail.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>
Subject: [PATCH V6 0/4] arm64: imx: add imx8qxp support
Date: Fri, 11 Jan 2019 11:37:19 +0000	[thread overview]
Message-ID: <1547206279-26169-1-git-send-email-aisheng.dong@nxp.com> (raw)

Add imx8qxp mek basic support with the function
Lpuart
uSDHC
FEC
GPIO

ChangeLog:
v5->v6:
 * separate binding doc
 * merge imx8-ca35.dtsi into imx8qxp.dtsi
 * remove still unused nodes
v5-resend
 * Rebase against v5.0-rc1
   Clock ID name updated accordingly
   [1] https://patchwork.kernel.org/patch/10741753/
v4->v5:
 * remove the dependency of SOC_IMX8QXP
 * the original Patch 2 adding SOC_IMX8QXP is dropped
v4:
 * change to new power domain binding suggested by Ulf
 * Note below patches were merged separetely by each SS maintainer,
   so dropped in this seris
   dt-bindings: mmc: fsl-imx-esdhc: add imx8qxp compatible string
   dt-bindings: i2c: i2c-imx-lpi2c: add imx8qxp compatible string
   dt-bindings: spi: lpspi: add imx8qxp compatible string

Dong Aisheng (4):
  dt-bindings: arm: imx: add imx8qxp mek support
  arm64: dts: imx: add imx8qxp support
  arm64: dts: imx: add imx8qxp mek support
  defconfig: arm64: add imx8qxp support

 Documentation/devicetree/bindings/arm/fsl.yaml |   6 +
 arch/arm64/boot/dts/freescale/Makefile         |   1 +
 arch/arm64/boot/dts/freescale/imx8qxp-mek.dts  | 137 ++++++++
 arch/arm64/boot/dts/freescale/imx8qxp.dtsi     | 442 +++++++++++++++++++++++++
 arch/arm64/configs/defconfig                   |  10 +
 5 files changed, 596 insertions(+)
 create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp-mek.dts
 create mode 100644 arch/arm64/boot/dts/freescale/imx8qxp.dtsi

-- 
2.7.4


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-01-11 11:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 11:37 Aisheng Dong [this message]
2019-01-11 11:37 ` [PATCH V6 1/4] dt-bindings: arm: imx: add imx8qxp mek support Aisheng Dong
2019-01-14  1:19   ` Shawn Guo
2019-01-11 11:37 ` [PATCH V6 2/4] arm64: dts: imx: add imx8qxp support Aisheng Dong
2019-01-14  1:21   ` Shawn Guo
2019-01-11 11:37 ` [PATCH V6 3/4] arm64: dts: imx: add imx8qxp mek support Aisheng Dong
2019-01-14  1:21   ` Shawn Guo
2019-01-11 11:37 ` [PATCH V6 4/4] defconfig: arm64: add imx8qxp support Aisheng Dong
2019-01-14  1:22   ` Shawn Guo
2019-01-14  3:24     ` Aisheng 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=1547206279-26169-1-git-send-email-aisheng.dong@nxp.com \
    --to=aisheng.dong@nxp.com \
    --cc=catalin.marinas@arm.com \
    --cc=dongas86@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=will.deacon@arm.com \
    /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).