summaryrefslogtreecommitdiff
path: root/drivers/firmware/tegra/Kconfig
diff options
context:
space:
mode:
authorThierry Reding <treding@nvidia.com>2016-08-19 19:05:04 +0200
committerThierry Reding <treding@nvidia.com>2016-11-18 14:33:42 +0100
commitca791d7f425635b63706e00896a141f85f7de463 (patch)
treeebb76fa51c8e19d74fdb0e480032687203921f72 /drivers/firmware/tegra/Kconfig
parentd55865608fe0191935665acc6bb6d36bc8bb4b2e (diff)
firmware: tegra: Add IVC library
The Inter-VM communication (IVC) is a communication protocol which is designed for interprocessor communication (IPC) or the communication between the hypervisor and the virtual machine with a guest OS. Message channels are used to communicate between processors. They are backed by DRAM or SRAM, so care must be taken to maintain coherence of data. The IVC library maintains memory-based descriptors for the transmission and reception channels as well as the data coherence of the counter and payload. Clients, such as the driver for the BPMP firmware, can use the library to exchange messages with remote processors. Based on work by Peter Newman <pnewman@nvidia.com> and Joseph Lo <josephl@nvidia.com>. Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'drivers/firmware/tegra/Kconfig')
-rw-r--r--drivers/firmware/tegra/Kconfig13
1 files changed, 13 insertions, 0 deletions
diff --git a/drivers/firmware/tegra/Kconfig b/drivers/firmware/tegra/Kconfig
new file mode 100644
index 000000000000..1fa3e4e136a5
--- /dev/null
+++ b/drivers/firmware/tegra/Kconfig
@@ -0,0 +1,13 @@
+menu "Tegra firmware driver"
+
+config TEGRA_IVC
+ bool "Tegra IVC protocol"
+ depends on ARCH_TEGRA
+ help
+ IVC (Inter-VM Communication) protocol is part of the IPC
+ (Inter Processor Communication) framework on Tegra. It maintains the
+ data and the different commuication channels in SysRAM or RAM and
+ keeps the content is synchronization between host CPU and remote
+ processors.
+
+endmenu