[PATCH v3 03/17] firmware: arm_ffa: Implement the notification bind and unbind interface
Sudeep Holla
sudeep.holla at arm.com
Thu Oct 5 06:30:24 PDT 2023
On Thu, Oct 05, 2023 at 11:56:22AM +0200, Jens Wiklander wrote:
> On Thu, Oct 5, 2023 at 10:51 AM Sudeep Holla <sudeep.holla at arm.com> wrote:
[...]
> > A receiver(FF-A driver) must bind a non-framework notification to a
> > sender(SP) before the latter can signal the notification to the former.
> > Only the sender can ring these doorbells. A receiver uses the
> > FFA_NOTIFICATION_BIND interface to bind one or more notifications to the
> > sender.
> >
> > So, based on this text(modified to refer sender and receiver in the driver
> > context) from the spec, my understanding is the driver is the receiver
> > and the SP is the sender of the notification.
> >
> > Do you think I am missing someting here ? Sorry for agreeing with you
> > in v2 and silently changing it back without this actual discussion.
> > Olivier raised the issue and then when I went back and looked at the
> > spec, I realised why I had it this way from the beginning.
>
> Thanks for the explanation, now I get it. My mistake was that I
> thought that sender and receiver meant the sender and receiver of the
> actual message being sent like with a direct request, it is using the
> same register and the same wording after all. Instead, it means the
> sender and receiver of an eventual notification, which of course is
> the exact opposite.
>
Thanks for the response. Glad we are on same page now with respect to this.
--
Regards,
Sudeep
More information about the linux-arm-kernel
mailing list