From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Sebastian Reichel <sebastian.reichel@collabora.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH 1/1] dt-bindings: rtc: convert hym8563 bindings to json-schema
Date: Mon, 24 Oct 2022 13:50:49 -0500 [thread overview]
Message-ID: <20221024185049.GA2034297-robh@kernel.org> (raw)
In-Reply-To: <a5db8a34-acd0-e262-36f0-0b904468bd1f@linaro.org>
On Fri, Oct 21, 2022 at 07:59:26PM -0400, Krzysztof Kozlowski wrote:
> On 21/10/2022 13:06, Sebastian Reichel wrote:
> > Convert RTC binding for Haoyu Microelectronics HYM8563 to Device Tree
> > Schema format.
> >
> > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> > ---
> > .../devicetree/bindings/rtc/haoyu,hym8563.txt | 30 ----------
> > .../bindings/rtc/haoyu,hym8563.yaml | 55 +++++++++++++++++++
> > 2 files changed, 55 insertions(+), 30 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/rtc/haoyu,hym8563.txt
> > create mode 100644 Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/rtc/haoyu,hym8563.txt b/Documentation/devicetree/bindings/rtc/haoyu,hym8563.txt
> > deleted file mode 100644
> > index a8934fe2ab4c..000000000000
> > --- a/Documentation/devicetree/bindings/rtc/haoyu,hym8563.txt
> > +++ /dev/null
> > @@ -1,30 +0,0 @@
> > -Haoyu Microelectronics HYM8563 Real Time Clock
> > -
> > -The HYM8563 provides basic rtc and alarm functionality
> > -as well as a clock output of up to 32kHz.
> > -
> > -Required properties:
> > -- compatible: should be: "haoyu,hym8563"
> > -- reg: i2c address
> > -- #clock-cells: the value should be 0
> > -
> > -Optional properties:
> > -- clock-output-names: From common clock binding
> > -- interrupts: rtc alarm/event interrupt
> > -
> > -Example:
> > -
> > -hym8563: hym8563@51 {
> > - compatible = "haoyu,hym8563";
> > - reg = <0x51>;
> > -
> > - interrupts = <13 IRQ_TYPE_EDGE_FALLING>;
> > -
> > - #clock-cells = <0>;
> > -};
> > -
> > -device {
> > -...
> > - clocks = <&hym8563>;
> > -...
> > -};
> > diff --git a/Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml b/Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml
> > new file mode 100644
> > index 000000000000..b0b6126b12dd
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/rtc/haoyu,hym8563.yaml
> > @@ -0,0 +1,55 @@
> > +# SPDX-License-Identifier: GPL-2.0
>
> Dual license please. I don't think you copied any content from original
> bindings... unless the example?
>
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/rtc/haoyu,hym8563.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Haoyu Microelectronics HYM8563 RTC
> > +
> > +maintainers:
> > + - Alexandre Belloni <alexandre.belloni@bootlin.com>
> > +
> > +properties:
> > + compatible:
> > + const: haoyu,hym8563
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > + "#clock-cells":
> > + const: 0
> > +
> > + clock-output-names:
> > + description: From common clock binding to override the default output clock name.
>
> You need maxItems for this.
>
> > +
> > + wakeup-source:
> > + description: Enables wake up of host system on alarm.
> > +
> > +allOf:
> > + - $ref: rtc.yaml
> > +
> > +unevaluatedProperties: false
> > +
>
> Would be great if you could also correct DTS using these bindings (see
> warning from Rob).
It looked to me like 'clock-frequency' should be added to the schema.
Rob
next prev parent reply other threads:[~2022-10-24 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 17:06 [PATCH 1/1] dt-bindings: rtc: convert hym8563 bindings to json-schema Sebastian Reichel
2022-10-21 21:00 ` Rob Herring
2022-10-21 23:59 ` Krzysztof Kozlowski
2022-10-24 18:50 ` Rob Herring [this message]
2022-10-24 22:05 ` Sebastian Reichel
2022-10-27 16:11 ` Johan Jonker
2022-10-27 16:26 ` Sebastian Reichel
2022-10-27 16:29 ` Johan Jonker
2022-10-28 16:19 ` Alexandre Belloni
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=20221024185049.GA2034297-robh@kernel.org \
--to=robh@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=sebastian.reichel@collabora.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).