[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <412459f3ebb4297b2c21adbb1b9903c6@codeaurora.org>
Date: Tue, 31 Dec 2019 12:13:15 +0530
From: sthella@...eaurora.org
To: Bjorn Andersson <bjorn.andersson@...aro.org>
Cc: agross@...nel.org, srinivas.kandagatla@...aro.org,
robh+dt@...nel.org, mark.rutland@....com,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: nvmem: add binding for QTI SPMI SDAM
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 <sthella@...eaurora.org>
>> ---
>> .../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 <sthella@...eaurora.org>
>> +
>> +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@...0 {
>> + #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
Powered by blists - more mailing lists