public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Akhila YS <akhilayalmati@gmail.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: power: ti,omap3-smartreflex-core: convert to DT schema
Date: Fri, 6 Feb 2026 09:10:01 -0600	[thread overview]
Message-ID: <20260206151001.GA229184-robh@kernel.org> (raw)
In-Reply-To: <20260128-smartreflex-v1-1-2ab7a35169ed@gmail.com>

On Wed, Jan 28, 2026 at 08:11:55AM +0000, Akhila YS wrote:
> Convert Texas Instruments SmartReflex module binding to YAML format.
> 
> Signed-off-by: Akhila YS <akhilayalmati@gmail.com>
> ---
>  .../bindings/power/ti,omap3-smartreflex-core.yaml  | 75 ++++++++++++++++++++++
>  .../devicetree/bindings/power/ti-smartreflex.txt   | 47 --------------
>  2 files changed, 75 insertions(+), 47 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/power/ti,omap3-smartreflex-core.yaml b/Documentation/devicetree/bindings/power/ti,omap3-smartreflex-core.yaml
> new file mode 100644
> index 000000000000..ad4094f15a63
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/ti,omap3-smartreflex-core.yaml
> @@ -0,0 +1,75 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/power/ti,omap3-smartreflex-core.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments SmartReflex module
> +
> +maintainers:
> +  - Tony Lindgren <tony@atomide.com>
> +
> +description:
> +  Texas Instruments SmartReflex is an on-chip adaptive power management
> +  technology integrated into TI's OMAP and other SoCs. It dynamically
> +  adjusts voltage and frequency for different chip domains in real time
> +  to compensate for process, voltage, and temperature (PVT) variations.
> +  Dedicated hardware sensors and control logic continuously monitor
> +  conditions and apply the lowest safe voltage for the required performance
> +  level.
> +
> +properties:
> +  compatible:
> +    enum:
> +      - ti,omap3-smartreflex-core
> +      - ti,omap3-smartreflex-mpu-iva
> +      - ti,omap4-smartreflex-core
> +      - ti,omap4-smartreflex-mpu
> +      - ti,omap4-smartreflex-iva
> +
> +  reg:
> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +
> +  ti,hwmods:
> +    $ref: /schemas/types.yaml#/definitions/string
> +    deprecated: true
> +    description:
> +      It was required by the OMAP interconnect/PRCM code to automatically
> +      initialize hardware modules using TI's internal database.
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> +    smartreflex@4a0db000 {
> +        compatible = "ti,omap4-smartreflex-iva";
> +        reg = <0x4a0db000 0x80>;
> +        interrupts = <GIC_SPI 102 IRQ_TYPE_LEVEL_HIGH>;
> +        ti,hwmods = "smartreflex_iva";

IIRC, ti,hwmods has been removed on omap4.

> +    };
> +
> +  - |
> +    smartreflex@4a0dd000 {
> +        compatible = "ti,omap4-smartreflex-core";
> +        reg = <0x4a0dd000 0x80>;
> +        interrupts = <GIC_SPI 19 IRQ_TYPE_LEVEL_HIGH>;
> +        ti,hwmods = "smartreflex_core";
> +    };
> +
> +  - |
> +    smartreflex@4a0d9000 {
> +        compatible = "ti,omap4-smartreflex-mpu";
> +        reg = <0x4a0d9000 0x80>;
> +        interrupts = <GIC_SPI 18 IRQ_TYPE_LEVEL_HIGH>;
> +        ti,hwmods = "smartreflex_mpu";
> +    };

Just one example is enough.

Rob

  reply	other threads:[~2026-02-06 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28  8:11 [PATCH] dt-bindings: power: ti,omap3-smartreflex-core: convert to DT schema Akhila YS
2026-02-06 15:10 ` Rob Herring [this message]
2026-02-06 16:55   ` Akhila YS

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=20260206151001.GA229184-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=akhilayalmati@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox