[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+-6iNxZ73gYtjP54kBJhcwzL5h4Co6Wh8-Nk4poqLV0s=jA8w@mail.gmail.com>
Date: Fri, 13 Nov 2020 09:26:43 -0500
From: Jim Quinlan <james.quinlan@...adcom.com>
To: Sudeep Holla <sudeep.holla@....com>
Cc: "maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@...adcom.com>,
Cristian Marussi <cristian.marussi@....com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 2/2] firmware: arm_scmi: Augment SMC/HVC to allow
optional interrupt
Hi, these are fast calls. Regards, Jim
On Fri, Nov 13, 2020 at 4:47 AM Sudeep Holla <sudeep.holla@....com> wrote:
>
> On Thu, Nov 12, 2020 at 12:56:27PM -0500, Jim Quinlan wrote:
> > The SMC/HVC SCMI transport is modified to allow the completion of an SCMI
> > message to be indicated by an interrupt rather than the return of the smc
> > call. This accommodates the existing behavior of the BrcmSTB SCMI
> > "platform" whose SW is already out in the field and cannot be changed.
> >
>
> Sorry for missing to check with you earlier. Are these not fast smc calls ?
> Can we check the SMC Function IDs for the same and expect IRQ to be present
> if they are not fast calls ?
Hi, if I understand you correctly you want to do something like this:
if (! ARM_SMCCC_IS_FAST_CALL(func_id)) {
/* look for irq and request it */
}
But we do use fast calls.
Regards,
Jim
>
> --
> Regards,
> Sudeep
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4167 bytes)
Powered by blists - more mailing lists