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 6.2
Date: Sat, 19 Nov 2022 20:57:30 +0800 [thread overview]
Message-ID: <20221119125733.32719-3-shawnguo@kernel.org> (raw)
In-Reply-To: <20221119125733.32719-1-shawnguo@kernel.org>
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-bindings-6.2
for you to fetch changes up to 651ae85e5c5be0185f341e82171275b0c3b68868:
dt-bindings: arm: fsl: Add an entry for Cloos PHG board (2022-11-14 16:56:31 +0800)
----------------------------------------------------------------
i.MX dt-bindings update for 6.2:
- New vendor prefix for Cloos and InnoComm.
- New compatible for Cloos PHG board, InnoComm WB15 EVK and Kobo Aura 2.
- Improve snvs-lpgpr bindings schema regarding i.MX8M SNVS LPGRP
compatible strings.
- Improve fsl-imx-cspi bindings schema for i.MX8MP ECSPI.
- Add bindings schema for i.MX8M ANATOP device.
- Update SCU firmware resource ID header by syncing with the latest
available SCFW kit version 1.13.0.
----------------------------------------------------------------
Andreas Kemnade (1):
dt-bindings: arm: fsl: add compatible string for Kobo Aura 2
Fabio Estevam (2):
dt-bindings: vendor-prefixes: Add an entry for Cloos
dt-bindings: arm: fsl: Add an entry for Cloos PHG board
Marek Vasut (1):
dt-bindings: nvmem: snvs-lpgpr: Fix i.MX8M compatible strings
Peng Fan (2):
dt-bindings: clock: add i.MX8M Anatop
dt-bindings: spi: fsl-imx-cspi: update i.MX8MP binding
Sascha Hauer (2):
dt-bindings: vendor-prefixes: Add prefix for InnoComm
dt-bindings: arm: fsl: Add InnoComm WB15 EVK
Viorel Suman (1):
dt-bindings: firmware: imx: sync with SCFW kit v1.13.0
Documentation/devicetree/bindings/arm/fsl.yaml | 3 +
.../bindings/clock/fsl,imx8m-anatop.yaml | 51 ++++
.../devicetree/bindings/nvmem/snvs-lpgpr.yaml | 20 +-
.../devicetree/bindings/spi/fsl-imx-cspi.yaml | 4 +-
.../devicetree/bindings/vendor-prefixes.yaml | 4 +
include/dt-bindings/firmware/imx/rsrc.h | 302 ++++++++++++++-------
6 files changed, 279 insertions(+), 105 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/fsl,imx8m-anatop.yaml
_______________________________________________
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:[~2022-11-19 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 12:57 [GIT PULL 1/6] i.MX drivers change for 6.2 Shawn Guo
2022-11-19 12:57 ` [GIT PULL 2/6] i.MX SoC " Shawn Guo
2022-11-19 12:57 ` Shawn Guo [this message]
2022-11-19 12:57 ` [GIT PULL 4/6] i.MX arm device tree update " Shawn Guo
2022-11-19 12:57 ` [GIT PULL 5/6] i.MX arm64 " Shawn Guo
2022-11-19 12:57 ` [GIT PULL 6/6] i.MX defconfig change " 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=20221119125733.32719-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).