devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Timo Alho <talho@nvidia.com>
Cc: jonathanh@nvidia.com, treding@nvidia.com, sivaramn@nvidia.com,
	robh@kernel.org, linux-tegra@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH V3 0/4] add Tegra210 BPMP driver
Date: Fri, 25 Jan 2019 15:57:42 +0100	[thread overview]
Message-ID: <20190125145742.GF22565@ulmo> (raw)
In-Reply-To: <1548349435-1086-1-git-send-email-talho@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

On Thu, Jan 24, 2019 at 07:03:51PM +0200, Timo Alho wrote:
> Hi,
> 
> This is a third version of "add Tegra210 BPMP driver" series. In additIt
> incorporates the review feedback received from Jon Hunter for patches
> 2, 3, and 4.
> 
> 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

Patches 1-3 applied to for-5.1/firmware and patch 4 applied to
for-5.1/dt-bindings, thanks.

I did apply some last-minute bike shedding (s/bpmp/BPMP/, make ops
structure pointers const, spelled out req -> request and resp ->
response, ...). I also renamed the bpmp-tXYZ.c files to bpmp-tegraXYZ
for consistency with other drivers.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2019-01-25 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 17:03 [PATCH V3 0/4] add Tegra210 BPMP driver Timo Alho
2019-01-24 17:03 ` [PATCH V3 1/4] firmware: tegra: reword messaging terminology Timo Alho
2019-01-24 17:03 ` [PATCH V3 2/4] firmware: tegra: refactor bpmp driver Timo Alho
2019-01-24 18:24   ` Jon Hunter
2019-01-24 17:03 ` [PATCH V3 3/4] firmware: tegra: add bpmp driver for Tegra210 Timo Alho
2019-01-25 13:34   ` Jon Hunter
2019-01-24 17:03 ` [PATCH V3 4/4] dt-bindings: firmware: Add bindings for Tegra210 BPMP Timo Alho
2019-01-24 18:29   ` Jon Hunter
2019-01-24 18:40     ` Timo Alho
2019-01-25 14:57 ` Thierry Reding [this message]

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=20190125145742.GF22565@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robh@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 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).