All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
	Andreas Kemnade <andreas@kemnade.info>,
	Kevin Hilman <khilman@baylibre.com>,
	Roger Quadros <rogerq@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Keerthy <j-keerthy@ti.com>, Afzal Mohammed <afzal@ti.com>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org,
	goledhruva@gmail.com, m-chawdhry@ti.com, daniel.baluta@gmail.com,
	simona.toaca@nxp.com
Subject: Re: [PATCH v2 3/3] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema
Date: Mon, 3 Aug 2026 16:27:22 -0500	[thread overview]
Message-ID: <20260803212722.GA575926-robh@kernel.org> (raw)
In-Reply-To: <20260725-ti-omap-rtc-v2-3-13f765ca96b3@gmail.com>

On Sat, Jul 25, 2026 at 02:31:58AM +0530, Bhargav Joshi wrote:
> Convert the Texas Instruments OMAP Real Time Clock (RTC) binding from
> the legacy text format to the DT schema. Mark 'ti,hwmods' as deprecated
> as it is no longer used, it is kept to support legacy boards.
> 
> Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
> ---
>  Documentation/devicetree/bindings/rtc/rtc-omap.txt |  53 --------
>  .../devicetree/bindings/rtc/ti,omap-rtc.yaml       | 149 +++++++++++++++++++++
>  2 files changed, 149 insertions(+), 53 deletions(-)
> 

> diff --git a/Documentation/devicetree/bindings/rtc/ti,omap-rtc.yaml b/Documentation/devicetree/bindings/rtc/ti,omap-rtc.yaml
> new file mode 100644
> index 000000000000..326d5ad97292
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/ti,omap-rtc.yaml
> @@ -0,0 +1,149 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/rtc/ti,omap-rtc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments OMAP Real Time Clock
> +
> +maintainers:
> +  - Keerthy <j-keerthy@ti.com>
> +  - Afzal Mohammed <afzal@ti.com>
> +
> +description:
> +  The OMAP RTC is a year/month/day/hours/minutes/seconds BCD clock with
> +  century-range alarm matching, driven by the 32kHz clock.
> +
> +properties:
> +  compatible:
> +    oneOf:
> +      - const: ti,da830-rtc
> +      - const: ti,am3352-rtc

am3352 is either compatible with da830 or it isn't. You can't have both. 
I would drop this entry. You don't have the fix the .dts (or can do that 
separately).

> +      - items:
> +          - const: ti,am3352-rtc
> +          - const: ti,da830-rtc
> +      - items:
> +          - const: ti,am4372-rtc
> +          - const: ti,am3352-rtc
> +          - const: ti,da830-rtc
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    minItems: 2
> +    maxItems: 2
> +
> +  system-power-controller:
> +    type: boolean
> +    description:
> +      Indicates that this RTC controls system power via the pmic_power_en pin.
> +
> +  clocks:
> +    minItems: 1
> +    maxItems: 2
> +
> +  clock-names:
> +    oneOf:
> +      - items:
> +          - const: ext-clk
> +          - const: int-clk
> +      - items:
> +          - const: ext-clk
> +      - items:
> +          - const: int-clk

This can be just:

minItems: 1
items:
  - enum [ ext-clk, int-clk ]
  - const: int-clk


> +
> +  pinctrl-0:
> +    description:
> +      Phandle to pin configuration for the external wakeup pins.
> +
> +  pinctrl-names:
> +    minItems: 1
> +
> +  ti,hwmods:
> +    $ref: /schemas/types.yaml#/definitions/string
> +    description:
> +      Name of the hwmod associated with the RTC.
> +    const: rtc
> +    deprecated: true
> +
> +patternProperties:
> +  "^ext-wakeup(-[0-9]+)?$":
> +    type: object
> +
> +    description:
> +      Child node describing external wakeup pin configuration.
> +
> +    properties:
> +      pins:
> +        enum:
> +          - ext_wakeup0
> +          - ext_wakeup1
> +          - ext_wakeup2
> +          - ext_wakeup3

pattern: '^ext_wakeup[0-3]$'


      parent reply	other threads:[~2026-08-03 21:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 21:01 [PATCH v2 0/3] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema and cleanups Bhargav Joshi
2026-07-24 21:01 ` [PATCH v2 1/3] ARM: dts: ti: am57xx-idk-common: Remove unused ext-clk-src property Bhargav Joshi
2026-07-24 21:11   ` sashiko-bot
2026-07-24 21:01 ` [PATCH v2 2/3] ARM: dts: ti: am335x-shc: Remove unused ti,no-init property Bhargav Joshi
2026-07-24 21:05   ` sashiko-bot
2026-07-24 21:01 ` [PATCH v2 3/3] dt-bindings: rtc: ti,omap-rtc: Convert to DT schema Bhargav Joshi
2026-07-24 21:08   ` sashiko-bot
2026-08-03 21:27   ` Rob Herring [this message]

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=20260803212722.GA575926-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=afzal@ti.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=goledhruva@gmail.com \
    --cc=j-keerthy@ti.com \
    --cc=j.bhargav.u@gmail.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=m-chawdhry@ti.com \
    --cc=rogerq@kernel.org \
    --cc=simona.toaca@nxp.com \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.