From: Rob Herring <robh@kernel.org>
To: Nishanth Menon <nm@ti.com>
Cc: "Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Vibhore Vardhan" <vibhore@ti.com>, "Dhruva Gole" <d-gole@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 5/5] dt-bindings: cpufreq: Convert ti-cpufreq.txt to yaml binding
Date: Wed, 26 Jul 2023 11:14:36 -0600 [thread overview]
Message-ID: <20230726171436.GA1609063-robh@kernel.org> (raw)
In-Reply-To: <20230724153911.1376830-6-nm@ti.com>
On Mon, Jul 24, 2023 at 10:39:11AM -0500, Nishanth Menon wrote:
> Move the ti-cpufreq binding over to opp and convert to yaml
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> .../bindings/cpufreq/ti-cpufreq.txt | 132 ------------------
> .../bindings/opp/opp-v2-ti-cpu.yaml | 88 ++++++++++++
> 2 files changed, 88 insertions(+), 132 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt
> create mode 100644 Documentation/devicetree/bindings/opp/opp-v2-ti-cpu.yaml
> diff --git a/Documentation/devicetree/bindings/opp/opp-v2-ti-cpu.yaml b/Documentation/devicetree/bindings/opp/opp-v2-ti-cpu.yaml
> new file mode 100644
> index 000000000000..758f6da619a8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/opp/opp-v2-ti-cpu.yaml
Filename matching the compatible.
> @@ -0,0 +1,88 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/opp/opp-v2-ti-cpu.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: TI CPU OPP
> +
> +description: |
Don't need '|'.
> + Certain TI SoCs, like those in the am335x, am437x, am57xx, am62x and dra7xx
> + families support different OPPs depending on the silicon variant in use.
> + The ti-cpufreq driver can use revision and an efuse value from the SoC to
> + provide the OPP framework with supported hardware information. This is
> + used to determine which OPPs from the operating-points-v2 table get enabled
> + when it is parsed by the OPP framework.
> +
> +maintainers:
> + - Nishanth Menon <nm@ti.com>
> +
> +allOf:
> + - $ref: opp-v2-base.yaml#
> +
> +properties:
> + compatible:
> + const: operating-points-v2-ti-cpu
> +
> + syscon:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: |
> + points to syscon node representing the control module
> + register space of the SoC.
> +
> + opp-shared: true
> +
> +patternProperties:
> + '^opp(-?[0-9]+)*$':
> + type: object
> + additionalProperties: false
> +
> + properties:
> + clock-latency-ns: true
> + opp-hz: true
> + opp-microvolt: true
> + opp-supported-hw: true
> + opp-suspend: true
> + turbo-mode: true
> +
> + required:
> + - opp-hz
> + - opp-supported-hw
> +
> +required:
> + - compatible
> + - syscon
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + cpu0_opp_table: opp-table {
Drop unused labels
> + compatible = "operating-points-v2-ti-cpu";
> + syscon = <&scm_conf>;
> +
> + opp-300000000 {
> + opp-hz = /bits/ 64 <300000000>;
> + opp-microvolt = <1100000 1078000 1122000>;
> + opp-supported-hw = <0x06 0x0020>;
> + opp-suspend;
> + };
> +
> + opp-500000000 {
> + opp-hz = /bits/ 64 <500000000>;
> + opp-microvolt = <1100000 1078000 1122000>;
> + opp-supported-hw = <0x01 0xFFFF>;
> + };
> +
> + opp-600000000 {
> + opp-hz = /bits/ 64 <600000000>;
> + opp-microvolt = <1100000 1078000 1122000>;
> + opp-supported-hw = <0x06 0x0040>;
> + };
> +
> + opp-1000000000 {
> + opp-hz = /bits/ 64 <1000000000>;
> + opp-microvolt = <1325000 1298500 1351500>;
> + opp-supported-hw = <0x04 0x0200>;
> + };
> + };
> --
> 2.40.0
>
next prev parent reply other threads:[~2023-07-26 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 15:39 [PATCH 0/5] dt-bindings: opp/cpufreq: Convert ti-cpufreq to Nishanth Menon
2023-07-24 15:39 ` [PATCH 1/5] arm: dts: ti: omap: omap36xx: Rename opp_supply nodename Nishanth Menon
2023-07-28 7:52 ` Dhruva Gole
2023-07-24 15:39 ` [PATCH 2/5] arm: dts: ti: omap: am5729-beagleboneai: Drop the OPP Nishanth Menon
2023-07-24 15:39 ` [PATCH 3/5] arm: dts: ti: omap: Fix OPP table node names Nishanth Menon
2023-07-31 6:25 ` Tony Lindgren
2023-07-24 15:39 ` [PATCH 4/5] dt-bindings: opp: Convert ti-omap5-opp-supply.txt to yaml binding Nishanth Menon
2023-07-26 17:10 ` Rob Herring
2023-07-26 19:15 ` Nishanth Menon
2023-07-24 15:39 ` [PATCH 5/5] dt-bindings: cpufreq: Convert ti-cpufreq.txt " Nishanth Menon
2023-07-26 17:14 ` Rob Herring [this message]
2023-07-26 19:17 ` Nishanth Menon
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=20230726171436.GA1609063-robh@kernel.org \
--to=robh@kernel.org \
--cc=bcousson@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=tony@atomide.com \
--cc=vibhore@ti.com \
--cc=viresh.kumar@linaro.org \
/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).