From: "Rob Herring (Arm)" <robh@kernel.org>
To: Claudiu <claudiu.beznea@tuxon.dev>
Cc: magnus.damm@gmail.com, linux-kernel@vger.kernel.org,
p.zabel@pengutronix.de, mturquette@baylibre.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
alexandre.belloni@bootlin.com, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, sboyd@kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org, geert+renesas@glider.be,
krzk+dt@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 06/12] dt-bindings: rtc: renesas,rzg3s-rtc: Document the Renesas RTCA-3 IP
Date: Sat, 19 Oct 2024 05:32:52 -0500 [thread overview]
Message-ID: <172933397224.3030070.17299337634844003264.robh@kernel.org> (raw)
In-Reply-To: <20241019084738.3370489-7-claudiu.beznea.uj@bp.renesas.com>
On Sat, 19 Oct 2024 11:47:32 +0300, Claudiu wrote:
> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>
> Document the RTC IP (RTCA-3) available on the Renesas RZ/G3S SoC.
> The RTC IP available on Renesas RZ/V2H is almost identical with the
> one found on Renesas RZ/G3S (it misses the time capture functionality
> which is not yet implemented on proposed driver). For this, added also a
> generic compatible that will be used at the moment as fallback for both
> RZ/G3S and RZ/V2H.
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
> ---
>
> Changes in v4:
> - collected tags
> - dropped the assigned-clocks, assigned-clock-parents properties from the
> example, along with r9a08g045-vbattb.h inclusion; these were moved
> to the VBATTB example as it fits better in there since these are
> related to the VBATTB but not to the RTC;
>
> Rob, I haven't dropped your Rb tag for this; please let me know if you
> consider it otherwise.
>
> Changes in v3:
> - added RTC bus clock, reset and power-domain; it has been detected
> by reverse engineering that RTC and VBATTB clock, reset and power
> domain are shared; HW manual doesn't mention it
> - updated example with these and with assigned-clock properties
> needed to configure the VBATTCLK MUX with proper parent
> - updated example section with dt-bindings/clock/r9a08g045-cpg.h
> and dt-bindings/clock/r9a08g045-vbattb.h includes
> - for all these, dropped Conor's Rb tag
>
> Changes in v2:
> - updated patch description and title
> - included reference to rtc.yaml
> - updated compatible list with a generic compatible as explained in
> patch description; with this the node in examples section has also been
> updated
> - used items to describe interrupts, interrupt-names, clock, clock-names
> - updated title section
>
> .../bindings/rtc/renesas,rz-rtca3.yaml | 83 +++++++++++++++++++
> 1 file changed, 83 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rtc/renesas,rz-rtca3.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Error: Documentation/devicetree/bindings/rtc/renesas,rz-rtca3.example.dts:35.47-48 syntax error
FATAL ERROR: Unable to parse input tree
make[2]: *** [scripts/Makefile.dtbs:129: Documentation/devicetree/bindings/rtc/renesas,rz-rtca3.example.dtb] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1442: dt_binding_check] Error 2
make: *** [Makefile:224: __sub-make] Error 2
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20241019084738.3370489-7-claudiu.beznea.uj@bp.renesas.com
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2024-10-19 10:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 8:47 [PATCH v4 00/12] Add RTC support for the Renesas RZ/G3S SoC Claudiu
2024-10-19 8:47 ` [PATCH v4 01/12] dt-bindings: clock: r9a08g045-cpg: Add power domain ID for RTC Claudiu
2024-10-21 7:28 ` Krzysztof Kozlowski
2024-10-24 14:19 ` Geert Uytterhoeven
2024-10-19 8:47 ` [PATCH v4 02/12] clk: renesas: r9a08g045: Add power domain " Claudiu
2024-10-24 14:19 ` Geert Uytterhoeven
2024-10-19 8:47 ` [PATCH v4 03/12] dt-bindings: clock: renesas,r9a08g045-vbattb: Document VBATTB Claudiu
2024-10-21 7:32 ` Krzysztof Kozlowski
2024-10-21 7:34 ` Krzysztof Kozlowski
2024-10-21 7:49 ` Claudiu Beznea
2024-10-21 7:47 ` Claudiu Beznea
2024-10-24 14:21 ` Geert Uytterhoeven
2024-10-19 8:47 ` [PATCH v4 04/12] clk: linux/clk-provider.h: Add devm_clk_hw_register_gate_parent_hw() Claudiu
2024-10-19 8:47 ` [PATCH v4 05/12] clk: renesas: clk-vbattb: Add VBATTB clock driver Claudiu
2024-10-24 14:21 ` Geert Uytterhoeven
2024-10-19 8:47 ` [PATCH v4 06/12] dt-bindings: rtc: renesas,rzg3s-rtc: Document the Renesas RTCA-3 IP Claudiu
2024-10-19 10:32 ` Rob Herring (Arm) [this message]
2024-10-19 8:47 ` [PATCH v4 07/12] rtc: renesas-rtca3: Add driver for RTCA-3 available on Renesas RZ/G3S SoC Claudiu
2024-10-19 16:16 ` Uwe Kleine-König
2024-10-19 8:47 ` [PATCH v4 08/12] arm64: dts: renesas: r9a08g045: Add VBATTB node Claudiu
2024-10-24 14:22 ` Geert Uytterhoeven
2024-10-19 8:47 ` [PATCH v4 09/12] arm64: dts: renesas: r9a08g045: Add RTC node Claudiu
2024-10-24 14:22 ` Geert Uytterhoeven
2024-10-19 8:47 ` [PATCH v4 10/12] arm64: dts: renesas: rzg3s-smarc-som: Enable VBATTB Claudiu
2024-10-24 14:22 ` Geert Uytterhoeven
2024-10-19 8:47 ` [PATCH v4 11/12] arm64: dts: renesas: rzg3s-smarc-som: Enable RTC Claudiu
2024-10-19 8:47 ` [PATCH v4 12/12] arm64: defconfig: Enable VBATTB clock and Renesas RTCA-3 flags Claudiu
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=172933397224.3030070.17299337634844003264.robh@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--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
all inboxes | Powered by JetHome®