From: Conor Dooley <conor@kernel.org>
To: Bryan Brattlof <bb@ti.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Vibhore Vardhan <vibhore@ti.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/5] DONOTMERGE: dt-bindings: mfd: syscon: add TI's opp table compatible
Date: Wed, 12 Jun 2024 17:51:13 +0100 [thread overview]
Message-ID: <20240612-unranked-unsalted-b32674a98d4a@spud> (raw)
In-Reply-To: <20240612-ti-opp-updates-v1-3-3551c31d9872@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
On Wed, Jun 12, 2024 at 11:41:52AM -0500, Bryan Brattlof wrote:
> The JTAG_USER_ID_USERCODE efuse address, which is located inside the
> WKUP_CTRL_MMR0 range holds information to identify the speed grades of
> various components on TI's K3 SoCs. Add a compatible to allow the
> cpufreq driver to obtain the data to limit the maximum frequency for the
> CPUs under Linux control.
>
> Signed-off-by: Bryan Brattlof <bb@ti.com>
$subject: DONOTMERGE: dt-bindings: mfd: syscon: add TI's opp table compatible
Okay, if this isn't for merging then I won't Ack it.
Thanks,
Conor.
> ---
> Documentation/devicetree/bindings/mfd/syscon.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
> index 7ed12a938baa3..ab1fcbe2148f7 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
> @@ -88,6 +88,7 @@ properties:
> - rockchip,rv1126-qos
> - starfive,jh7100-sysmain
> - ti,am62-usb-phy-ctrl
> + - ti,am62-opp-efuse-table
> - ti,am62p-cpsw-mac-efuse
> - ti,am654-dss-oldi-io-ctrl
> - ti,am654-serdes-ctrl
>
> --
> 2.45.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-12 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 16:41 [PATCH 0/5] Update OPP table and add entries for AM62Ax & AM62Px SoCs Bryan Brattlof
2024-06-12 16:41 ` [PATCH 1/5] cpufreq: ti: update OPP table for AM62Ax SoCs Bryan Brattlof
2024-06-12 16:41 ` [PATCH 2/5] cpufreq: ti: update OPP table for AM62Px SoCs Bryan Brattlof
2024-06-12 16:41 ` [PATCH 3/5] DONOTMERGE: dt-bindings: mfd: syscon: add TI's opp table compatible Bryan Brattlof
2024-06-12 16:51 ` Conor Dooley [this message]
2024-06-12 17:54 ` Bryan Brattlof
2024-06-13 12:09 ` Lee Jones
2024-06-13 12:20 ` Conor Dooley
2024-06-13 13:13 ` Krzysztof Kozlowski
2024-06-13 17:30 ` Lee Jones
2024-06-15 14:43 ` Bryan Brattlof
2024-06-12 16:41 ` [PATCH 4/5] DONOTMERGE: arm64: dts: ti: k3-am62p: add in opp tables Bryan Brattlof
2024-06-12 16:41 ` [PATCH 5/5] DONOTMERGE: arm64: dts: ti: k3-am62a: add in opp table Bryan Brattlof
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=20240612-unranked-unsalted-b32674a98d4a@spud \
--to=conor@kernel.org \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=vibhore@ti.com \
--cc=vigneshr@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).