From: Anson Huang <Anson.Huang@nxp.com>
To: mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, shc_work@mail.ru,
s.trumtrar@pengutronix.de, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Linux-imx@nxp.com
Subject: [PATCH 0/9] Convert i.MX legacy platforms clock binding to json-schema
Date: Thu, 28 May 2020 15:27:50 +0800 [thread overview]
Message-ID: <1590650879-18288-1-git-send-email-Anson.Huang@nxp.com> (raw)
The patch series converts i.MX legacy platforms clock binding to
json-schema, including i.MX1, i.MX21, i.MX23, i.MX25, i.MX27, i.MX28,
i.MX31, i.MX35 and i.MX5.
On i.MX21, the CCM has no interrupt at all, so remove the interrupts
property from original binding doc.
Anson Huang (9):
dt-bindings: clock: Convert i.MX5 clock to json-schema
dt-bindings: clock: Convert i.MX35 clock to json-schema
dt-bindings: clock: Convert i.MX31 clock to json-schema
dt-bindings: clock: Convert i.MX28 clock to json-schema
dt-bindings: clock: Convert i.MX23 clock to json-schema
dt-bindings: clock: Convert i.MX27 clock to json-schema
dt-bindings: clock: Convert i.MX25 clock to json-schema
dt-bindings: clock: Convert i.MX21 clock to json-schema
dt-bindings: clock: Convert i.MX1 clock to json-schema
.../devicetree/bindings/clock/imx1-clock.txt | 26 ---
.../devicetree/bindings/clock/imx1-clock.yaml | 49 ++++++
.../devicetree/bindings/clock/imx21-clock.txt | 27 ---
.../devicetree/bindings/clock/imx21-clock.yaml | 49 ++++++
.../devicetree/bindings/clock/imx23-clock.txt | 70 --------
.../devicetree/bindings/clock/imx23-clock.yaml | 90 ++++++++++
.../devicetree/bindings/clock/imx25-clock.txt | 160 ------------------
.../devicetree/bindings/clock/imx25-clock.yaml | 184 +++++++++++++++++++++
.../devicetree/bindings/clock/imx27-clock.txt | 27 ---
.../devicetree/bindings/clock/imx27-clock.yaml | 53 ++++++
.../devicetree/bindings/clock/imx28-clock.txt | 93 -----------
.../devicetree/bindings/clock/imx28-clock.yaml | 113 +++++++++++++
.../devicetree/bindings/clock/imx31-clock.txt | 90 ----------
.../devicetree/bindings/clock/imx31-clock.yaml | 118 +++++++++++++
.../devicetree/bindings/clock/imx35-clock.txt | 114 -------------
.../devicetree/bindings/clock/imx35-clock.yaml | 137 +++++++++++++++
.../devicetree/bindings/clock/imx5-clock.txt | 28 ----
.../devicetree/bindings/clock/imx5-clock.yaml | 63 +++++++
18 files changed, 856 insertions(+), 635 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/clock/imx1-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx1-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/imx21-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx21-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/imx23-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx23-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/imx25-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx25-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/imx27-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx27-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/imx28-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx28-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/imx31-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx31-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/imx35-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx35-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/imx5-clock.txt
create mode 100644 Documentation/devicetree/bindings/clock/imx5-clock.yaml
--
2.7.4
next reply other threads:[~2020-05-28 7:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 7:27 Anson Huang [this message]
2020-05-28 7:27 ` [PATCH 1/9] dt-bindings: clock: Convert i.MX5 clock to json-schema Anson Huang
2020-05-29 2:45 ` Rob Herring
2020-05-28 7:27 ` [PATCH 2/9] dt-bindings: clock: Convert i.MX35 " Anson Huang
2020-05-29 2:48 ` Rob Herring
2020-05-28 7:27 ` [PATCH 3/9] dt-bindings: clock: Convert i.MX31 " Anson Huang
2020-05-29 2:48 ` Rob Herring
2020-05-28 7:27 ` [PATCH 4/9] dt-bindings: clock: Convert i.MX28 " Anson Huang
2020-05-29 2:51 ` Rob Herring
2020-05-28 7:27 ` [PATCH 5/9] dt-bindings: clock: Convert i.MX23 " Anson Huang
2020-05-29 2:51 ` Rob Herring
2020-05-28 7:27 ` [PATCH 6/9] dt-bindings: clock: Convert i.MX27 " Anson Huang
2020-05-29 2:52 ` Rob Herring
2020-05-28 7:27 ` [PATCH 7/9] dt-bindings: clock: Convert i.MX25 " Anson Huang
2020-05-29 2:53 ` Rob Herring
2020-05-28 7:27 ` [PATCH 8/9] dt-bindings: clock: Convert i.MX21 " Anson Huang
2020-05-29 2:53 ` Rob Herring
2020-05-28 7:27 ` [PATCH 9/9] dt-bindings: clock: Convert i.MX1 " Anson Huang
2020-05-29 2:54 ` Rob Herring
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=1590650879-18288-1-git-send-email-Anson.Huang@nxp.com \
--to=anson.huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s.trumtrar@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=shc_work@mail.ru \
/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).