From: Sivaram Nair <sivaramn@nvidia.com>
To: Timo Alho <talho@nvidia.com>
Cc: treding@nvidia.com, linux-tegra@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] firmware: tegra: reword messaging terminology
Date: Wed, 12 Dec 2018 12:15:36 -0800 [thread overview]
Message-ID: <20181212201536.GA31765@sdt> (raw)
In-Reply-To: <1544643088-17678-2-git-send-email-talho@nvidia.com>
On Wed, Dec 12, 2018 at 09:31:25PM +0200, Timo Alho wrote:
> As a preparatory change to refactor bpmp driver to support other than
> t186/t194 chip generations, reword and slightly refactor some of the
> functions to better match with what is actually happening in the
> wire-level protocol.
>
> The communication with bpmp is essentially a Remote Procedure Call
> consisting of "request" and "response". Either side (BPMP or CPU) can
> initiate the communication. The state machine for communication
> consists of following steps (from Linux point of view):
>
> Linux initiating the call:
> 1) check that channel is free to transmit a request (is_req_channel_free)
> 2) copy request message payload to shared location
> 3) post the request in channel (post_req)
> 4) notify BPMP that channel state has been update (ring_doorbell)
*updated*
next prev parent reply other threads:[~2018-12-12 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 19:31 [PATCH 0/4] add Tegra210 BPMP driver Timo Alho
2018-12-12 19:31 ` [PATCH 1/4] firmware: tegra: reword messaging terminology Timo Alho
2018-12-12 20:15 ` Sivaram Nair [this message]
2018-12-14 10:27 ` Timo Alho
2018-12-12 19:31 ` [PATCH 2/4] firmware: tegra: refactor bpmp driver Timo Alho
2018-12-12 21:26 ` Sivaram Nair
2018-12-12 19:31 ` [PATCH 3/4] firmware: tegra: add bpmp driver for Tegra210 Timo Alho
2018-12-12 21:31 ` Sivaram Nair
2018-12-12 19:31 ` [PATCH 4/4] dt-bindings: firmware: Add bindings for Tegra210 BPMP Timo Alho
2018-12-20 20:18 ` Rob Herring
2018-12-27 11:19 ` 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=20181212201536.GA31765@sdt \
--to=sivaramn@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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.