Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp14996296ybl; Mon, 30 Dec 2019 22:45:50 -0800 (PST) X-Google-Smtp-Source: APXvYqwx673B5oW0uYu/00MwC08eS99VeZMmkDlSUY5ALpwW5eMS0afz44OPJ+W5mWHn3Yy4VSI8 X-Received: by 2002:a9d:21f4:: with SMTP id s107mr79850524otb.102.1577774750525; Mon, 30 Dec 2019 22:45:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577774750; cv=none; d=google.com; s=arc-20160816; b=rGS9Ady6DVKWdlZDXMZOMfNaOBmyk0dPFZZCSH9RTCxb05YLvY4UlB+JDpKDk2NnrO v1TVbgMLGGziYu6+WyiGhWHxskPwE3HdfW83FmuwztCvu/c7FBd+5o6PyNGdbHVk8CH2 PTSfShNGegDMCuG0OYAmAJSQ8idb/d96+tlnA2HyQ6VXPc88a6tX8e3HR7E3oeRzIVii glOkM+8LKp4c5J3ihm3a8dzRnZYOHr+GcShP0mlNzdpPuomQTaCk9aqb66oM4W9YU3nD peE2cOjVKchJHUVlLMl0lfx4qc+sSC84ZrSPOW0GeZ1EkgYAdXPZAC1OWfyTjxv/P1it Rz9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature; bh=F847wiYtiWu9zLjLzGjKkB/KIgILEIIryO4cx7acaiI=; b=XACSGy9RQaAcjFPpJqlHMrJ/+XZO/YQ1yeRGmQbRZvCwlnInOtrEbz3Uk1VALthxkR SwC7KxkJ2LqgIZcGI5xUnVOJMJpvTSusc+jBLyoMD1xSO59Rp4XYDXojwl4NfjA9trdf 5R9OdaLVf3i/jMqbeeydGwkYnCY6J4ucu3ZvUMJ9qPBmoLOBTfU+y9F/FY42MUmd4uq3 32mQ4Yu1MvVdQMo34bF5qXyA9Fy7UTWaH4IYzjhodpkcillc8XCULsTtdRtBtSP0zQHf oDbJu9S4gYTWAgDDuTboF+TzdGmYf4KpdTFq7DYhYlTqh0ENTAWbpE9GUyF9Q+WeehVP hIZQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@mg.codeaurora.org header.s=smtp header.b=eDoRKXgr; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o15si24611177otp.314.2019.12.30.22.45.37; Mon, 30 Dec 2019 22:45:50 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@mg.codeaurora.org header.s=smtp header.b=eDoRKXgr; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726307AbfLaGnS (ORCPT + 99 others); Tue, 31 Dec 2019 01:43:18 -0500 Received: from mail25.static.mailgun.info ([104.130.122.25]:48645 "EHLO mail25.static.mailgun.info" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725468AbfLaGnR (ORCPT ); Tue, 31 Dec 2019 01:43:17 -0500 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1577774597; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=F847wiYtiWu9zLjLzGjKkB/KIgILEIIryO4cx7acaiI=; b=eDoRKXgrJ4nuFLDddi2gfURIdd98fUOTxs+YkETGbM9q/23HwLqhBK9UT2Pv9Oh9TtDPE/PW hONEBvqGpcjGsSUYHWQ+X7OH+0pYC3urDVgKEug97mxo+82h/QWGff1fORF8Kes7WLRO53Hr BkSyGFcLy0lvmDWKfkIl6hExAjQ= X-Mailgun-Sending-Ip: 104.130.122.25 X-Mailgun-Sid: WyI0MWYwYSIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by mxa.mailgun.org with ESMTP id 5e0aee04.7fbad48cfb58-smtp-out-n01; Tue, 31 Dec 2019 06:43:16 -0000 (UTC) Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 2A24FC433A2; Tue, 31 Dec 2019 06:43:16 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=2.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: sthella) by smtp.codeaurora.org (Postfix) with ESMTPSA id 74374C43383; Tue, 31 Dec 2019 06:43:15 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 31 Dec 2019 12:13:15 +0530 From: sthella@codeaurora.org To: Bjorn Andersson Cc: agross@kernel.org, srinivas.kandagatla@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] dt-bindings: nvmem: add binding for QTI SPMI SDAM In-Reply-To: <20191229030140.GJ3755841@builder> References: <1577165532-28772-1-git-send-email-sthella@codeaurora.org> <20191229030140.GJ3755841@builder> Message-ID: <412459f3ebb4297b2c21adbb1b9903c6@codeaurora.org> X-Sender: sthella@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-12-29 08:31, Bjorn Andersson wrote: > On Mon 23 Dec 21:32 PST 2019, Shyam Kumar Thella wrote: > >> QTI SDAM allows PMIC peripherals to access the shared memory that is >> available on QTI PMICs. Add documentation for it. >> >> Signed-off-by: Shyam Kumar Thella >> --- >> .../devicetree/bindings/nvmem/qcom,spmi-sdam.yaml | 79 >> ++++++++++++++++++++++ >> 1 file changed, 79 insertions(+) >> create mode 100644 >> Documentation/devicetree/bindings/nvmem/qcom,spmi-sdam.yaml >> >> diff --git >> a/Documentation/devicetree/bindings/nvmem/qcom,spmi-sdam.yaml >> b/Documentation/devicetree/bindings/nvmem/qcom,spmi-sdam.yaml >> new file mode 100644 >> index 0000000..8961a99 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/nvmem/qcom,spmi-sdam.yaml >> @@ -0,0 +1,79 @@ >> +# SPDX-License-Identifier: GPL-2.0 >> +%YAML 1.2 >> +--- >> +$id: http://devicetree.org/schemas/nvmem/qcom,spmi-sdam.yaml# >> +$schema: http://devicetree.org/meta-schemas/core.yaml# >> + >> +title: Qualcomm Technologies, Inc. SPMI SDAM DT bindings >> + >> +maintainers: >> + - Shyam Kumar Thella >> + >> +description: | >> + The SDAM provides scratch register space for the PMIC clients. This >> + memory can be used by software to store information or communicate >> + to/from the PBUS. >> + >> +allOf: >> + - $ref: "nvmem.yaml#" >> + >> +properties: >> + compatible: >> + enum: >> + - qcom,spmi-sdam >> + >> + reg: >> + maxItems: 1 >> + >> + "#address-cells": >> + const: 1 >> + >> + "#size-cells": >> + const: 1 >> + >> +required: >> + - compatible >> + - reg >> + >> +patternProperties: >> + "^.*@[0-9a-f]+$": >> + type: object >> + >> + properties: >> + reg: >> + maxItems: 1 >> + description: >> + Offset and size in bytes within the storage device. >> + >> + bits: >> + maxItems: 1 >> + items: >> + items: >> + - minimum: 0 >> + maximum: 7 >> + description: >> + Offset in bit within the address range specified by >> reg. >> + - minimum: 1 >> + description: >> + Size in bit within the address range specified by >> reg. >> + >> + required: >> + - reg >> + >> + additionalProperties: false >> + >> +examples: >> + - | >> + sdam_1: nvram@b000 { >> + #address-cells = <1>; >> + #size-cells = <1>; >> + compatible = "qcom,spmi-sdam"; >> + reg = <0xb000 0x100>; >> + >> + /* Data cells */ >> + restart_reason: restart@50 { > > So this register has moved out of the PON register set? What component > in the system is going to reference this? Should it have a compatible, > in the same way as "syscon-reboot-mode" does? This is just an example for using data cells. It is not used in the system. > > Regards, > Bjorn > >> + reg = <0x50 0x1>; >> + bits = <7 2>; >> + }; >> + }; >> +... >> -- >> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora >> Forum, >> a Linux Foundation Collaborative Project