From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D4501C2D0CE for ; Sun, 29 Dec 2019 03:01:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AA014206F4 for ; Sun, 29 Dec 2019 03:01:45 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="XrrMPzMc" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726626AbfL2DBn (ORCPT ); Sat, 28 Dec 2019 22:01:43 -0500 Received: from mail-pf1-f194.google.com ([209.85.210.194]:40506 "EHLO mail-pf1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726359AbfL2DBn (ORCPT ); Sat, 28 Dec 2019 22:01:43 -0500 Received: by mail-pf1-f194.google.com with SMTP id q8so16692180pfh.7 for ; Sat, 28 Dec 2019 19:01:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=otzAHEuQRQz5JEZyg1vitpEwm2qVyYHjx2AMIYobrWU=; b=XrrMPzMcmtar6QgFnxMt39dWC1wTvsaWWRW+osd5EWKZdaaGDC8Dwv2mlKiQK/X6d7 GOH6rW33UU+7iVy+U2wJ8AA7qCvFyR6jg1iC5Wg+6Xs52wUlm3bgvhrUXXa998pxzgaA t5/PONW0yAxoE6NI/uJbZvVFLHu7NnhYFOnCxmy5ulBYrQ3oaIOylK8MXclG8kfw0Byd wWtdEg5KEJRiqH+nqzIUfGTxCPmhuTt1Pr7hAxNeIx4nbLpgiYW8U+Zo0y7krpD5Qm7e zvodHOeMFH+nNmrG+psyB9IfUlC2rf/+TkV1QAfgYUU9Ndi4igWZoLY3tMCqHhOdg3iS n+8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=otzAHEuQRQz5JEZyg1vitpEwm2qVyYHjx2AMIYobrWU=; b=IfGgx2fv3lFtUT1rXLM+C1HcrqRilEinHO99+9yWzB1zTGftaNJTju0xx2yJzOLFVe LYq2RDGlIuglDxf8XjZ//yygwFSvIpzvQaNSTP+gN+blm2gydUcGSPIq1mciBzzvuCi3 cSZe+VYCWCzmr+ZiN9000SII49uwlgo7ko7TAQD8PVIsWhsiI6VNSCr34QGpbPhZ1kkC ae/jox3KVp0XKwHuZSh/V4V5flsNO0nFtaeDhvpf4mwYUUEHOAAOtWD2RnRmUlDhR6pi lKYml9R79W5WueGYsG5NciIV+msTL3ZkDWmBTkSiOxsRBD5vwsxw8DhwzQ2ZLkWXan0Z 7DvQ== X-Gm-Message-State: APjAAAVt46Bas0LA+LmCwJ08/FfjW5g+f0GHf4MwewZaX19oHZkVDZLh ujdOS8aGDNKvX2zhQeAU5kaEXg== X-Google-Smtp-Source: APXvYqxCeS5pCH3BOi6UYjDt6eJVBUTzoCmAT6O9GOajpM3LoVIJRRcsZiFJcUkwJpxqQmlJXcv5Sw== X-Received: by 2002:a63:5f45:: with SMTP id t66mr61831803pgb.198.1577588502803; Sat, 28 Dec 2019 19:01:42 -0800 (PST) Received: from builder (104-188-17-28.lightspeed.sndgca.sbcglobal.net. [104.188.17.28]) by smtp.gmail.com with ESMTPSA id g19sm46419995pfh.134.2019.12.28.19.01.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 28 Dec 2019 19:01:42 -0800 (PST) Date: Sat, 28 Dec 2019 19:01:40 -0800 From: Bjorn Andersson To: Shyam Kumar Thella 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 Message-ID: <20191229030140.GJ3755841@builder> References: <1577165532-28772-1-git-send-email-sthella@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1577165532-28772-1-git-send-email-sthella@codeaurora.org> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-arm-msm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org 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? 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