Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030829AbbDWUBf (ORCPT ); Thu, 23 Apr 2015 16:01:35 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:54226 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030657AbbDWUBb (ORCPT ); Thu, 23 Apr 2015 16:01:31 -0400 Message-ID: <55394F98.3060600@codeaurora.org> Date: Thu, 23 Apr 2015 14:01:28 -0600 From: Jeffrey Hugo User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Bjorn Andersson , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Andry Gross CC: devicetree@vger.kernel.org, linux-arm-msm , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] soc: qcom: Add device tree binding for SMEM References: <1428795178-24312-1-git-send-email-bjorn.andersson@sonymobile.com> In-Reply-To: <1428795178-24312-1-git-send-email-bjorn.andersson@sonymobile.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2503 Lines: 85 On 4/11/2015 5:32 PM, Bjorn Andersson wrote: > Add device tree binding documentation for the Qualcom Shared Memory > manager. > > Signed-off-by: Bjorn Andersson > --- > > Changes since v1: > - None > > .../devicetree/bindings/soc/qcom/qcom,smem.txt | 49 ++++++++++++++++++++++ > 1 file changed, 49 insertions(+) > create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,smem.txt > > diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,smem.txt b/Documentation/devicetree/bindings/soc/qcom/qcom,smem.txt > new file mode 100644 > index 0000000..d90f839 > --- /dev/null > +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,smem.txt > @@ -0,0 +1,49 @@ > +Qualcomm Shared Memory binding > + > +This binding describes the Qualcomm Shared Memory, used to share data between > +various subsystems and OSes in Qualcomm platforms. > + > +- compatible: > + Usage: required > + Value type: > + Definition: must be: > + "qcom,smem" > + > +- memory-region: > + Usage: required > + Value type: > + Definition: handle to memory reservation for main smem memory region. > + > +- reg: > + Usage: optional > + Value type: > + Definition: base address and size pair for any additional memory areas > + of the shared memory. > + > +- hwspinlocks: > + Usage: required > + Value type: > + Definition: reference to a hwspinlock used to protect allocations from > + the shared memory > + > += EXAMPLE > + > + reserved-memory { > + #address-cells = <1>; > + #size-cells = <1>; > + ranges; > + > + smem_region: smem@fa00000 { > + reg = <0xfa00000 0x200000>; > + no-map; > + }; > + }; > + > + smem@fa00000 { > + compatible = "qcom,smem"; > + > + memory-region = <&smem_region>; > + reg = <0xfc428000 0x4000>; > + > + hwlocks = <&tcsr_mutex 3>; > + }; > For my information, is there any intention to support the relocatable smem_region by looking it up at init time? It does not seem like it would be possible to support that with this binding. -- Jeffrey Hugo Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/