From: Rob Herring <robh@kernel.org>
To: Timo Alho <talho@nvidia.com>
Cc: treding@nvidia.com, sivaramn@nvidia.com, robh@kernel.org,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH V2 4/4] dt-bindings: firmware: Add bindings for Tegra210 BPMP
Date: Mon, 21 Jan 2019 11:38:49 -0600 [thread overview]
Message-ID: <20190121173849.GA17553@bogus> (raw)
In-Reply-To: <1548073731-6449-5-git-send-email-talho@nvidia.com>
On Mon, 21 Jan 2019 14:28:51 +0200, Timo Alho wrote:
> The BPMP is a specific processor in Tegra210 chip, which is designed
> for boot process handling, assisting in entering deep low power states
> (suspend to ram), and offloading DRAM memory clock scaling on some
> platforms.
>
> Signed-off-by: Timo Alho <talho@nvidia.com>
> ---
> .../bindings/firmware/nvidia,tegra210-bpmp.txt | 36 ++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/firmware/nvidia,tegra210-bpmp.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-01-21 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 12:28 [PATCH V2 0/4] add Tegra210 BPMP driver Timo Alho
2019-01-21 12:28 ` [PATCH V2 1/4] firmware: tegra: reword messaging terminology Timo Alho
2019-01-24 11:33 ` Jon Hunter
2019-01-24 12:25 ` Timo Alho
2019-01-21 12:28 ` [PATCH V2 2/4] firmware: tegra: refactor bpmp driver Timo Alho
2019-01-24 11:45 ` Jon Hunter
2019-01-24 14:26 ` Timo Alho
2019-01-21 12:28 ` [PATCH V2 3/4] firmware: tegra: add bpmp driver for Tegra210 Timo Alho
2019-01-24 12:16 ` Jon Hunter
2019-01-24 13:41 ` Timo Alho
2019-01-24 13:57 ` Jon Hunter
2019-01-21 12:28 ` [PATCH V2 4/4] dt-bindings: firmware: Add bindings for Tegra210 BPMP Timo Alho
2019-01-21 17:38 ` Rob Herring [this message]
2019-01-24 12:19 ` Jon Hunter
2019-01-24 13:02 ` Jon Hunter
2019-01-24 14:49 ` Timo Alho
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=20190121173849.GA17553@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sivaramn@nvidia.com \
--cc=talho@nvidia.com \
--cc=treding@nvidia.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.