Re: [openmcapi-dev] Re: [RFC] Inter-processor Mailboxes Drivers
flat view
From: Blanchard, Hollis <hidden>
Date: 2011-02-16 20:22:41
Also in:
linux-arm-kernel
On 02/15/2011 10:22 PM, Hiroshi DOYU wrote:
From: "ext Blanchard, Hollis"<redacted> Subject: Re: [RFC] Inter-processor Mailboxes Drivers Date: Tue, 15 Feb 2011 15:38:25 -0800quoted
On 02/15/2011 01:58 PM, Meador Inge wrote:quoted
On 02/14/2011 04:01 AM, Jamie Iles wrote:quoted
On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:quoted
1. Hardware specific bits somewhere under '.../arch/*'. =
Drivers
quoted
quoted
quoted
quoted
for the MPIC message registers on Power and OMAP4 =
mailboxes,
quoted
quoted
quoted
quoted
for example. 2. A higher level driver under '.../drivers/mailbox/*'. =
That the
quoted
quoted
quoted
quoted
pieces in (1) would register with. This piece would =
expose the
quoted
quoted
quoted
quoted
main kernel API. 3. Userspace interfaces for accessing the mailboxes. A '/dev/mailbox1', '/dev/mailbox2', etc... mapping, for =
example.
quoted
quoted
quoted
How about using virtio for all of this and having the mailbox as a notification/message passing driver for the virtio backend? There =
are
quoted
quoted
quoted
already virtio console and network drivers that could be useful for =
the
quoted
quoted
quoted
userspace part of it. drivers/virtio/virtio_ring.c might be a good starting point if you thought there was some mileage in this =
approach.
quoted
quoted
To be honest, I am not that familiar with 'virtio', but I will take =
a
quoted
quoted
look. Thanks for the pointer. Maybe Hollis can speak to this idea =
more.
quoted
My opinion is that virtio is (over?) complicated.Considering the case of omap mailbox H/W, it is just a simple one way 4 slot x 32bit H/W FIFO, I also may think that this may be a bit too much...
I think the proposal is to implement a virtio link using the OMAP=20 mailboxes as the interrupt mechanism, and shared memory to carry the=20 data and descriptor rings. Hollis Blanchard Mentor Graphics, Embedded Systems Division