On Mon, Jul 24, 2017 at 11:08 PM, Sudeep Holla wrote:
> On 24/07/17 18:20, Jassi Brar wrote:
>>
>>> I see that the SCPI firmware driver (as the user of the mailbox API) is
>>> expecting the return value from a0 as returned above, translating the
>>> firmware error codes into Linux' ones.
>>>
>> I
On 24/07/17 18:20, Jassi Brar wrote:
> On Mon, Jul 24, 2017 at 4:50 AM, André Przywara
> wrote:
>> On 02/07/17 06:55, Jassi Brar wrote:
>>
+ mbox_chan_received_data(link, (void *)res.a0);
+
>>> Or you can update the 'data' with value from 'a0' ?
>>
>> Mmh, I am a bit puzzled by
On Mon, Jul 24, 2017 at 4:50 AM, André Przywara wrote:
> On 02/07/17 06:55, Jassi Brar wrote:
>
>>> + mbox_chan_received_data(link, (void *)res.a0);
>>> +
>> Or you can update the 'data' with value from 'a0' ?
>
> Mmh, I am a bit puzzled by this. Why would this be needed or useful?
>
I meant
On 02/07/17 06:55, Jassi Brar wrote:
Hi Jassi,
thank you very much for having a look!
> On Fri, Jun 30, 2017 at 3:26 PM, Andre Przywara
> wrote:
>> This mailbox driver implements a mailbox which signals transmitted data
>> via an ARM smc (secure monitor call) instruction. The mailbox receiver
On Fri, Jun 30, 2017 at 3:26 PM, Andre Przywara wrote:
> This mailbox driver implements a mailbox which signals transmitted data
> via an ARM smc (secure monitor call) instruction. The mailbox receiver
> is implemented in firmware and can synchronously return data when it
> returns execution to th
This mailbox driver implements a mailbox which signals transmitted data
via an ARM smc (secure monitor call) instruction. The mailbox receiver
is implemented in firmware and can synchronously return data when it
returns execution to the non-secure world again.
An asynchronous receive path is not im
6 matches
Mail list logo
