[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1581566330-1029-1-git-send-email-peng.fan@nxp.com>
Date: Thu, 13 Feb 2020 11:58:48 +0800
From: peng.fan@....com
To: sudeep.holla@....com, robh+dt@...nel.org, mark.rutland@....com
Cc: viresh.kumar@...aro.org, f.fainelli@...il.com, linux-imx@....com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, andre.przywara@....com,
Peng Fan <peng.fan@....com>
Subject: [PATCH V2 0/2] firmware: arm_scmi: add smc/hvc transports support
From: Peng Fan <peng.fan@....com>
V2:
patch 1/2: only add smc-id property
patch 2/2: Parse smc/hvc from psci node
Use prot_id as 2nd arg when issue smc/hvc
Differentiate tranports using mboxes or smc-id property
This is to add smc/hvc transports support, based on Viresh's v6.
SCMI firmware could be implemented in EL3, S-EL1, NS-EL2 or other
A core exception level. Then smc/hvc could be used. And for vendor
specific firmware, a wrapper layer could added in EL3, S-EL1,
NS-EL2 and etc to translate SCMI calls to vendor specific firmware calls.
A new compatible string arm,scmi-smc is added. arm,scmi is still for
mailbox transports.
All protocol share same smc/hvc id, the protocol id will be take as
2nd arg when issue smc/hvc.
Each protocol could use its own shmem or share the same shmem
Per smc/hvc, only Tx supported.
Peng Fan (2):
dt-bindings: arm: arm,scmi: add smc/hvc transports
firmware: arm_scmi: add smc/hvc transports
Documentation/devicetree/bindings/arm/arm,scmi.txt | 1 +
drivers/firmware/arm_scmi/Makefile | 2 +-
drivers/firmware/arm_scmi/common.h | 4 +-
drivers/firmware/arm_scmi/driver.c | 11 +-
drivers/firmware/arm_scmi/mailbox.c | 2 +-
drivers/firmware/arm_scmi/smc.c | 222 +++++++++++++++++++++
6 files changed, 235 insertions(+), 7 deletions(-)
create mode 100644 drivers/firmware/arm_scmi/smc.c
--
2.16.4
Powered by blists - more mailing lists