From: Rob Herring <robh@kernel.org>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: "Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Sylwester Nawrocki" <s.nawrocki@samsung.com>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-clk@vger.kernel.org, willmcvicker@google.com,
kernel-team@android.com
Subject: Re: [PATCH 1/3] dt-bindings: firmware: google,gs101-acpm-ipc: add clocks node
Date: Fri, 22 Aug 2025 08:55:21 -0500 [thread overview]
Message-ID: <20250822135521.GA3487754-robh@kernel.org> (raw)
In-Reply-To: <20250819-acpm-clk-v1-1-6bbd97474671@linaro.org>
On Tue, Aug 19, 2025 at 11:45:36AM +0000, Tudor Ambarus wrote:
> The firmware exposes clocks that can be controlled via the ACPM
> interface. Describe the clocks exposed by the APM firmware.
ACPM? APM is Advanced Power Management aka the predecessor to ACPI?
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
> ---
> .../bindings/firmware/google,gs101-acpm-ipc.yaml | 28 ++++++++++++++++++++++
> include/dt-bindings/clock/google,gs101.h | 15 ++++++++++++
> 2 files changed, 43 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/firmware/google,gs101-acpm-ipc.yaml b/Documentation/devicetree/bindings/firmware/google,gs101-acpm-ipc.yaml
> index 9785aac3b5f34955bbfe2718eec48581d050954f..27cdf9c881ca680e78e77a0e14ffcffeba970871 100644
> --- a/Documentation/devicetree/bindings/firmware/google,gs101-acpm-ipc.yaml
> +++ b/Documentation/devicetree/bindings/firmware/google,gs101-acpm-ipc.yaml
> @@ -27,6 +27,29 @@ properties:
> mboxes:
> maxItems: 1
>
> + clocks:
> + description:
> + Clocks that are variable and index based. These clocks don't provide
> + an entire range of values between the limits but only discrete points
> + within the range. The firmware also manages the voltage scaling
> + appropriately with the clock scaling.
> + type: object
> + additionalProperties: false
You don't need a child node. Just add #clock-cells to the parent.
> +
> + properties:
> + compatible:
> + const: google,gs101-acpm-dvfs-clocks
> +
> + "#clock-cells":
> + const: 1
> + description:
> + The argument is the ID of the clock contained by the firmware
> + messages.
> +
> + required:
> + - compatible
> + - "#clock-cells"
> +
> pmic:
> description: Child node describing the main PMIC.
> type: object
> @@ -59,6 +82,11 @@ examples:
> mboxes = <&ap2apm_mailbox>;
> shmem = <&apm_sram>;
>
> + clocks {
> + compatible = "google,gs101-acpm-dvfs-clocks";
> + #clock-cells = <1>;
> + };
> +
> pmic {
> compatible = "samsung,s2mpg10-pmic";
> interrupts-extended = <&gpa0 6 IRQ_TYPE_LEVEL_LOW>;
> diff --git a/include/dt-bindings/clock/google,gs101.h b/include/dt-bindings/clock/google,gs101.h
> index 442f9e9037dc33198a1cee20af62fc70bbd96605..f1d0df412fdd49b300db4ba88bc0b1674cf0cdf8 100644
> --- a/include/dt-bindings/clock/google,gs101.h
> +++ b/include/dt-bindings/clock/google,gs101.h
> @@ -634,4 +634,19 @@
> #define CLK_GOUT_PERIC1_CLK_PERIC1_USI9_USI_CLK 45
> #define CLK_GOUT_PERIC1_SYSREG_PERIC1_PCLK 46
>
> +#define CLK_ACPM_DVFS_MIF 0
> +#define CLK_ACPM_DVFS_INT 1
> +#define CLK_ACPM_DVFS_CPUCL0 2
> +#define CLK_ACPM_DVFS_CPUCL1 3
> +#define CLK_ACPM_DVFS_CPUCL2 4
> +#define CLK_ACPM_DVFS_G3D 5
> +#define CLK_ACPM_DVFS_G3DL2 6
> +#define CLK_ACPM_DVFS_TPU 7
> +#define CLK_ACPM_DVFS_INTCAM 8
> +#define CLK_ACPM_DVFS_TNR 9
> +#define CLK_ACPM_DVFS_CAM 10
> +#define CLK_ACPM_DVFS_MFC 11
> +#define CLK_ACPM_DVFS_DISP 12
> +#define CLK_ACPM_DVFS_BO 13
> +
> #endif /* _DT_BINDINGS_CLOCK_GOOGLE_GS101_H */
>
> --
> 2.51.0.rc1.167.g924127e9c0-goog
>
next prev parent reply other threads:[~2025-08-23 6:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 11:45 [PATCH 0/3] exynos-acpm: add DVFS protocol and clock driver Tudor Ambarus
2025-08-19 11:45 ` [PATCH 1/3] dt-bindings: firmware: google,gs101-acpm-ipc: add clocks node Tudor Ambarus
2025-08-22 13:55 ` Rob Herring [this message]
2025-08-22 15:03 ` Tudor Ambarus
2025-08-24 17:00 ` Krzysztof Kozlowski
2025-08-25 12:01 ` Tudor Ambarus
2025-08-19 11:45 ` [PATCH 2/3] firmware: exynos-acpm: add DVFS protocol Tudor Ambarus
2025-08-24 17:11 ` Krzysztof Kozlowski
2025-08-25 12:02 ` Tudor Ambarus
2025-08-19 11:45 ` [PATCH 3/3] clk: samsung: add Exynos ACPM clock driver Tudor Ambarus
2025-08-21 18:34 ` Brian Masney
2025-08-22 8:14 ` Tudor Ambarus
2025-08-22 10:23 ` Brian Masney
2025-08-22 10:27 ` Tudor Ambarus
2025-08-24 17:10 ` Krzysztof Kozlowski
2025-08-25 12:28 ` Tudor Ambarus
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=20250822135521.GA3487754-robh@kernel.org \
--to=robh@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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.