From: Shawn Guo <shawnguo@kernel.org>
To: soc@kernel.org, arm@kernel.org
Cc: Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/6] i.MX DT bindings update for 5.13
Date: Wed, 31 Mar 2021 12:10:16 +0800 [thread overview]
Message-ID: <20210331041019.31345-3-shawnguo@kernel.org> (raw)
In-Reply-To: <20210331041019.31345-1-shawnguo@kernel.org>
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-bindgins-5.13
for you to fetch changes up to 6634b2d252accd3fcdc94a5e0a1319009363892e:
dt-bindings: arm: fsl: Add the reMarkable 2 e-Ink tablet (2021-03-29 09:42:11 +0800)
----------------------------------------------------------------
i.MX bindings update for 5.13:
- Add vendor prefix for reMarkable.
- Add compatible for reMarkable 2 e-Ink tablet, Kontron pITX-imx8m
board, Engicam i.Core MX8M Mini devices.
- Add compatbile 'fsl,imx8qm-mu' for i.MX mailbox bindings.
- One correction on example clock-names in imx8qxp-lpcg bindings.
----------------------------------------------------------------
Alistair Francis (2):
dt-bindings: Add vendor prefix for reMarkable
dt-bindings: arm: fsl: Add the reMarkable 2 e-Ink tablet
Dong Aisheng (2):
dt-bindings: arm: fsl: add imx8qm boards compatible string
dt-bindings: mailbox: mu: add imx8qm support
Heiko Thiery (1):
dt-bindings: arm: fsl: add Kontron pITX-imx8m board
Jagan Teki (2):
dt-bindings: arm: fsl: Add Engicam i.Core MX8M Mini C.TOUCH 2.0
dt-bindings: arm: fsl: Add Engicam i.Core MX8M Mini EDIMM2.2 Starter Kit
Peng Fan (1):
dt-bindings: clock: imx8qxp-lpcg: correct the example clock-names
Documentation/devicetree/bindings/arm/fsl.yaml | 16 ++++++++++++++++
.../devicetree/bindings/clock/imx8qxp-lpcg.yaml | 6 +++---
Documentation/devicetree/bindings/mailbox/fsl,mu.yaml | 5 ++++-
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
4 files changed, 25 insertions(+), 4 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-31 4:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 4:10 [GIT PULL 1/6] i.MX drivers change for 5.13 Shawn Guo
2021-03-31 4:10 ` [GIT PULL 2/6] i.MX SoC update " Shawn Guo
2021-04-01 21:07 ` Arnd Bergmann
2021-03-31 4:10 ` Shawn Guo [this message]
2021-04-01 20:15 ` [GIT PULL 3/6] i.MX DT bindings " Arnd Bergmann
2021-03-31 4:10 ` [GIT PULL 4/6] i.MX device tree change " Shawn Guo
2021-04-01 20:15 ` Arnd Bergmann
2021-03-31 4:10 ` [GIT PULL 5/6] i.MX arm64 device tree update " Shawn Guo
2021-04-01 20:15 ` Arnd Bergmann
2021-03-31 4:10 ` [GIT PULL 6/6] i.MX defconfig change " Shawn Guo
2021-04-01 21:06 ` Arnd Bergmann
2021-04-01 19:24 ` [GIT PULL 1/6] i.MX drivers " Arnd Bergmann
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=20210331041019.31345-3-shawnguo@kernel.org \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=soc@kernel.org \
--cc=stefan@agner.ch \
/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).