From: Shawn Guo <shawnguo@kernel.org>
To: arm@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
linux-imx@nxp.com, kernel@pengutronix.de
Subject: [GIT PULL 3/7] i.MX DT bindings update for 5.1
Date: Tue, 12 Feb 2019 19:21:22 +0800 [thread overview]
Message-ID: <20190212112126.572-3-shawnguo@kernel.org> (raw)
In-Reply-To: <20190212112126.572-1-shawnguo@kernel.org>
Hi Arnd, Olof,
In the past, I was simply using imx/dt branch to collect i.MX platform
related DT bindings changes, together with arm32 dts ones. Now with the
move to json-schema, we are using a single fsl.yaml file to accommodate
both arm32 and arm64 platform bindings, while we have separate branches
for dts changes - imx/dt and imx/dt64. To avoid conflicts, I chose to
create a new branch imx/bindings for i.MX platform bindings change for
this cycle. That's why we get this pull request, which you will pull
into arm-soc next/dt branch, I guess.
For future cycles, I would like to hear your thoughts on if we can use
a single branch for both arm32 and arm64 dts changes, so that the
bindings changes can go in there too. Thanks.
Shawn
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-bindings-5.1
for you to fetch changes up to 2a005397117019cbd4e4a09ab5cf896a16b652c5:
dt-bindings: fsl: scu: add imx8qm scu clock support (2019-02-01 14:21:22 +0800)
----------------------------------------------------------------
i.MX DT bindings update for 5.1:
- Convert the bindings of FSL SoCs and the boards built on FSL SoCs to
json-schema.
- Add bindings for boards: i.MX8QXP MEK, LS1012A based Oxalis, and
i.MX6 based Y Soft IOTA Draco and Hydra.
- Add vendor prefix for EBS-SYSTART GmbH and Catalyst Semiconductor.
- Add bindings for imx8qm scu clock and imx7ulp system integration
module.
----------------------------------------------------------------
Aisheng Dong (3):
dt-bindings: arm: imx: add imx8qxp mek support
dt-bindings: fsl: scu: add fallback compatible string for clock
dt-bindings: fsl: scu: add imx8qm scu clock support
Anson Huang (1):
dt-bindings: fsl: add imx7ulp system integration module binding
Manivannan Sadhasivam (3):
dt-bindings: arm: fsl: Fix bindings for LS1012A and LS1021A based boards
dt-bindings: vendor-prefixes: Add EBS-SYSTART GmbH Vendor Prefix
dt-bindings: arm: fsl: Add devicetree binding for Oxalis
Martyn Welch (1):
dt-bindings: Add vendor prefix for Catalyst Semiconductor
Rob Herring (1):
dt-bindings: arm: Convert FSL board/soc bindings to json-schema
Vokáč Michal (1):
dt-bindings: arm: Add Y Soft IOTA Draco, Hydra and Ursa boards
Documentation/devicetree/bindings/arm/armadeus.txt | 6 -
Documentation/devicetree/bindings/arm/bhf.txt | 6 -
.../devicetree/bindings/arm/compulab-boards.txt | 25 ---
.../bindings/arm/freescale/fsl,imx7ulp-sim.txt | 16 ++
.../devicetree/bindings/arm/freescale/fsl,scu.txt | 7 +-
Documentation/devicetree/bindings/arm/fsl.txt | 237 ---------------------
Documentation/devicetree/bindings/arm/fsl.yaml | 232 ++++++++++++++++++++
Documentation/devicetree/bindings/arm/i2se.txt | 22 --
Documentation/devicetree/bindings/arm/olimex.txt | 10 -
.../devicetree/bindings/arm/technologic.txt | 23 --
.../devicetree/bindings/vendor-prefixes.txt | 2 +
11 files changed, 255 insertions(+), 331 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/arm/armadeus.txt
delete mode 100644 Documentation/devicetree/bindings/arm/bhf.txt
delete mode 100644 Documentation/devicetree/bindings/arm/compulab-boards.txt
create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,imx7ulp-sim.txt
delete mode 100644 Documentation/devicetree/bindings/arm/fsl.txt
create mode 100644 Documentation/devicetree/bindings/arm/fsl.yaml
delete mode 100644 Documentation/devicetree/bindings/arm/i2se.txt
delete mode 100644 Documentation/devicetree/bindings/arm/olimex.txt
delete mode 100644 Documentation/devicetree/bindings/arm/technologic.txt
_______________________________________________
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:[~2019-02-12 11:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 11:21 [GIT PULL 1/7] i.MX drivers update for 5.1 Shawn Guo
2019-02-12 11:21 ` [GIT PULL 2/7] i.MX SoC changes " Shawn Guo
2019-02-15 16:40 ` Arnd Bergmann
2019-02-12 11:21 ` Shawn Guo [this message]
2019-02-15 15:08 ` [GIT PULL 3/7] i.MX DT bindings update " Arnd Bergmann
2019-02-18 1:16 ` Shawn Guo
2019-02-12 11:21 ` [GIT PULL 4/7] i.MX device tree changes " Shawn Guo
2019-02-15 15:10 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 5/7] i.MX arm64 " Shawn Guo
2019-02-15 15:11 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 6/7] i.MX defconfig updates " Shawn Guo
2019-02-15 15:47 ` Arnd Bergmann
2019-02-12 11:21 ` [GIT PULL 7/7] i.MX MAINTAINERS update " Shawn Guo
2019-02-15 16:38 ` Arnd Bergmann
2019-02-15 17:03 ` Fabio Estevam
2019-02-15 16:18 ` [GIT PULL 1/7] 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=20190212112126.572-3-shawnguo@kernel.org \
--to=shawnguo@kernel.org \
--cc=arm@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.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).