public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Lucian Paul-Trifu <lucian.paul-trifu@arm.com>,
	Marc Bonnici <marc.bonnici@arm.com>,
	Coboy Chen <coboy.chen@mediatek.com>
Subject: Re: [PATCH RFT 03/12] firmware: arm_ffa: Implement the notification bind and unbind interface
Date: Tue, 12 Sep 2023 17:08:14 +0100	[thread overview]
Message-ID: <20230912160814.maooz77hthnja2py@bogus> (raw)
In-Reply-To: <20230912132353.GB4160483@rayden>

On Tue, Sep 12, 2023 at 03:23:53PM +0200, Jens Wiklander wrote:
> On Thu, Aug 03, 2023 at 08:02:07PM +0100, Sudeep Holla wrote:
> > A receiver endpoint must bind a notification to any sender endpoint
> > before the latter can signal the notification to the former. The receiver
> > assigns one or more doorbells to a specific sender. Only the sender can
> > ring these doorbells.
> > 
> > A receiver uses the FFA_NOTIFICATION_BIND interface to bind one or more
> > notifications to the sender. A receiver un-binds a notification from a
> > sender endpoint to stop the notification from being signaled. It uses
> > the FFA_NOTIFICATION_UNBIND interface to do this.
> > 
> > Allow the FF-A driver to be able to bind and unbind a given notification
> > ID to a specific partition ID. This will be used to register and
> > unregister notification callbacks from the FF-A client drivers.
> > 
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > ---
> >  drivers/firmware/arm_ffa/driver.c | 29 +++++++++++++++++++++++++++++
> >  1 file changed, 29 insertions(+)
> > 
> > diff --git a/drivers/firmware/arm_ffa/driver.c b/drivers/firmware/arm_ffa/driver.c
> > index 022c893c9e06..a76e5d3a2422 100644
> > --- a/drivers/firmware/arm_ffa/driver.c
> > +++ b/drivers/firmware/arm_ffa/driver.c
> > @@ -575,6 +575,35 @@ static int ffa_notification_bitmap_destroy(void)
> >  	return 0;
> >  }
> >  
> > +#define NOTIFICATION_LOW_MASK		GENMASK(31, 0)
> > +#define NOTIFICATION_HIGH_MASK		GENMASK(63, 32)
> > +#define NOTIFICATION_BITMAP_HIGH(x)	\
> > +		((u32)(FIELD_GET(NOTIFICATION_HIGH_MASK, (x))))
> > +#define NOTIFICATION_BITMAP_LOW(x)	\
> > +		((u32)(FIELD_GET(NOTIFICATION_LOW_MASK, (x))))
> > +
> > +static int ffa_notification_bind_common(u16 dst_id, u64 bitmap,
> > +					u32 flags, bool is_bind)
> > +{
> > +	ffa_value_t ret;
> > +	u32 func, src_dst_ids = PACK_TARGET_INFO(dst_id, drv_info->vm_id);
> dst_id and drv_info->vm_id should be swapped in the argument to
> PACK_TARGET_INFO().
> 

Thanks a lot for having a look at the series. I see Olivier or someone
have already pointed this in private and I seem to have it fixed locally
already.

-- 
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-12 16:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 19:02 [PATCH RFT 00/12] firmware: arm_ffa: Add FF-A v1.1 notifications support Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 01/12] firmware: arm_ffa: Update the FF-A command list with v1.1 additions Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 02/12] firmware: arm_ffa: Implement notification bitmap create and destroy interfaces Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 03/12] firmware: arm_ffa: Implement the notification bind and unbind interface Sudeep Holla
2023-09-12 13:23   ` Jens Wiklander
2023-09-12 16:08     ` Sudeep Holla [this message]
2023-08-03 19:02 ` [PATCH RFT 04/12] firmware: arm_ffa: Implement the FFA_RUN interface Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 05/12] firmware: arm_ffa: Implement the FFA_NOTIFICATION_SET interface Sudeep Holla
2023-09-12 13:23   ` Jens Wiklander
2023-08-03 19:02 ` [PATCH RFT 06/12] firmware: arm_ffa: Implement the FFA_NOTIFICATION_GET interface Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 07/12] firmware: arm_ffa: Implement the NOTIFICATION_INFO_GET interface Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 08/12] firmware: arm_ffa: Initial support for scheduler receiver interrupt Sudeep Holla
2023-09-12 13:41   ` Jens Wiklander
2023-09-12 16:06     ` Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 09/12] firmware: arm_ffa: Add schedule receiver callback mechanism Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 10/12] firmware: arm_ffa: Add interfaces to request notification callbacks Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 11/12] firmware: arm_ffa: Add interface to send a notification to a given partition Sudeep Holla
2023-08-03 19:02 ` [PATCH RFT 12/12] firmware: arm_ffa: Add notification handling mechanism 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=20230912160814.maooz77hthnja2py@bogus \
    --to=sudeep.holla@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=lucian.paul-trifu@arm.com \
    --cc=marc.bonnici@arm.com \
    /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