| Message ID | 1439977055-1747-2-git-send-email-leo.yan@linaro.org |
|---|---|
| State | New |
| Headers | show |
Hi Sudeep, Thanks for review, please see below comment. On Tue, Aug 25, 2015 at 12:17:20PM +0100, Sudeep Holla wrote: > On 19/08/15 10:37, Leo Yan wrote: > >Document the new compatible for Hisilicon Hi6220 mailbox driver. > > > >Signed-off-by: Leo Yan <leo.yan@linaro.org> > >--- > > .../bindings/mailbox/hisilicon,hi6220-mailbox.txt | 57 ++++++++++++++++++++++ > > 1 file changed, 57 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt > > > >diff --git a/Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt b/Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt > >new file mode 100644 > >index 0000000..3dfb0b0 > >--- /dev/null > >+++ b/Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt > >@@ -0,0 +1,57 @@ > >+Hisilicon Hi6220 Mailbox Driver > >+=============================== > >+ > >+Hisilicon Hi6220 mailbox supports up to 32 channels. Each channel > >+is unidirectional with a maximum message size of 8 words. I/O is > >+performed using register access (there is no DMA) and the cell > >+raises an interrupt when messages are received. > >+ > >+Mailbox Device Node: > >+==================== > >+ > >+Required properties: > >+-------------------- > >+- compatible: Shall be "hisilicon,hi6220-mbox" > >+- reg: Contains the mailbox register address range (base > >+ address and length); the first item is for IPC > >+ registers, the second item is shared buffer for > >+ slots. > > Not sure if the shared buffer needs to be part of the controller binding > as it's not related to it. It's just agreement between the endpoints of > this mailbox on particular SoC and IMO has to part of the client binding. Yes, we need distinguish the buffer is really used for channel's management or just only used for client. Here "shared buffer" is used for channels' state machine, mode and raw data with 8 words. So mailbox driver just read/write raw data according to client's requirement, client will define their specific format for data transcation. Thanks, Leo Yan -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt b/Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt new file mode 100644 index 0000000..3dfb0b0 --- /dev/null +++ b/Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt @@ -0,0 +1,57 @@ +Hisilicon Hi6220 Mailbox Driver +=============================== + +Hisilicon Hi6220 mailbox supports up to 32 channels. Each channel +is unidirectional with a maximum message size of 8 words. I/O is +performed using register access (there is no DMA) and the cell +raises an interrupt when messages are received. + +Mailbox Device Node: +==================== + +Required properties: +-------------------- +- compatible: Shall be "hisilicon,hi6220-mbox" +- reg: Contains the mailbox register address range (base + address and length); the first item is for IPC + registers, the second item is shared buffer for + slots. +- #mbox-cells Common mailbox binding property to identify the number + of cells required for the mailbox specifier. Should be 1. +- interrupts: Contains the interrupt information for the mailbox + device. The format is dependent on which interrupt + controller the SoCs use. + +Example: +-------- + + mailbox: mailbox@F7510000 { + #mbox-cells = <1>; + compatible = "hisilicon,hi6220-mbox"; + reg = <0x0 0xF7510000 0x0 0x1000>, /* IPC_S */ + <0x0 0x06DFF800 0x0 0x0800>; /* Mailbox */ + interrupt-parent = <&gic>; + interrupts = <0 94 4>; + }; + + +Mailbox client +=============== + +"mboxes" and the optional "mbox-names" (please see +Documentation/devicetree/bindings/mailbox/mailbox.txt for details). Each value +of the mboxes property should contain a phandle to the mailbox controller +device node and second argument is the channel index. It must be 0 (hardware +support only one channel). The equivalent "mbox-names" property value can be +used to give a name to the communication channel to be used by the client user. + +Example: +-------- + + stub_clock: stub_clock { + compatible = "hisilicon,hi6220-stub-clk"; + hisilicon,hi6220-clk-sram = <&sram>; + #clock-cells = <1>; + mbox-names = "mbox-tx"; + mboxes = <&mailbox 1>; + };
Document the new compatible for Hisilicon Hi6220 mailbox driver. Signed-off-by: Leo Yan <leo.yan@linaro.org> --- .../bindings/mailbox/hisilicon,hi6220-mailbox.txt | 57 ++++++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 Documentation/devicetree/bindings/mailbox/hisilicon,hi6220-mailbox.txt