From patchwork Fri Feb 5 16:34:03 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Nishanth Menon X-Patchwork-Id: 61328 Delivered-To: patch@linaro.org Received: by 10.112.43.199 with SMTP id y7csp67873lbl; Fri, 5 Feb 2016 08:34:44 -0800 (PST) X-Received: by 10.66.194.230 with SMTP id hz6mr20922023pac.70.1454690084090; Fri, 05 Feb 2016 08:34:44 -0800 (PST) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id dn3si24790953pac.189.2016.02.05.08.34.43; Fri, 05 Feb 2016 08:34:44 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of devicetree-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of devicetree-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=devicetree-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754261AbcBEQem (ORCPT + 6 others); Fri, 5 Feb 2016 11:34:42 -0500 Received: from devils.ext.ti.com ([198.47.26.153]:43564 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751592AbcBEQej (ORCPT ); Fri, 5 Feb 2016 11:34:39 -0500 Received: from dflxv15.itg.ti.com ([128.247.5.124]) by devils.ext.ti.com (8.13.7/8.13.7) with ESMTP id u15GYC3P025842; Fri, 5 Feb 2016 10:34:12 -0600 Received: from DFLE72.ent.ti.com (dfle72.ent.ti.com [128.247.5.109]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id u15GYCwq019478; Fri, 5 Feb 2016 10:34:12 -0600 Received: from dflp32.itg.ti.com (10.64.6.15) by DFLE72.ent.ti.com (128.247.5.109) with Microsoft SMTP Server id 14.3.224.2; Fri, 5 Feb 2016 10:34:11 -0600 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by dflp32.itg.ti.com (8.14.3/8.13.8) with ESMTP id u15GYB3j026127; Fri, 5 Feb 2016 10:34:12 -0600 From: Nishanth Menon To: Jassi Brar , Suman Anna CC: Franklin S Cooper Jr , , , , Santosh Shilimkar , Nishanth Menon Subject: [PATCH 1/2] Documentation: dt: mailbox: Add TI Message Manager Date: Fri, 5 Feb 2016 10:34:03 -0600 Message-ID: <1454690044-2560-2-git-send-email-nm@ti.com> X-Mailer: git-send-email 2.7.0 In-Reply-To: <1454690044-2560-1-git-send-email-nm@ti.com> References: <1454690044-2560-1-git-send-email-nm@ti.com> MIME-Version: 1.0 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Message Manager is a hardware block used to communicate with various processor systems within certain Texas Instrument's Keystone generation SoCs. This hardware engine is used to transfer messages from various compute entities(or processors) within the SoC. It is designed to be self contained without needing software initialization for operation. Signed-off-by: Nishanth Menon --- .../bindings/mailbox/ti,message-manager.txt | 72 ++++++++++++++++++++++ 1 file changed, 72 insertions(+) create mode 100644 Documentation/devicetree/bindings/mailbox/ti,message-manager.txt -- 2.7.0 -- 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/ti,message-manager.txt b/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt new file mode 100644 index 000000000000..f3d73b0b3c66 --- /dev/null +++ b/Documentation/devicetree/bindings/mailbox/ti,message-manager.txt @@ -0,0 +1,72 @@ +Texas Instruments' Message Manager Driver +======================================== + +The Texas Instruments' Message Manager is a mailbox controller that has +configurable queues selectable at SoC(System on Chip) integration. The Message +manager is broken up into queues in different address regions that are called +"proxies" - each instance is unidirectional and is instantiated at SoC +integration level to indicate receive or transmit path. + +Message Manager Device Node: +=========================== + +Required properties: +-------------------- +- compatible: Shall be: + "ti,k2g-message-manager" + "ti,message-manager" +- reg-names queue_proxy_region - Map the queue Proxy region + queue_state_debug_region - Map the queue state debug + region. +- reg: Contains the register map per reg-names +- #mbox-cells Shall be 1 + +Child Nodes: +============ +A child node is used for representing the actual queue device that is +used for the communication between the host processor and a remote processor. +Each child node should have a unique node name across all the different +message manager device nodes. + +Required Properties: +-------------------- +- ti,queue-id: Indicates the queue number this node represents +- ti,proxy-id: Proxy ID representing the processor in the SoC. + +Optional Properties: +-------------------- +- interrupt-names: 'rx' - indicates a receive interrupt (mandatory ONLY if + this is a receive queue) +- interrupts: Contains the interrupt information corresponding to + interrupt-names property. + +Example: +-------- + + msgmgr: msgmgr@02a00000 { + compatible = "ti,k2g-message-manager", "ti,message-manager"; + #mbox-cells = <1>; + reg-names = "queue_proxy_region", "queue_state_debug_region"; + reg = <0x02a00000 0x400000>, <0x028c3400 0x400>; + + msgmgr_proxy_pmmc_tx_prio0: pmmc_tx_prio0 { + ti,queue-id = <0>; + ti,proxy-id = <0>; + }; + + msgmgr_proxy_pmmc_rx: pmmc_rx { + ti,queue-id = <5>; + ti,proxy-id = <2>; + interrupt-names = "rx"; + interrupts = ; + }; + }; + +... + pmmc { + ... + mbox-names = "tx", "rx"; + mboxes = <&msgmgr &msgmgr_proxy_pmmc_tx> + <&msgmgr &msgmgr_proxy_pmmc_rx>; + ... + };