linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: slapdau@yahoo.com.au (Craig McGeachie)
To: linux-arm-kernel@lists.infradead.org
Subject: Query about include/linux/mailbox.h
Date: Fri, 06 Sep 2013 20:48:48 +1200	[thread overview]
Message-ID: <522996F0.2040203@yahoo.com.au> (raw)
In-Reply-To: <CABb+yY0FRYgGSmfSXG+vWcsK0aqg_BwULtH7xY6fqFhLF_i5OA@mail.gmail.com>

On 09/01/2013 01:39 AM, Jassi Brar wrote:
>> See if I can get my head around that framework and what it does, and try
>> fitting the BCM2835 mailbox into it?
>>
> Yes. If you point me to your mailbox client drivers, I could also give
> it a look to see if we need some changes.

Righty ho. This seems to be a reasonable attempt.

https://github.com/rickytarr/linux/tree/subsys-mailbox
https://github.com/rickytarr/linux/commit/e0c25371581d125e3f6a46f452ce3e95f1d267ee

It compiles cleanly and boots.  Start with bcm2835_defconfig, and then 
enable Device Drivers -> Mailbox Hardware Support -> BCM 2835 Mailbox. I 
think it validates that BCM2835 mailbox support can fit into your 
generic device.

But that's as far as I know.  I'm offering this as an early look only 
(comments and defects welcome). I've got to build something that uses it 
next.  For all I know it might cause the Raspberry Pi to explode and 
vaporise any desk it is sitting on.

Out of interest, do you have a roadmap for moving this into the kernel 
mainline?

Cheers,
Craig.

      parent reply	other threads:[~2013-09-06  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-31  4:57 Query about include/linux/mailbox.h Craig McGeachie
2013-08-31  5:33 ` Jassi Brar
2013-08-31 11:19   ` Craig McGeachie
2013-08-31 13:39     ` Jassi Brar
2013-09-01  8:53       ` Craig McGeachie
2013-09-06  8:48       ` Craig McGeachie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=522996F0.2040203@yahoo.com.au \
    --to=slapdau@yahoo.com.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).