From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Vladimir Zapolskiy <vz@mleia.com>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 3/9] dt-bindings: rtc: lpc32xx-rtc: move to trivial-rtc
Date: Tue, 9 Apr 2024 14:11:53 +0200 [thread overview]
Message-ID: <20240409121153e2941468@mail.local> (raw)
In-Reply-To: <6dc808bf-682f-4e91-aac7-7ce6f05a0ab4@gmail.com>
On 09/04/2024 10:52:54+0200, Javier Carrasco wrote:
> On 4/9/24 09:34, Krzysztof Kozlowski wrote:
> > On 08/04/2024 17:53, Javier Carrasco wrote:
> >> This RTC requires a compatible, a reg and a single interrupt,
> >> which makes it suitable for a direct conversion into trivial-rtc.
> >>
> >> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> >> ---
> >> Documentation/devicetree/bindings/rtc/lpc32xx-rtc.txt | 15 ---------------
> >> Documentation/devicetree/bindings/rtc/trivial-rtc.yaml | 2 ++
> >> 2 files changed, 2 insertions(+), 15 deletions(-)
> >
> > This one no... and if you tested DTS you would see errors, although you
> > need to test specific lpc config, not multi_v7.
> >
> > It does not look like you tested the DTS against bindings. Please run
> > `make dtbs_check W=1` (see
> > Documentation/devicetree/bindings/writing-schema.rst or
> > https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/
> > for instructions).
> >
> > Anyway, you *must* check all DTS before moving anything to trivial.
> >
> > Does it mean all other bindings were not checked against DTS at all?
> >
> > Best regards,
> > Krzysztof
> >
> Hi,
>
> I did check the conversion against nxp/lpc/lpc3250-phy3250.dts, which
> throws a message about the 'clocks' property.
>
> That property is not documented in the original binding, and even though
> it could be missing, I could not find any function to get a clock (i.e.
> any form of clk_get()) in rtc-lpc32xx.c, which is the only file where
> the compatible can be found.
>
> Is therefore the property not useless in the dts? My apologies if I am
> missing something here.
The bindings doesn't document the driver but the hardware. In this case,
the only input clock seems to be a 32kHz crystal.
>
> Thanks and best regards,
> Javier Carrasco
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-09 12:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 15:53 [PATCH 0/9] rtc: convert multiple bindings into dtschema Javier Carrasco
2024-04-08 15:53 ` [PATCH 1/9] dt-bindings: rtc: orion-rtc: move to trivial-rtc Javier Carrasco
2024-04-09 7:31 ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 2/9] dt-bindings: rtc: google,goldfish-rtc: " Javier Carrasco
2024-04-09 7:32 ` Krzysztof Kozlowski
2024-04-16 22:45 ` kernel test robot
2024-04-17 8:19 ` Javier Carrasco
2024-04-08 15:53 ` [PATCH 3/9] dt-bindings: rtc: lpc32xx-rtc: " Javier Carrasco
2024-04-09 7:34 ` Krzysztof Kozlowski
2024-04-09 8:52 ` Javier Carrasco
2024-04-09 9:40 ` Krzysztof Kozlowski
2024-04-09 12:11 ` Alexandre Belloni [this message]
2024-04-08 15:53 ` [PATCH 4/9] dt-bindings: rtc: maxim,ds1742: " Javier Carrasco
2024-04-09 7:35 ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 5/9] dt-bindings: rtc: rtc-aspeed: " Javier Carrasco
2024-04-09 7:36 ` Krzysztof Kozlowski
2024-04-09 11:53 ` Andrew Jeffery
2024-04-08 15:53 ` [PATCH 6/9] dt-bindings: rtc: pxa-rtc: convert to dtschema Javier Carrasco
2024-04-09 7:37 ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 7/9] dt-bindings: rtc: spear-rtc: move to trivial-rtc Javier Carrasco
2024-04-09 7:37 ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 8/9] dt-bindings: rtc: stmp3xxx-rtc: convert to dtschema Javier Carrasco
2024-04-09 7:40 ` Krzysztof Kozlowski
2024-04-09 9:22 ` Javier Carrasco
2024-04-09 9:42 ` Krzysztof Kozlowski
2024-04-08 15:53 ` [PATCH 9/9] dt-bindings: rtc: via,vt8500-rtc: move to trivial-rtc Javier Carrasco
2024-04-09 7:40 ` Krzysztof Kozlowski
2024-04-09 10:26 ` [PATCH 0/9] rtc: convert multiple bindings into dtschema Alexandre Belloni
2024-04-09 12:02 ` Javier Carrasco
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=20240409121153e2941468@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=vz@mleia.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).