From: Rob Herring <robh@kernel.org>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
Heiko Stuebner <heiko@sntech.de>,
Kever Yang <kever.yang@rock-chips.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
kernel@collabora.com
Subject: Re: [PATCH 2/2] dt-bindings: timer: convert rockchip,rk-timer.txt to YAML
Date: Thu, 29 Apr 2021 11:25:42 -0500 [thread overview]
Message-ID: <20210429162542.GA1372880@robh.at.kernel.org> (raw)
In-Reply-To: <20210424191946.69978-2-ezequiel@collabora.com>
On Sat, Apr 24, 2021 at 04:19:46PM -0300, Ezequiel Garcia wrote:
> Convert Rockchip Timer dt-bindings to YAML.
>
> Signed-off-by: Ezequiel Garcia <ezequiel@collabora.com>
> ---
> .../bindings/timer/rockchip,rk-timer.txt | 27 --------
> .../bindings/timer/rockchip,rk-timer.yaml | 67 +++++++++++++++++++
> 2 files changed, 67 insertions(+), 27 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/timer/rockchip,rk-timer.txt
> create mode 100644 Documentation/devicetree/bindings/timer/rockchip,rk-timer.yaml
>
> diff --git a/Documentation/devicetree/bindings/timer/rockchip,rk-timer.txt b/Documentation/devicetree/bindings/timer/rockchip,rk-timer.txt
> deleted file mode 100644
> index d65fdce7c7f0..000000000000
> --- a/Documentation/devicetree/bindings/timer/rockchip,rk-timer.txt
> +++ /dev/null
> @@ -1,27 +0,0 @@
> -Rockchip rk timer
> -
> -Required properties:
> -- compatible: should be:
> - "rockchip,rv1108-timer", "rockchip,rk3288-timer": for Rockchip RV1108
> - "rockchip,rk3036-timer", "rockchip,rk3288-timer": for Rockchip RK3036
> - "rockchip,rk3066-timer", "rockchip,rk3288-timer": for Rockchip RK3066
> - "rockchip,rk3188-timer", "rockchip,rk3288-timer": for Rockchip RK3188
> - "rockchip,rk3228-timer", "rockchip,rk3288-timer": for Rockchip RK3228
> - "rockchip,rk3229-timer", "rockchip,rk3288-timer": for Rockchip RK3229
> - "rockchip,rk3288-timer": for Rockchip RK3288
> - "rockchip,rk3368-timer", "rockchip,rk3288-timer": for Rockchip RK3368
> - "rockchip,rk3399-timer": for Rockchip RK3399
> -- reg: base address of the timer register starting with TIMERS CONTROL register
> -- interrupts: should contain the interrupts for Timer0
> -- clocks : must contain an entry for each entry in clock-names
> -- clock-names : must include the following entries:
> - "timer", "pclk"
> -
> -Example:
> - timer: timer@ff810000 {
> - compatible = "rockchip,rk3288-timer";
> - reg = <0xff810000 0x20>;
> - interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>;
> - clocks = <&xin24m>, <&cru PCLK_TIMER>;
> - clock-names = "timer", "pclk";
> - };
> diff --git a/Documentation/devicetree/bindings/timer/rockchip,rk-timer.yaml b/Documentation/devicetree/bindings/timer/rockchip,rk-timer.yaml
> new file mode 100644
> index 000000000000..f1bc3ac7abc8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/timer/rockchip,rk-timer.yaml
> @@ -0,0 +1,67 @@
> +# SPDX-License-Identifier: GPL-2.0
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/timer/rockchip,rk-timer.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Rockchip Timer Device Tree Bindings
> +
> +maintainers:
> + - Daniel Lezcano <daniel.lezcano@linaro.org>
This should be someone that knows the h/w and cares about Rockchip.
> +
> +properties:
> + compatible:
> + oneOf:
> + - const: rockchip,rk3288-timer
> + - const: rockchip,rk3399-timer
> + - items:
> + - enum:
> + - rockchip,rv1108-timer
> + - rockchip,rk3036-timer
> + - rockchip,rk3066-timer
> + - rockchip,rk3188-timer
> + - rockchip,rk3228-timer
> + - rockchip,rk3229-timer
> + - rockchip,rk3288-timer
> + - rockchip,rk3368-timer
> + - rockchip,px30-timer
> + - const: rockchip,rk3288-timer
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + minItems: 2
> + maxItems: 2
> +
> + clock-names:
> + items:
> + enum:
> + - timer
> + - pclk
We can't define the order here? We should fix dts files if they are
inconsistent.
> + minItems: 2
> + maxItems: 2
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/clock/rk3288-cru.h>
> +
> + timer: timer@ff810000 {
> + compatible = "rockchip,rk3288-timer";
> + reg = <0xff810000 0x20>;
> + interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&xin24m>, <&cru PCLK_TIMER>;
> + clock-names = "timer", "pclk";
> + };
> --
> 2.30.0
>
next prev parent reply other threads:[~2021-04-29 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 19:19 [PATCH 1/2] arm64: dts: rockchip: add timer0 clocks on rk3368 Ezequiel Garcia
2021-04-24 19:19 ` [PATCH 2/2] dt-bindings: timer: convert rockchip,rk-timer.txt to YAML Ezequiel Garcia
2021-04-26 21:04 ` Rob Herring
2021-04-29 16:25 ` Rob Herring [this message]
2021-04-29 17:03 ` Ezequiel Garcia
2021-04-29 20:28 ` 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=20210429162542.GA1372880@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-rockchip@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).