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: Sudeep Holla <sudeep.holla@arm.com>, Arnd Bergmann <arnd@kernel.org>, Olof Johansson <olof@lixom.net> Subject: [GIT PULL] firmware: arm_ffa: Updates for v6.7 Date: Tue, 10 Oct 2023 13:43:54 +0100 [thread overview] Message-ID: <20231010124354.1620064-1-sudeep.holla@arm.com> (raw) Hi ARM SoC Team, There is a small change in KVM FF-A proxy implementation which is Acked by Marc and agreed to take it as part of the other changes. Please pull ! Regards, Sudeep -->8 The following changes since commit 9dda1178479aa0a73fe0eaabfe2d9a1c603cfeed: firmware: arm_ffa: Don't set the memory region attributes for MEM_LEND (2023-09-25 19:43:49 +0100) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/ffa-updates-6.7 for you to fetch changes up to bcefd1bf63b1ec9bb08067021cf47f0fad96f395: firmware: arm_ffa: Upgrade the driver version to v1.1 (2023-10-08 21:18:48 +0100) ---------------------------------------------------------------- Arm FF-A updates for v6.7 The main addition is the initial support for the notifications and memory transaction descriptor changes added in FF-A v1.1 specification. The notification mechanism enables a requester/sender endpoint to notify a service provider/receiver endpoint about an event with non-blocking semantics. A notification is akin to the doorbell between two endpoints in a communication protocol that is based upon the doorbell/mailbox mechanism. The framework is responsible for the delivery of the notification from the ender to the receiver without blocking the sender. The receiver endpoint relies on the OS scheduler for allocation of CPU cycles to handle a notification. OS is referred as the receiver’s scheduler in the context of notifications. The framework is responsible for informing the receiver’s scheduler that the receiver must be run since it has a pending notification. The series also includes support for the new format of memory transaction descriptors introduced in v1.1 specification. Apart from the main additions, it includes minor fixes to re-enable FF-A drivers usage of 32bit mode of messaging and kernel warning due to the missing assignment of IDR allocation ID to the FFA device. It also adds emitting 'modalias' to the base attribute of FF-A devices. ---------------------------------------------------------------- Sudeep Holla (20): firmware: arm_ffa: Assign the missing IDR allocation ID to the FFA device firmware: arm_ffa: Allow the FF-A drivers to use 32bit mode of messaging firmware: arm_ffa: Emit modalias for FF-A devices firmware: arm_ffa: Update the FF-A command list with v1.1 additions firmware: arm_ffa: Implement notification bitmap create and destroy interfaces firmware: arm_ffa: Implement the notification bind and unbind interface firmware: arm_ffa: Implement the FFA_RUN interface firmware: arm_ffa: Implement the FFA_NOTIFICATION_SET interface firmware: arm_ffa: Implement the FFA_NOTIFICATION_GET interface firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface firmware: arm_ffa: Initial support for scheduler receiver interrupt firmware: arm_ffa: Add schedule receiver callback mechanism firmware: arm_ffa: Add interfaces to request notification callbacks firmware: arm_ffa: Add interface to send a notification to a given partition firmware: arm_ffa: Add notification handling mechanism firmware: arm_ffa: Simplify the computation of transmit and fragment length KVM: arm64: FFA: Remove access of endpoint memory access descriptor array firmware: arm_ffa: Switch to using ffa_mem_desc_offset() accessor firmware: arm_ffa: Update memory descriptor to support v1.1 format firmware: arm_ffa: Upgrade the driver version to v1.1 arch/arm64/kvm/hyp/nvhe/ffa.c | 10 +- drivers/firmware/arm_ffa/bus.c | 16 +- drivers/firmware/arm_ffa/driver.c | 770 +++++++++++++++++++++++++++++++++++++- include/linux/arm_ffa.h | 79 +++- 4 files changed, 840 insertions(+), 35 deletions(-)
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: Sudeep Holla <sudeep.holla@arm.com>, Arnd Bergmann <arnd@kernel.org>, Olof Johansson <olof@lixom.net> Subject: [GIT PULL] firmware: arm_ffa: Updates for v6.7 Date: Tue, 10 Oct 2023 13:43:54 +0100 [thread overview] Message-ID: <20231010124354.1620064-1-sudeep.holla@arm.com> (raw) Hi ARM SoC Team, There is a small change in KVM FF-A proxy implementation which is Acked by Marc and agreed to take it as part of the other changes. Please pull ! Regards, Sudeep -->8 The following changes since commit 9dda1178479aa0a73fe0eaabfe2d9a1c603cfeed: firmware: arm_ffa: Don't set the memory region attributes for MEM_LEND (2023-09-25 19:43:49 +0100) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/ffa-updates-6.7 for you to fetch changes up to bcefd1bf63b1ec9bb08067021cf47f0fad96f395: firmware: arm_ffa: Upgrade the driver version to v1.1 (2023-10-08 21:18:48 +0100) ---------------------------------------------------------------- Arm FF-A updates for v6.7 The main addition is the initial support for the notifications and memory transaction descriptor changes added in FF-A v1.1 specification. The notification mechanism enables a requester/sender endpoint to notify a service provider/receiver endpoint about an event with non-blocking semantics. A notification is akin to the doorbell between two endpoints in a communication protocol that is based upon the doorbell/mailbox mechanism. The framework is responsible for the delivery of the notification from the ender to the receiver without blocking the sender. The receiver endpoint relies on the OS scheduler for allocation of CPU cycles to handle a notification. OS is referred as the receiver’s scheduler in the context of notifications. The framework is responsible for informing the receiver’s scheduler that the receiver must be run since it has a pending notification. The series also includes support for the new format of memory transaction descriptors introduced in v1.1 specification. Apart from the main additions, it includes minor fixes to re-enable FF-A drivers usage of 32bit mode of messaging and kernel warning due to the missing assignment of IDR allocation ID to the FFA device. It also adds emitting 'modalias' to the base attribute of FF-A devices. ---------------------------------------------------------------- Sudeep Holla (20): firmware: arm_ffa: Assign the missing IDR allocation ID to the FFA device firmware: arm_ffa: Allow the FF-A drivers to use 32bit mode of messaging firmware: arm_ffa: Emit modalias for FF-A devices firmware: arm_ffa: Update the FF-A command list with v1.1 additions firmware: arm_ffa: Implement notification bitmap create and destroy interfaces firmware: arm_ffa: Implement the notification bind and unbind interface firmware: arm_ffa: Implement the FFA_RUN interface firmware: arm_ffa: Implement the FFA_NOTIFICATION_SET interface firmware: arm_ffa: Implement the FFA_NOTIFICATION_GET interface firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface firmware: arm_ffa: Initial support for scheduler receiver interrupt firmware: arm_ffa: Add schedule receiver callback mechanism firmware: arm_ffa: Add interfaces to request notification callbacks firmware: arm_ffa: Add interface to send a notification to a given partition firmware: arm_ffa: Add notification handling mechanism firmware: arm_ffa: Simplify the computation of transmit and fragment length KVM: arm64: FFA: Remove access of endpoint memory access descriptor array firmware: arm_ffa: Switch to using ffa_mem_desc_offset() accessor firmware: arm_ffa: Update memory descriptor to support v1.1 format firmware: arm_ffa: Upgrade the driver version to v1.1 arch/arm64/kvm/hyp/nvhe/ffa.c | 10 +- drivers/firmware/arm_ffa/bus.c | 16 +- drivers/firmware/arm_ffa/driver.c | 770 +++++++++++++++++++++++++++++++++++++- include/linux/arm_ffa.h | 79 +++- 4 files changed, 840 insertions(+), 35 deletions(-) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-10-10 12:43 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-10 12:43 Sudeep Holla [this message] 2023-10-10 12:43 ` [GIT PULL] firmware: arm_ffa: Updates for v6.7 Sudeep Holla 2023-10-16 21:31 ` 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=20231010124354.1620064-1-sudeep.holla@arm.com \ --to=sudeep.holla@arm.com \ --cc=arm@kernel.org \ --cc=arnd@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.