From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Dmitry Osipenko <digetx@gmail.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 2/8] dt-bindings: devfreq: tegra30-actmon: Add Tegra124 fallback for Tegra210
Date: Thu, 4 Sep 2025 10:09:37 +0200 [thread overview]
Message-ID: <20250904-nice-fresh-lion-0d718b@kuoka> (raw)
In-Reply-To: <20250903-t210-actmon-v2-2-e0d534d4f8ea@gmail.com>
On Wed, Sep 03, 2025 at 02:50:08PM -0500, Aaron Kling wrote:
> The Tegra210 actmon is compatible with the existing Tegra124 driver.
> Describe the compatibles as such.
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> .../devicetree/bindings/devfreq/nvidia,tegra30-actmon.yaml | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-04 8:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 19:50 [PATCH v2 0/8] Support Tegra210 actmon for dynamic EMC scaling Aaron Kling via B4 Relay
2025-09-03 19:50 ` [PATCH v2 1/8] dt-bindings: memory: tegra210: Add memory client IDs Aaron Kling via B4 Relay
2025-09-04 8:20 ` Krzysztof Kozlowski
2025-09-04 17:33 ` Aaron Kling
2025-09-05 6:56 ` Krzysztof Kozlowski
2025-09-05 7:18 ` Aaron Kling
2025-09-03 19:50 ` [PATCH v2 2/8] dt-bindings: devfreq: tegra30-actmon: Add Tegra124 fallback for Tegra210 Aaron Kling via B4 Relay
2025-09-04 8:09 ` Krzysztof Kozlowski [this message]
2025-09-06 15:58 ` Chanwoo Choi
2025-09-03 19:50 ` [PATCH v2 3/8] dt-bindings: memory: tegra210: emc: Document OPP table and interconnect Aaron Kling via B4 Relay
2025-09-04 8:11 ` Krzysztof Kozlowski
2025-09-06 17:22 ` Aaron Kling
2025-09-03 19:50 ` [PATCH v2 4/8] soc: tegra: fuse: speedo-tegra210: Add soc speedo 2 Aaron Kling via B4 Relay
2025-09-03 19:50 ` [PATCH v2 5/8] memory: tegra210: Support interconnect framework Aaron Kling via B4 Relay
2025-09-04 8:17 ` Krzysztof Kozlowski
2025-09-04 17:28 ` Aaron Kling
2025-09-05 6:59 ` Krzysztof Kozlowski
2025-09-03 19:50 ` [PATCH v2 6/8] arm64: tegra: tegra210: Add actmon Aaron Kling via B4 Relay
2025-09-03 19:50 ` [PATCH v2 7/8] arm64: tegra: Add interconnect properties to Tegra210 device-tree Aaron Kling via B4 Relay
2025-09-03 19:50 ` [PATCH v2 8/8] arm64: tegra: Add OPP tables on Tegra210 Aaron Kling via B4 Relay
2025-09-04 8:08 ` [PATCH v2 0/8] Support Tegra210 actmon for dynamic EMC scaling Krzysztof Kozlowski
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=20250904-nice-fresh-lion-0d718b@kuoka \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=webgeek1234@gmail.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