On Thu, 2014-06-12 at 22:31 +0530, Jassi Brar wrote:
> Introduce common framework for client/protocol drivers and
> controller drivers of Inter-Processor-Communication (IPC).
>
> Client driver developers should have a look at
> include/linux/mailbox_client.h to understand the part of
> the API ex
On Thu, 2014-06-12 at 22:31 +0530, Jassi Brar wrote:
> Introduce common framework for client/protocol drivers and
> controller drivers of Inter-Processor-Communication (IPC).
>
> Client driver developers should have a look at
> include/linux/mailbox_client.h to understand the part of
> the API ex
On Fri, Jun 20, 2014 at 01:59:30AM +0530, Jassi Brar wrote:
> On 20 June 2014 00:33, Matt Porter wrote:
> > On Thu, Jun 19, 2014 at 07:17:11PM +0100, Sudeep Holla wrote:
> >
> >> >+ * After startup and before shutdown any data received on the chan
> >> >+ * is passed on to the API via atomic mbox_
On 20 June 2014 00:33, Matt Porter wrote:
> On Thu, Jun 19, 2014 at 07:17:11PM +0100, Sudeep Holla wrote:
>
>> >+ * After startup and before shutdown any data received on the chan
>> >+ * is passed on to the API via atomic mbox_chan_received_data().
>> >+ * The controller should ACK the RX only af
Hi Jassi,
I started using this from v5 and tried briefly to follow previous versions
and discussion. Please forgive me if I ask questions that are already answered.
On 12/06/14 18:01, Jassi Brar wrote:
Introduce common framework for client/protocol drivers and
controller drivers of Inter-Proces
Hi Jassi,
On 19/06/14 03:55, Jassi Brar wrote:
On 18 June 2014 22:33, Kevin Hilman wrote:
[...]
That's great.
I sure would like to see some more Reviewed-by tags from those folks to
confirm that those starting to use it think it's on the right track.
The upstreaming attempts have been go
Hello,
On 18 June 2014 22:55, Jassi Brar wrote:
>>
>> I sure would like to see some more Reviewed-by tags from those folks to
>> confirm that those starting to use it think it's on the right track.
>>
> The upstreaming attempts have been going on for months now, and via
> non-public interactions
On 18 June 2014 22:33, Kevin Hilman wrote:
> Jassi Brar writes:
>
>> On 18 June 2014 05:57, Kevin Hilman wrote:
>>> Jassi Brar writes:
>>>
Introduce common framework for client/protocol drivers and
controller drivers of Inter-Processor-Communication (IPC).
Client driver deve
Jassi Brar writes:
> On 18 June 2014 05:57, Kevin Hilman wrote:
>> Jassi Brar writes:
>>
>>> Introduce common framework for client/protocol drivers and
>>> controller drivers of Inter-Processor-Communication (IPC).
>>>
>>> Client driver developers should have a look at
>>> include/linux/mailbo
On 18 June 2014 05:57, Kevin Hilman wrote:
> Jassi Brar writes:
>
>> Introduce common framework for client/protocol drivers and
>> controller drivers of Inter-Processor-Communication (IPC).
>>
>> Client driver developers should have a look at
>> include/linux/mailbox_client.h to understand the p
Jassi Brar writes:
> Introduce common framework for client/protocol drivers and
> controller drivers of Inter-Processor-Communication (IPC).
>
> Client driver developers should have a look at
> include/linux/mailbox_client.h to understand the part of
> the API exposed to client drivers.
> Simila
On Thu, Jun 12, 2014 at 10:31:19PM +0530, Jassi Brar wrote:
A couple of tiny nits, I'll send followup patches for these.
> +bool mbox_client_peek_data(struct mbox_chan *chan)
> +{
> + if (chan->mbox->ops->peek_data)
> + return chan->mbox->ops->peek_data(chan);
> +
> + return f
Introduce common framework for client/protocol drivers and
controller drivers of Inter-Processor-Communication (IPC).
Client driver developers should have a look at
include/linux/mailbox_client.h to understand the part of
the API exposed to client drivers.
Similarly controller driver developers s
13 matches
Mail list logo
