[PATCH 02/10] mailbox: Enable BCM2835 mailbox support
arnd at arndb.de
Wed Mar 4 01:49:30 PST 2015
On Tuesday 03 March 2015 20:03:13 Stephen Warren wrote:
> > +
> > +/*
> > + * Mailbox registers. We basically only support mailbox 0 & 1. We
> > + * deliver to the VC in mailbox 1, it delivers to us in mailbox 0. See
> > + * BCM2835-ARM-Peripherals.pdf section 1.3 for an explanation about
> > + * the placement of memory barriers.
> > + */
> > +#define MAIL0_RD (ARM_0_MAIL0 + 0x00)
> > +#define MAIL0_POL (ARM_0_MAIL0 + 0x10)
> > +#define MAIL0_STA (ARM_0_MAIL0 + 0x18)
> > +#define MAIL0_CNF (ARM_0_MAIL0 + 0x1C)
> > +#define MAIL1_WRT (ARM_0_MAIL1 + 0x00)
> That implies there are more mailboxes. I wonder if we should
> parameterize which to use via some DT properties? I guess we can defer
> that though; we can default to the current values and add properties
> later if we want to use something else.
How about changing #mbox-cells to <2> and using the first cell to
identify the mailbox and the second to identify the channel?
The binding isn't very clear on the meaning of the one argument
cell for the mailbox reference, but I assume it's used for the
mailbox channel rather than the mailbox id.
More information about the linux-rpi-kernel