On Wed, Jan 6, 2021 at 4:30 AM Sudeep Holla wrote:
>
> On Tue, Jan 05, 2021 at 01:32:49PM -0500, Jim Quinlan wrote:
>
> [...]
>
> >
> > I don't think that is the case; the bottom routine,
> > do_wait_for_common(), decrements the x->done after a completion (which
> > does an increment).
On Tue, Jan 05, 2021 at 01:32:49PM -0500, Jim Quinlan wrote:
[...]
>
> I don't think that is the case; the bottom routine,
> do_wait_for_common(), decrements the x->done after a completion (which
> does an increment). Regardless, I think it is prudent to add the
> reinit patch you've provided
> From: Sudeep Holla
> Date: Tue, Jan 5, 2021 at 12:35 PM
> Subject: Re: [PATCH v4 2/2] firmware: arm_scmi: Augment SMC/HVC to allow
> optional interrupt
> To: Florian Fainelli
> Cc: Jim Quinlan , Sudeep Holla ,
> , , open
> list:SYSTEM CONTROL & POWER/MANAGEMEN
On Tue, Dec 22, 2020 at 07:37:22PM -0800, Florian Fainelli wrote:
>
>
> On 12/22/2020 6:56 AM, 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
On 12/22/2020 6:56 AM, 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
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.
6 matches
Mail list logo
