From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: add IVC protocol implementation
Date: Mon, 25 Jul 2016 13:57:58 -0600 [thread overview]
Message-ID: <57966F46.8050506@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ0dXVVYLmZQqHgb3HA0pdr0oV+AYqhPf9LD7-uu2RWznQ@mail.gmail.com>
On 07/22/2016 08:08 PM, Simon Glass wrote:
> Hi Stephen,
>
> On 18 July 2016 at 12:17, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> IVC (Inter-VM Communication) protocol is a Tegra-specific IPC (Inter
>> Processor Communication) framework. Within the context of U-Boot, it is
>> typically used for communication between the main CPU and various
>> auxiliary processors. In particular, it will be used to communicate with
>> the BPMP (Boot and Power Management Processor) on Tegra186 in order to
>> manipulate clocks and reset signals.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>> This depends on "ARM: tegra: unify Tegra186 Makefile a bit" (which I just
>> sent) purely for a tiny bit of diff context in the Makefile. Otherwise,
>> it's entirely independent.
>>
>> arch/arm/include/asm/arch-tegra/ivc.h | 179 +++++++++++
>> arch/arm/mach-tegra/Kconfig | 9 +
>> arch/arm/mach-tegra/Makefile | 1 +
>> arch/arm/mach-tegra/ivc.c | 553 ++++++++++++++++++++++++++++++++++
>> 4 files changed, 742 insertions(+)
>> create mode 100644 arch/arm/include/asm/arch-tegra/ivc.h
>> create mode 100644 arch/arm/mach-tegra/ivc.c
>
> Can this use driver model? It seems different from remoteproc. Maybe
> mailbox or blk?
This code is essentially utility/implementation code that will be called
from a "DM-enabled" driver. The BPMP driver will be instantiated from DT
like any other device, and will "host"/use an IVC channel, hence call
the IVC code.
next prev parent reply other threads:[~2016-07-25 19:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 18:17 [U-Boot] [PATCH] ARM: tegra: add IVC protocol implementation Stephen Warren
2016-07-23 2:08 ` Simon Glass
2016-07-25 19:57 ` Stephen Warren [this message]
2016-08-05 1:36 ` Simon Glass
2016-08-05 16:04 ` Stephen Warren
2016-08-06 1:40 ` Simon Glass
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=57966F46.8050506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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