linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	 Sudeep Holla <sudeep.holla@arm.com>,
	 Jens Wiklander <jens.wiklander@linaro.org>,
	 Marc Bonnici <marc.bonnici@arm.com>,
	Coboy Chen <coboy.chen@mediatek.com>,
	 Lorenzo Pieralisi <lpieralisi@kernel.org>,
	 Olivier Deprez <olivier.deprez@arm.com>
Cc: Joao Alves <joao.alves@arm.com>, Marc Zyngier <maz@kernel.org>,
	 Oliver Upton <oliver.upton@linux.dev>,
	Will Deacon <will@kernel.org>,
	 Quentin Perret <qperret@google.com>
Subject: [PATCH RFT v2 00/18] firmware: arm_ffa: Add FF-A v1.1 support(notification + new memory descriptor format)
Date: Tue, 19 Sep 2023 18:40:48 +0100	[thread overview]
Message-ID: <20230919-ffa_v1-1_notif-v2-0-6f3a3ca3923c@arm.com> (raw)

The series adds 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
sender 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.

It also contains one fix for MEMORY LEND operation.

v1[1]->v2:
	- Added a fix for MEMORY LEND operation
	- Upgraded the driver version
	- Added support for the new format of memory transaction descriptors
	- Remove unnecessary partition ID information in the notification
	  callbacks
	- Fixed setting up drv_info->sched_recv_irq before enabling the SGIs
	- Added missing resetting of bitmap_created in notifications_cleanup()
	- Added some comments about GICv3 and SGI assumption
	- Removed partition ID from the notification hash table entries as
	  they are redundant/incorrect. Added the notification type instead
	  (SP/VM/Framework)
	-

[1] https://lore.kernel.org/all/20230803-ffa_v1-1_notif-v1-0-6613ff2b1f81@arm.com/

Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
---
Sudeep Holla (18):
      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: Don't set the memory region attributes for MEM_LEND
      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     |   8 +-
 drivers/firmware/arm_ffa/driver.c | 769 +++++++++++++++++++++++++++++++++++++-
 include/linux/arm_ffa.h           |  76 +++-
 3 files changed, 827 insertions(+), 26 deletions(-)
---
base-commit: ce9ecca0238b140b88f43859b211c9fdfd8e5b70
change-id: 20230803-ffa_v1-1_notif-e11bc9459962

Best regards,
-- 
Regards,
Sudeep


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-09-19 17:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 17:40 Sudeep Holla [this message]
2023-09-19 17:40 ` [PATCH RFT v2 01/18] firmware: arm_ffa: Update the FF-A command list with v1.1 additions Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 02/18] firmware: arm_ffa: Implement notification bitmap create and destroy interfaces Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 03/18] firmware: arm_ffa: Implement the notification bind and unbind interface Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 04/18] firmware: arm_ffa: Implement the FFA_RUN interface Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 05/18] firmware: arm_ffa: Implement the FFA_NOTIFICATION_SET interface Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 06/18] firmware: arm_ffa: Implement the FFA_NOTIFICATION_GET interface Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 07/18] firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 08/18] firmware: arm_ffa: Initial support for scheduler receiver interrupt Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 09/18] firmware: arm_ffa: Add schedule receiver callback mechanism Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 10/18] firmware: arm_ffa: Add interfaces to request notification callbacks Sudeep Holla
2023-09-19 17:40 ` [PATCH RFT v2 11/18] firmware: arm_ffa: Add interface to send a notification to a given partition Sudeep Holla
2023-09-19 17:41 ` [PATCH RFT v2 12/18] firmware: arm_ffa: Add notification handling mechanism Sudeep Holla
2023-09-19 17:41 ` [PATCH RFT v2 13/18] firmware: arm_ffa: Don't set the memory region attributes for MEM_LEND Sudeep Holla
2023-09-19 17:41 ` [PATCH RFT v2 14/18] firmware: arm_ffa: Simplify the computation of transmit and fragment length Sudeep Holla
2023-09-19 17:41 ` [PATCH RFT v2 15/18] KVM: arm64: FFA: Remove access of endpoint memory access descriptor array Sudeep Holla
2023-09-19 17:41 ` [PATCH RFT v2 16/18] firmware: arm_ffa: Switch to using ffa_mem_desc_offset() accessor Sudeep Holla
2023-09-19 17:41 ` [PATCH RFT v2 17/18] firmware: arm_ffa: Update memory descriptor to support v1.1 format Sudeep Holla
2023-09-19 17:41 ` [PATCH RFT v2 18/18] firmware: arm_ffa: Upgrade the driver version to v1.1 Sudeep Holla

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=20230919-ffa_v1-1_notif-v2-0-6f3a3ca3923c@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=coboy.chen@mediatek.com \
    --cc=jens.wiklander@linaro.org \
    --cc=joao.alves@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=marc.bonnici@arm.com \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=olivier.deprez@arm.com \
    --cc=qperret@google.com \
    --cc=will@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: 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;
as well as URLs for NNTP newsgroup(s).