From: slapdau@yahoo•com.au (Craig McGeachie)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC PATCH 2/3] Enable BCM2835 mailbox support
Date: Thu, 03 Oct 2013 20:30:55 +1300 [thread overview]
Message-ID: <524D1D2F.3020303@yahoo.com.au> (raw)
In-Reply-To: <524BECCC.6030804@yahoo.com.au>
On 10/02/2013 10:52 PM, Craig McGeachie wrote:
> mailbox {
> compatible = "brcm,bcm2835-mbox";
> reg = <0x7e00b880 0x40>;
> interrupts = <0 1>;
> #address-cells = <1>;
> #size-cells = <0>;
> power at 0 {
> reg = <0>;
> };
> fb at 1 {
> reg = <1>;
> };
> vchiq at 1 {
> reg = <3>;
> };
> props_mbox: property at 8 {
> reg = <8>;
> };
> };
>
> thermal {
> compatible = "brcm,bcm2835-thermal";
> brcm,channel = <&props_mbox>;
> };
>
It's occurred to me that this might not be the best motivating example.
thermal has no register address and does not belong under soc really,
even if it sort of works. It does make more sense for it to live under
mailbox, maybe. DMA is the other example that might make more sense.
mailbox {
compatible = "brcm,bcm2835-mbox";
reg = <0x7e00b880 0x40>;
interrupts = <0 1>;
#address-cells = <1>;
#size-cells = <0>;
power at 0 {
reg = <0>;
};
fb at 1 {
reg = <1>;
};
vchiq at 1 {
reg = <3>;
};
props_mbox: property at 8 {
reg = <8>;
};
};
dma {
compatible = "brcm,bcm2835-dma";
reg = <0x7e007000 0x1000>;
channel = <&props_mbox>;
interrupts =
<1 16>, <1 17>, <1 18>, <1 19>, <1 20>, <1 21>,
<1 22>, <1 23>, <1 24>, <1 25>, <1 26>, <1 27>,
<1 28>;
/* Maybe some other stuff. */
};
/* And thermal somewhere else, I don't know where. */
Access to the properties mailbox channel enables getting a bit mask of
DMA channels that the ARM core is permitted to use.
Cheers,
Craig.
next prev parent reply other threads:[~2013-10-03 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 11:32 [RFC PATCH 2/3] Enable BCM2835 mailbox support Craig McGeachie
2013-10-02 3:05 ` Stephen Warren
2013-10-02 9:52 ` Craig McGeachie
2013-10-03 7:30 ` Craig McGeachie [this message]
2014-06-22 10:45 ` Lubomir Rintel
2014-06-24 6:21 ` Craig McGeachie
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=524D1D2F.3020303@yahoo.com.au \
--to=slapdau@yahoo$(echo .)com.au \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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