From: Timo Alho <talho@nvidia.com>
To: treding@nvidia.com, sivaramn@nvidia.com, robh@kernel.org
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
Timo Alho <talho@nvidia.com>
Subject: [PATCH V2 0/4] add Tegra210 BPMP driver
Date: Mon, 21 Jan 2019 14:28:47 +0200 [thread overview]
Message-ID: <1548073731-6449-1-git-send-email-talho@nvidia.com> (raw)
Hi,
This is a second version of "add Tegra210 BPMP driver" series. It has
only some minor updates to original series based on feedback received
from Sivaram Nair and Rob Herring. The original cover letter of patch
series one is below.
This series adds a driver for Tegra210 BPMP firmware. The BPMP is a
specific processor in Tegra210 chip, which runs firmware for assisting
in entering deep low power states (suspend to ram), and offloading
DRAM memory clock scaling on some platforms.
The series consist of first refactoring the existing BPMP driver by
first renaming the terminology used for communication, then splitting
out the Tegra186 chip specific parts, and finally adding the needed
functionality for Tegra210.
Timo Alho (4):
firmware: tegra: reword messaging terminology
firmware: tegra: refactor bpmp driver
firmware: tegra: add bpmp driver for Tegra210
dt-bindings: firmware: Add bindings for Tegra210 BPMP
.../bindings/firmware/nvidia,tegra210-bpmp.txt | 36 +++
drivers/firmware/tegra/Makefile | 2 +
drivers/firmware/tegra/bpmp-private.h | 29 ++
drivers/firmware/tegra/bpmp-t186.c | 303 +++++++++++++++++
drivers/firmware/tegra/bpmp-t210.c | 241 ++++++++++++++
drivers/firmware/tegra/bpmp.c | 359 ++++++++-------------
include/soc/tegra/bpmp.h | 13 +-
7 files changed, 751 insertions(+), 232 deletions(-)
create mode 100644 Documentation/devicetree/bindings/firmware/nvidia,tegra210-bpmp.txt
create mode 100644 drivers/firmware/tegra/bpmp-private.h
create mode 100644 drivers/firmware/tegra/bpmp-t186.c
create mode 100644 drivers/firmware/tegra/bpmp-t210.c
--
2.7.4
next reply other threads:[~2019-01-21 12:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 12:28 Timo Alho [this message]
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
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=1548073731-6449-1-git-send-email-talho@nvidia.com \
--to=talho@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sivaramn@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 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).