On Mon, Sep 14, 2015 at 6:06 AM, Caesar Wang <wxt@xxxxxxxxxxxxxx> wrote: > This add the necessary binding documentation for mailbox > found on RK3368 SoC. > > Signed-off-by: Caesar Wang <wxt@xxxxxxxxxxxxxx> > --- > > .../bindings/mailbox/rockchip-mailbox.txt | 33 ++++++++++++++++++++++ > 1 file changed, 33 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mailbox/rockchip-mailbox.txt > > diff --git a/Documentation/devicetree/bindings/mailbox/rockchip-mailbox.txt b/Documentation/devicetree/bindings/mailbox/rockchip-mailbox.txt > new file mode 100644 > index 0000000..b9b4768 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mailbox/rockchip-mailbox.txt > @@ -0,0 +1,33 @@ > +Rockchip mailbox > + > +The Rockchip mailbox is used by the Rockchip CPU cores to communicate > +requests to MCU processor. > + > +Refer to ./mailbox.txt for generic information about mailbox device-tree > +bindings. > + > +Required properties: > + > + - compatible: should be one of the following. > + - "rockchip,rk3368-mbox" for rk3368 > + - reg: physical base address of the controller and length of memory mapped > + region. > + physical base address of the share buffer and length of memory mapped s/share/shared/ > + region. > + - interrupts: The interrupt number to the cpu. The interrupt specifier format > + depends on the interrupt controller. Need to specify the value of #mbox-cells. > + > +Example: > +-------- > + > +/* RK3368 */ > +mbox: mbox@ff6b0000 { > + compatible = "rockchip,rk3368-mailbox"; > + reg = <0x0 0xff6b0000 0x0 0x1000>, > + <0x0 0xff8cf000 0x0 0x1000>; /* the end 4k of sram */ If this is just onchip SRAM usable for anything, then use the SRAM binding (misc/sram.txt). It has provisions for defining the use. > + interrupts = <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>, > + <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>, > + <GIC_SPI 148 IRQ_TYPE_LEVEL_HIGH>, > + <GIC_SPI 149 IRQ_TYPE_LEVEL_HIGH>; > + #mbox-cells = <1>; > +}; > -- > 1.9.1 > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html