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> Subject: [GIT PULL] firmware: arm_ffa: Fixes for v6.7 Date: Thu, 16 Nov 2023 19:16:03 +0000 [thread overview] Message-ID: <20231116191603.929767-1-sudeep.holla@arm.com> (raw) Hi ARM SoC Team, Please pull ! Regards, Sudeep -->8 The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86: Linux 6.7-rc1 (2023-11-12 16:19:07 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/ffa-fixes-6.7 for you to fetch changes up to f1ed48ef97e2d12dee21e42db4a6ebb895ed3a79: firmware: arm_ffa: Fix ffa_notification_info_get() IDs handling (2023-11-13 11:51:26 +0000) ---------------------------------------------------------------- Arm FF-A fixes for v6.7 A bunch of fixes addressing issues around the notification support that was added this cycle. They address issue in partition IDs handling in ffa_notification_info_get(), notifications cleanup path and the size of the allocation in ffa_partitions_cleanup(). It also adds check for the notification enabled state so that the drivers registering the callbacks can be rejected if not enabled/supported. It also moves the partitions setup operation after the notification initialisation so that the driver has the correct state for notification enabled/supported before the partitions are initialised/setup. It also now allows FF-A initialisation to complete successfully even when the notification initialisation fails as it is an optional support in the specification. Initial support just allowed it only if the firmware didn't support notifications. Finally, it also adds a fix for smatch warning by declaring ffa_bus_type structure in the header. ---------------------------------------------------------------- Lorenzo Pieralisi (1): firmware: arm_ffa: Fix ffa_notification_info_get() IDs handling Sudeep Holla (6): firmware: arm_ffa: Declare ffa_bus_type structure in the header firmware: arm_ffa: Allow FF-A initialisation even when notification fails firmware: arm_ffa: Setup the partitions after the notification initialisation firmware: arm_ffa: Add checks for the notification enabled state firmware: arm_ffa: Fix FFA notifications cleanup path firmware: arm_ffa: Fix the size of the allocation in ffa_partitions_cleanup() drivers/firmware/arm_ffa/driver.c | 70 +++++++++++++++++++++++++-------------- include/linux/arm_ffa.h | 2 ++ 2 files changed, 48 insertions(+), 24 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> Subject: [GIT PULL] firmware: arm_ffa: Fixes for v6.7 Date: Thu, 16 Nov 2023 19:16:03 +0000 [thread overview] Message-ID: <20231116191603.929767-1-sudeep.holla@arm.com> (raw) Hi ARM SoC Team, Please pull ! Regards, Sudeep -->8 The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86: Linux 6.7-rc1 (2023-11-12 16:19:07 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git tags/ffa-fixes-6.7 for you to fetch changes up to f1ed48ef97e2d12dee21e42db4a6ebb895ed3a79: firmware: arm_ffa: Fix ffa_notification_info_get() IDs handling (2023-11-13 11:51:26 +0000) ---------------------------------------------------------------- Arm FF-A fixes for v6.7 A bunch of fixes addressing issues around the notification support that was added this cycle. They address issue in partition IDs handling in ffa_notification_info_get(), notifications cleanup path and the size of the allocation in ffa_partitions_cleanup(). It also adds check for the notification enabled state so that the drivers registering the callbacks can be rejected if not enabled/supported. It also moves the partitions setup operation after the notification initialisation so that the driver has the correct state for notification enabled/supported before the partitions are initialised/setup. It also now allows FF-A initialisation to complete successfully even when the notification initialisation fails as it is an optional support in the specification. Initial support just allowed it only if the firmware didn't support notifications. Finally, it also adds a fix for smatch warning by declaring ffa_bus_type structure in the header. ---------------------------------------------------------------- Lorenzo Pieralisi (1): firmware: arm_ffa: Fix ffa_notification_info_get() IDs handling Sudeep Holla (6): firmware: arm_ffa: Declare ffa_bus_type structure in the header firmware: arm_ffa: Allow FF-A initialisation even when notification fails firmware: arm_ffa: Setup the partitions after the notification initialisation firmware: arm_ffa: Add checks for the notification enabled state firmware: arm_ffa: Fix FFA notifications cleanup path firmware: arm_ffa: Fix the size of the allocation in ffa_partitions_cleanup() drivers/firmware/arm_ffa/driver.c | 70 +++++++++++++++++++++++++-------------- include/linux/arm_ffa.h | 2 ++ 2 files changed, 48 insertions(+), 24 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-11-16 19:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-16 19:16 Sudeep Holla [this message] 2023-11-16 19:16 ` [GIT PULL] firmware: arm_ffa: Fixes for v6.7 Sudeep Holla 2023-12-06 16:23 ` Sudeep Holla 2023-12-06 16:23 ` Sudeep Holla 2023-12-06 16:40 ` Arnd Bergmann 2023-12-06 16:40 ` Arnd Bergmann 2023-12-06 16:40 ` 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=20231116191603.929767-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=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.