Linux clock framework development
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: mturquette@baylibre.com, Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: [GIT PULL] Rockchip clock changes for 5.19 #2
Date: Tue, 17 May 2022 21:31:15 +0200	[thread overview]
Message-ID: <5781991.QJadu78ljV@phil> (raw)

Hi Mike, Stephen,

please find below a pull-request converting a number of Rockchip
clock controllers to yaml, which shound go on top of the previous
pull request.

In the discussion Stephen had comments about the optional clocks, that
have a circular dependency (xin24m -> cru -> i2c -> rtc -> xin32k -> cru) .
After everyone put in their argument, the discussion itself just stopped.

I've picked up the conversion patches anyway, as this is the status-quo
in terms of modelling clocks on Rockchip, so the yaml conversion doesn't
change anything in either direction and just transforms what is in the
kernel right now into the yaml format which will improve devicetree checks
a lot and also reduce the number of warnings emitted by the checker.

So hopefully please pull :-)
Thanks
Heiko


The following changes since commit b21445db9818ccb9fa1c0ba81fd3705eb8d347e3:

  dt-binding: clock: Add missing rk3568 cru bindings (2022-05-14 12:40:41 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v5.19-rockchip-clk2

for you to fetch changes up to 32a214cd8ccbc361319bcd00b0b1b05a6b53bc61:

  dt-bindings: clock: convert rockchip,rk3368-cru.txt to YAML (2022-05-17 21:05:43 +0200)

----------------------------------------------------------------
Conversion from txt to Yaml for a number of Rockchip
clock bindings.

----------------------------------------------------------------
Johan Jonker (8):
      dt-bindings: clock: convert rockchip,rv1108-cru.txt to YAML
      dt-bindings: clock: convert rockchip,rk3288-cru.txt to YAML
      dt-bindings: clock: convert rockchip,rk3188-cru.txt to YAML
      dt-bindings: clock: convert rockchip,px30-cru.txt to YAML
      dt-bindings: clock: convert rockchip,rk3308-cru.txt to YAML
      dt-bindings: clock: convert rockchip,rk3036-cru.txt to YAML
      dt-bindings: clock: convert rockchip,rk3228-cru.txt to YAML
      dt-bindings: clock: convert rockchip,rk3368-cru.txt to YAML

 .../bindings/clock/rockchip,px30-cru.txt           |  70 ------------
 .../bindings/clock/rockchip,px30-cru.yaml          | 119 +++++++++++++++++++++
 .../bindings/clock/rockchip,rk3036-cru.txt         |  56 ----------
 .../bindings/clock/rockchip,rk3036-cru.yaml        |  72 +++++++++++++
 .../bindings/clock/rockchip,rk3188-cru.txt         |  61 -----------
 .../bindings/clock/rockchip,rk3188-cru.yaml        |  78 ++++++++++++++
 .../bindings/clock/rockchip,rk3228-cru.txt         |  58 ----------
 .../bindings/clock/rockchip,rk3228-cru.yaml        |  74 +++++++++++++
 .../bindings/clock/rockchip,rk3288-cru.txt         |  67 ------------
 .../bindings/clock/rockchip,rk3288-cru.yaml        |  85 +++++++++++++++
 .../bindings/clock/rockchip,rk3308-cru.txt         |  60 -----------
 .../bindings/clock/rockchip,rk3308-cru.yaml        |  76 +++++++++++++
 .../bindings/clock/rockchip,rk3368-cru.txt         |  61 -----------
 .../bindings/clock/rockchip,rk3368-cru.yaml        |  78 ++++++++++++++
 .../bindings/clock/rockchip,rv1108-cru.txt         |  59 ----------
 .../bindings/clock/rockchip,rv1108-cru.yaml        |  75 +++++++++++++
 16 files changed, 657 insertions(+), 492 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,px30-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,px30-cru.yaml
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3036-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3036-cru.yaml
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3188-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3188-cru.yaml
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3228-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3228-cru.yaml
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3288-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3288-cru.yaml
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3308-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3308-cru.yaml
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3368-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3368-cru.yaml
 delete mode 100644 Documentation/devicetree/bindings/clock/rockchip,rv1108-cru.txt
 create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rv1108-cru.yaml




             reply	other threads:[~2022-05-17 19:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 19:31 Heiko Stuebner [this message]
2022-05-17 22:20 ` [GIT PULL] Rockchip clock changes for 5.19 #2 Stephen Boyd

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=5781991.QJadu78ljV@phil \
    --to=heiko@sntech.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    /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