From: Rob Herring <robh@kernel.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: "Matt Merhar" <mattmerhar@protonmail.com>,
"Nicolas Chauvet" <kwizart@gmail.com>,
linux-kernel@vger.kernel.org,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org,
"Peter Geis" <pgwipeout@gmail.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Paul Fertser" <fercerpav@gmail.com>,
devicetree@vger.kernel.org, "Viresh Kumar" <vireshk@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Stephen Boyd" <sboyd@kernel.org>
Subject: Re: [PATCH v5 1/3] dt-bindings: soc: tegra-pmc: Document core power domain
Date: Tue, 18 May 2021 09:20:09 -0500 [thread overview]
Message-ID: <20210518142009.GA617606@robh.at.kernel.org> (raw)
In-Reply-To: <20210516231755.24193-2-digetx@gmail.com>
On Mon, 17 May 2021 02:17:53 +0300, Dmitry Osipenko wrote:
> All NVIDIA Tegra SoCs have a core power domain where majority of hardware
> blocks reside. Document the new core power domain properties.
>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
> .../arm/tegra/nvidia,tegra20-pmc.yaml | 35 +++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-05-18 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 23:17 [PATCH v5 0/3] Add support for NVIDIA Tegra SoC core power domain Dmitry Osipenko
2021-05-16 23:17 ` [PATCH v5 1/3] dt-bindings: soc: tegra-pmc: Document " Dmitry Osipenko
2021-05-18 14:20 ` Rob Herring [this message]
2021-05-16 23:17 ` [PATCH v5 2/3] soc/tegra: pmc: Add " Dmitry Osipenko
2021-05-31 12:36 ` Thierry Reding
2021-05-31 20:28 ` Dmitry Osipenko
2021-05-16 23:17 ` [PATCH v5 3/3] soc/tegra: regulators: Support Core domain state syncing Dmitry Osipenko
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=20210518142009.GA617606@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=fercerpav@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kwizart@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=vireshk@kernel.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 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.