From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Peter Geis <pgwipeout@gmail.com>,
Matt Merhar <mattmerhar@protonmail.com>
Cc: linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: devfreq: tegra30-actmon: Add cooling-cells
Date: Tue, 1 Jun 2021 07:32:19 +0300 [thread overview]
Message-ID: <bda7233e-a9e0-7a3d-f6b5-084a49d705ed@gmail.com> (raw)
In-Reply-To: <20210601022319.17938-3-digetx@gmail.com>
01.06.2021 05:23, Dmitry Osipenko пишет:
> The ACTMON watches activity of memory clients. Decisions about a minimum
> required frequency are made based on the info from ACTMON. We can use
> ACTMON as a thermal cooling device by limiting the required frequency.
> Document new cooling-cells property of NVIDIA Tegra ACTMON hardware unit.
>
> Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
> Acked-by: Thierry Reding <treding@nvidia.com>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
I missed to add Rob's r-b to this patch that he gave to v1:
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-06-01 4:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 2:23 [PATCH v2 0/2] Add thermal cooling support to NVIDIA Tegra devfreq Dmitry Osipenko
2021-06-01 2:23 ` [PATCH v2 1/2] dt-bindings: devfreq: tegra30-actmon: Convert to schema Dmitry Osipenko
2021-06-01 2:55 ` Chanwoo Choi
2021-06-01 2:57 ` Dmitry Osipenko
2021-06-01 11:28 ` Thierry Reding
2021-06-01 2:23 ` [PATCH v2 2/2] dt-bindings: devfreq: tegra30-actmon: Add cooling-cells Dmitry Osipenko
2021-06-01 4:32 ` Dmitry Osipenko [this message]
2021-06-01 15:35 ` [PATCH v2 0/2] Add thermal cooling support to NVIDIA Tegra devfreq Chanwoo Choi
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=bda7233e-a9e0-7a3d-f6b5-084a49d705ed@gmail.com \
--to=digetx@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@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;
as well as URLs for NNTP newsgroup(s).