From: Sudeep Holla <sudeep.holla@arm.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: Olivier Deprez <Olivier.Deprez@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marc Bonnici <Marc.Bonnici@arm.com>,
Coboy Chen <coboy.chen@mediatek.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>
Subject: Re: [PATCH v3 03/17] firmware: arm_ffa: Implement the notification bind and unbind interface
Date: Thu, 5 Oct 2023 14:30:24 +0100 [thread overview]
Message-ID: <20231005133024.kdxfajmruedli4ne@bogus> (raw)
In-Reply-To: <CAHUa44ETFTKE17tUMsAiF5vYk2yT9wQT-zE+22ic3jHrHhrrJg@mail.gmail.com>
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@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
next prev parent reply other threads:[~2023-10-05 16:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 15:02 [PATCH v3 00/17] firmware: arm_ffa: Add FF-A v1.1 support(notification + new memory descriptor format) Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 01/17] firmware: arm_ffa: Update the FF-A command list with v1.1 additions Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 02/17] firmware: arm_ffa: Implement notification bitmap create and destroy interfaces Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 03/17] firmware: arm_ffa: Implement the notification bind and unbind interface Sudeep Holla
2023-10-04 9:11 ` Jens Wiklander
2023-10-04 9:50 ` Olivier Deprez
2023-10-04 15:32 ` Sudeep Holla
2023-10-05 6:57 ` Jens Wiklander
2023-10-05 8:49 ` Sudeep Holla
2023-10-05 9:56 ` Jens Wiklander
2023-10-05 13:30 ` Sudeep Holla [this message]
2023-09-29 15:02 ` [PATCH v3 04/17] firmware: arm_ffa: Implement the FFA_RUN interface Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 05/17] firmware: arm_ffa: Implement the FFA_NOTIFICATION_SET interface Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 06/17] firmware: arm_ffa: Implement the FFA_NOTIFICATION_GET interface Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 07/17] firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface Sudeep Holla
2023-10-04 9:10 ` Jens Wiklander
2023-10-04 15:11 ` Sudeep Holla
2023-10-05 6:30 ` Jens Wiklander
2023-09-29 15:02 ` [PATCH v3 08/17] firmware: arm_ffa: Initial support for scheduler receiver interrupt Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 09/17] firmware: arm_ffa: Add schedule receiver callback mechanism Sudeep Holla
2023-09-29 15:02 ` [PATCH v3 10/17] firmware: arm_ffa: Add interfaces to request notification callbacks Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 11/17] firmware: arm_ffa: Add interface to send a notification to a given partition Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 12/17] firmware: arm_ffa: Add notification handling mechanism Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 13/17] firmware: arm_ffa: Simplify the computation of transmit and fragment length Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 14/17] KVM: arm64: FFA: Remove access of endpoint memory access descriptor array Sudeep Holla
2023-10-02 16:20 ` Sudeep Holla
2023-10-04 10:08 ` Marc Zyngier
2023-10-04 13:22 ` Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 15/17] firmware: arm_ffa: Switch to using ffa_mem_desc_offset() accessor Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 16/17] firmware: arm_ffa: Update memory descriptor to support v1.1 format Sudeep Holla
2023-09-29 15:03 ` [PATCH v3 17/17] 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=20231005133024.kdxfajmruedli4ne@bogus \
--to=sudeep.holla@arm.com \
--cc=Marc.Bonnici@arm.com \
--cc=Olivier.Deprez@arm.com \
--cc=coboy.chen@mediatek.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@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
all inboxes | Powered by JetHome®