From: Rob Herring <robh@kernel.org>
To: daire.mcnamara@microchip.com
Cc: a.zummo@towertech.it, alexandre.belloni@bootlin.com,
linux-rtc@vger.kernel.org, devicetree@vger.kernel.org,
palmer@dabbelt.com, cyril.jean@microchip.com,
padmarao.begari@microchip.com, lewis.hanly@microchip.com,
conor.dooley@microchip.com, david.abdurachmanov@gmail.com
Subject: Re: [PATCH v1 1/2] dt-bindings: rtc: microchip: Add Microchip PolarFire host binding
Date: Wed, 12 May 2021 21:22:49 -0500 [thread overview]
Message-ID: <20210513022249.GA896078@robh.at.kernel.org> (raw)
In-Reply-To: <20210512111133.1650740-2-daire.mcnamara@microchip.com>
On Wed, May 12, 2021 at 12:11:32PM +0100, daire.mcnamara@microchip.com wrote:
> From: Daire McNamara <daire.mcnamara@microchip.com>
>
> Add device tree bindings for the Microchip PolarFire real-time
> clock controller
>
> Signed-off-by: Daire McNamara <daire.mcnamara@microchip.com>
> ---
> .../bindings/rtc/microchip,mfps-rtc.yaml | 61 +++++++++++++++++++
> 1 file changed, 61 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/rtc/microchip,mfps-rtc.yaml
>
> diff --git a/Documentation/devicetree/bindings/rtc/microchip,mfps-rtc.yaml b/Documentation/devicetree/bindings/rtc/microchip,mfps-rtc.yaml
> new file mode 100644
> index 000000000000..c82b3e7351e0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/microchip,mfps-rtc.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/rtc/microchip,mfps-rtc.yaml#
> +
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Microchip PolarFire Soc (MPFS) RTC Device Tree Bindings
> +
> +allOf:
> + - $ref: "rtc.yaml#"
> +
> +maintainers:
> + - Daire McNamara <daire.mcnamara@microchip.com>
> + - Lewis Hanly <lewis.hanly@microchip.com>
> +
> +properties:
> + compatible:
> + enum:
> + - microchip,mpfs-rtc
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + prescaler:
> + maxItems: 1
An array?
Needs a type, constraints, and vendor prefix.
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + items:
> + - const: rtc
Kind of a pointless name. You don't need *-names when there is only 1.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/microchip,mpfs-clock.h>
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + rtc@20124000 {
> + compatible = "microchip,mpfs-rtc";
> + reg = <0 0x20124000 0 0x1000>;
> + clocks = <&clkcfg CLK_RTC>;
> + clock-names = "rtc";
> + interrupts = <80>;
> + };
> + };
> +...
> --
> 2.25.1
>
next prev parent reply other threads:[~2021-05-13 2:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 11:11 [PATCH v1 0/2] rtc: microchip: Add driver for PolarFire SoC daire.mcnamara
2021-05-12 11:11 ` [PATCH v1 1/2] dt-bindings: rtc: microchip: Add Microchip PolarFire host binding daire.mcnamara
2021-05-12 18:35 ` Rob Herring
2021-05-13 2:22 ` Rob Herring [this message]
2021-05-12 11:11 ` [PATCH v1 2/2] rtc: microchip: Add driver for Microchip PolarFire SoC daire.mcnamara
2021-05-12 22:18 ` 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=20210513022249.GA896078@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=david.abdurachmanov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=lewis.hanly@microchip.com \
--cc=linux-rtc@vger.kernel.org \
--cc=padmarao.begari@microchip.com \
--cc=palmer@dabbelt.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).