soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
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.14
Date: Sun, 13 Jun 2021 16:25:41 +0800	[thread overview]
Message-ID: <20210613082544.16067-3-shawnguo@kernel.org> (raw)
Message-ID: <20210613082541.UsTEP5sLM4T3in2zuMQCIfDPWKL6-k0be0btiw-8P5s@z> (raw)
In-Reply-To: <20210613082544.16067-1-shawnguo@kernel.org>

The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:

  Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-bindings-5.14

for you to fetch changes up to cd044eafd7105275220f6b7140a8a8fb64e0e5af:

  dt-bindings: arm: fsl: add GE B1x5pv2 boards (2021-06-12 17:57:52 +0800)

----------------------------------------------------------------
i.MX dt-bindings update for 5.14:

- Add vendor prefixes for congatec GmbH and DaSheng, Inc.
- Add compatibles for i.MX6Q DaSheng COM-9XX SBC, GE B1x5pv2 and
  i.MX8MM GW7901 boards.
- Add an optional 'resets' property for i.MX GPCv2 bindings.

----------------------------------------------------------------
Dillon Min (2):
      dt-bindings: add dasheng vendor prefix
      dt-bindings: arm: imx: Add i.mx6q DaSheng COM-9XX SBC

Lucas Stach (1):
      dt-bindings: imx: gpcv2: add support for optional resets

Sebastian Reichel (2):
      dt-bindings: vendor-prefixes: add congatec
      dt-bindings: arm: fsl: add GE B1x5pv2 boards

Tim Harvey (1):
      dt-bindings: arm: imx: add imx8mm gw7901 support

 Documentation/devicetree/bindings/arm/fsl.yaml             | 13 +++++++++++++
 Documentation/devicetree/bindings/power/fsl,imx-gpcv2.yaml | 10 ++++++++++
 Documentation/devicetree/bindings/vendor-prefixes.yaml     |  4 ++++
 3 files changed, 27 insertions(+)

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

  parent reply	other threads:[~2021-06-13  8:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13  8:25 [GIT PULL 1/6] i.MX drivers update for 5.14 Shawn Guo
2021-06-13  8:25 ` Shawn Guo
2021-06-13  8:25 ` [GIT PULL 2/6] i.MX SoC changes " Shawn Guo
2021-06-13  8:25   ` Shawn Guo
2021-06-13  8:25 ` Shawn Guo [this message]
2021-06-13  8:25   ` [GIT PULL 3/6] i.MX dt-bindings update " Shawn Guo
2021-06-13  8:25 ` [GIT PULL 4/6] i.MX device tree changes " Shawn Guo
2021-06-13  8:25   ` Shawn Guo
2021-06-13  8:25 ` [GIT PULL 5/6] i.MX arm64 " Shawn Guo
2021-06-13  8:25   ` Shawn Guo
2021-06-13  8:25 ` [GIT PULL 6/6] i.MX defconfig update " Shawn Guo
2021-06-13  8:25   ` Shawn Guo
2021-06-15 16:00 ` [GIT PULL 1/6] i.MX drivers " patchwork-bot+linux-soc

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=20210613082544.16067-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).