linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Elaine Zhang <zhangqing@rock-chips.com>,
	kernel@collabora.com,
	Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: Re: [PATCH 1/5] dt-binding: clock: Document rockchip,rk3588-cru bindings
Date: Mon, 27 Jun 2022 08:17:15 +0200	[thread overview]
Message-ID: <1896998.PYKUYFuaPT@diego> (raw)
In-Reply-To: <20220623160329.239501-2-sebastian.reichel@collabora.com>

Hi Sebastian,

Am Donnerstag, 23. Juni 2022, 18:03:25 CEST schrieb Sebastian Reichel:
> From: Elaine Zhang <zhangqing@rock-chips.com>
> 
> Document the device tree bindings of the rockchip rk3588 SoC
> clock and reset unit.
> 
> This also contains the header, which is shared betwen the DT
> files and the kernel driver containing the clock and reset IDs.
> 
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> [add additional clocks IDs for gate clocks, which are handled via
>  separate DT nodes in the vendor kernel]
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> ---
>  .../bindings/clock/rockchip,rk3588-cru.yaml   |   59 +
>  include/dt-bindings/clock/rk3588-cru.h        | 1516 +++++++++++++++++
>  2 files changed, 1575 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3588-cru.yaml
>  create mode 100644 include/dt-bindings/clock/rk3588-cru.h

please split the binding and dt-binding-header into separate patches.
Depending on what gets merged when, I will need a shared-branch
for the header, so don't want to also carry the yaml binding in there.

Thanks
Heiko



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

  parent reply	other threads:[~2022-06-27  6:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 16:03 [PATCH 0/5] RK3588 Clock and Reset Support Sebastian Reichel
2022-06-23 16:03 ` [PATCH 1/5] dt-binding: clock: Document rockchip,rk3588-cru bindings Sebastian Reichel
2022-06-26 20:27   ` Krzysztof Kozlowski
2022-06-27  6:14     ` Heiko Stübner
2022-06-27  6:46       ` Krzysztof Kozlowski
2022-06-27  6:17   ` Heiko Stübner [this message]
2022-06-23 16:03 ` [PATCH 2/5] clk: rockchip: add register offset of the cores select parent Sebastian Reichel
2022-06-23 16:03 ` [PATCH 3/5] clk: rockchip: add pll type for RK3588 Sebastian Reichel
2022-06-23 16:03 ` [PATCH 4/5] clk: rockchip: clk-cpu: add mux setting for cpu change frequency Sebastian Reichel

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=1896998.PYKUYFuaPT@diego \
    --to=heiko@sntech.de \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@collabora.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=zhangqing@rock-chips.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).