From: Sudeep Holla <sudeep.holla@arm.com> To: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>, ALKML <linux-arm-kernel@lists.infradead.org> Cc: Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>, Sudeep Holla <sudeep.holla@arm.com>, Olof Johansson <olof@lixom.net> Subject: [GIT PULL] firmware: arm_ffa: Initial support for v5.14 Date: Tue, 1 Jun 2021 10:58:38 +0100 [thread overview] Message-ID: <20210601095838.GA838783@bogus> (raw) Hi ARM SoC Team, Please pull ! This is a new driver pull request. One of the arm64 patch is being pulled from a stable arm64 branch for-next/ffa as the other patches are dependent of the same. Background ---------- This has been on the list for almost a year now with changing requirements. Initially Arm KVM wanted to use this via userspace interface in VMM to communicate with VMs. But it was later dropped in favour of arch-agnostic interface[1]. Also there was some discussion on the dt-bindings which was dropped completely. Though we need to workaround the lack of full discoveribility in v1.0 spec, it is now being fixed for the next version of the spec. Regards, Sudeep [1] https://mirrors.edge.kernel.org/pub/linux/kernel/people/will/slides/kvmforum-2020-edited.pdf -->8 The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5: Linux 5.13-rc1 (2021-05-09 14:17:44 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/arm-ffa-5.14 for you to fetch changes up to cc2195fe536c28e192df5d07e6dd277af36814b4: firmware: arm_ffa: Add support for MEM_* interfaces (2021-05-26 22:38:43 +0100) ---------------------------------------------------------------- Arm Firmware Framework for ARMv8-A(FFA) interface driver The Arm FFA specification describes a software architecture to leverages the virtualization extension to isolate software images provided by an ecosystem of vendors from each other and describes interfaces that standardize communication between the various software images including communication between images in the Secure world and Normal world. Any Hypervisor could use the FFA interfaces to enable communication between VMs it manages. The Hypervisor a.k.a Partition managers in FFA terminology can assign system resources(Memory regions, Devices, CPU cycles) to the partitions and manage isolation amongst them. This is the initial and minimal support for the FFA interface to enable communication between secure partitions and the normal world OS. ---------------------------------------------------------------- Sudeep Holla (6): arm64: smccc: Add support for SMCCCv1.2 extended input/output registers firmware: arm_ffa: Add initial FFA bus support for device enumeration firmware: arm_ffa: Add initial Arm FFA driver support firmware: arm_ffa: Add support for SMCCC as transport to FFA driver firmware: arm_ffa: Setup in-kernel users of FFA partitions firmware: arm_ffa: Add support for MEM_* interfaces MAINTAINERS | 7 + arch/arm64/kernel/asm-offsets.c | 9 + arch/arm64/kernel/smccc-call.S | 57 +++ drivers/firmware/Kconfig | 1 + drivers/firmware/Makefile | 1 + drivers/firmware/arm_ffa/Kconfig | 21 ++ drivers/firmware/arm_ffa/Makefile | 6 + drivers/firmware/arm_ffa/bus.c | 210 +++++++++++ drivers/firmware/arm_ffa/common.h | 31 ++ drivers/firmware/arm_ffa/driver.c | 731 ++++++++++++++++++++++++++++++++++++++ drivers/firmware/arm_ffa/smccc.c | 39 ++ include/linux/arm-smccc.h | 55 +++ include/linux/arm_ffa.h | 267 ++++++++++++++ 13 files changed, 1435 insertions(+) create mode 100644 drivers/firmware/arm_ffa/Kconfig create mode 100644 drivers/firmware/arm_ffa/Makefile create mode 100644 drivers/firmware/arm_ffa/bus.c create mode 100644 drivers/firmware/arm_ffa/common.h create mode 100644 drivers/firmware/arm_ffa/driver.c create mode 100644 drivers/firmware/arm_ffa/smccc.c create mode 100644 include/linux/arm_ffa.h
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com> To: ARM SoC Team <arm@kernel.org>, SoC Team <soc@kernel.org>, ALKML <linux-arm-kernel@lists.infradead.org> Cc: Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>, Sudeep Holla <sudeep.holla@arm.com>, Olof Johansson <olof@lixom.net> Subject: [GIT PULL] firmware: arm_ffa: Initial support for v5.14 Date: Tue, 1 Jun 2021 10:58:38 +0100 [thread overview] Message-ID: <20210601095838.GA838783@bogus> (raw) Message-ID: <20210601095838.ernErqojiMQcU3zdet2QsK76frRFA_6y5A964c236nQ@z> (raw) Hi ARM SoC Team, Please pull ! This is a new driver pull request. One of the arm64 patch is being pulled from a stable arm64 branch for-next/ffa as the other patches are dependent of the same. Background ---------- This has been on the list for almost a year now with changing requirements. Initially Arm KVM wanted to use this via userspace interface in VMM to communicate with VMs. But it was later dropped in favour of arch-agnostic interface[1]. Also there was some discussion on the dt-bindings which was dropped completely. Though we need to workaround the lack of full discoveribility in v1.0 spec, it is now being fixed for the next version of the spec. Regards, Sudeep [1] https://mirrors.edge.kernel.org/pub/linux/kernel/people/will/slides/kvmforum-2020-edited.pdf -->8 The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5: Linux 5.13-rc1 (2021-05-09 14:17:44 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/arm-ffa-5.14 for you to fetch changes up to cc2195fe536c28e192df5d07e6dd277af36814b4: firmware: arm_ffa: Add support for MEM_* interfaces (2021-05-26 22:38:43 +0100) ---------------------------------------------------------------- Arm Firmware Framework for ARMv8-A(FFA) interface driver The Arm FFA specification describes a software architecture to leverages the virtualization extension to isolate software images provided by an ecosystem of vendors from each other and describes interfaces that standardize communication between the various software images including communication between images in the Secure world and Normal world. Any Hypervisor could use the FFA interfaces to enable communication between VMs it manages. The Hypervisor a.k.a Partition managers in FFA terminology can assign system resources(Memory regions, Devices, CPU cycles) to the partitions and manage isolation amongst them. This is the initial and minimal support for the FFA interface to enable communication between secure partitions and the normal world OS. ---------------------------------------------------------------- Sudeep Holla (6): arm64: smccc: Add support for SMCCCv1.2 extended input/output registers firmware: arm_ffa: Add initial FFA bus support for device enumeration firmware: arm_ffa: Add initial Arm FFA driver support firmware: arm_ffa: Add support for SMCCC as transport to FFA driver firmware: arm_ffa: Setup in-kernel users of FFA partitions firmware: arm_ffa: Add support for MEM_* interfaces MAINTAINERS | 7 + arch/arm64/kernel/asm-offsets.c | 9 + arch/arm64/kernel/smccc-call.S | 57 +++ drivers/firmware/Kconfig | 1 + drivers/firmware/Makefile | 1 + drivers/firmware/arm_ffa/Kconfig | 21 ++ drivers/firmware/arm_ffa/Makefile | 6 + drivers/firmware/arm_ffa/bus.c | 210 +++++++++++ drivers/firmware/arm_ffa/common.h | 31 ++ drivers/firmware/arm_ffa/driver.c | 731 ++++++++++++++++++++++++++++++++++++++ drivers/firmware/arm_ffa/smccc.c | 39 ++ include/linux/arm-smccc.h | 55 +++ include/linux/arm_ffa.h | 267 ++++++++++++++ 13 files changed, 1435 insertions(+) create mode 100644 drivers/firmware/arm_ffa/Kconfig create mode 100644 drivers/firmware/arm_ffa/Makefile create mode 100644 drivers/firmware/arm_ffa/bus.c create mode 100644 drivers/firmware/arm_ffa/common.h create mode 100644 drivers/firmware/arm_ffa/driver.c create mode 100644 drivers/firmware/arm_ffa/smccc.c create mode 100644 include/linux/arm_ffa.h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-06-01 9:58 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-01 9:58 Sudeep Holla [this message] 2021-06-01 9:58 ` [GIT PULL] firmware: arm_ffa: Initial support for v5.14 Sudeep Holla 2021-06-14 17:08 ` Sudeep Holla 2021-06-14 17:08 ` Sudeep Holla 2021-06-15 15:21 ` Olof Johansson 2021-06-15 15:21 ` Olof Johansson 2021-06-15 15:34 ` Sudeep Holla 2021-06-15 15:34 ` Sudeep Holla 2021-06-15 16:47 ` Olof Johansson 2021-06-15 16:47 ` Olof Johansson 2021-06-15 19:56 ` Sudeep Holla 2021-06-15 19:56 ` Sudeep Holla 2021-06-15 17:10 ` patchwork-bot+linux-soc
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=20210601095838.GA838783@bogus \ --to=sudeep.holla@arm.com \ --cc=arm@kernel.org \ --cc=arnd@arndb.de \ --cc=khilman@kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=olof@lixom.net \ --cc=soc@kernel.org \ /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: linkBe 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.