From: Rajendra Nayak <rnayak@codeaurora.org>
To: Ravi Kumar Bokka <rbokka@codeaurora.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
saiprakash.ranjan@codeaurora.org, dhavalp@codeaurora.org,
mturney@codeaurora.org, sparate@codeaurora.org,
c_rbokka@codeaurora.org, mkurumel@codeaurora.org
Subject: Re: [RFC v2 1/3] dt-bindings: nvmem: Add devicetree bindings for qfprom-efuse
Date: Thu, 11 Jun 2020 17:48:58 +0530 [thread overview]
Message-ID: <8ef8c7c4-3560-274d-3043-ddf5b87e794a@codeaurora.org> (raw)
In-Reply-To: <1591868882-16553-2-git-send-email-rbokka@codeaurora.org>
On 6/11/2020 3:18 PM, Ravi Kumar Bokka wrote:
> This patch adds dt-bindings document for qfprom-efuse controller.
there is an existing bindings doc (in .txt) which you should convert to yaml,
and then add another patch to extend it.
>
> Signed-off-by: Ravi Kumar Bokka <rbokka@codeaurora.org>
> ---
> .../devicetree/bindings/nvmem/qfprom.yaml | 52 ++++++++++++++++++++++
> 1 file changed, 52 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/qfprom.yaml
>
> diff --git a/Documentation/devicetree/bindings/nvmem/qfprom.yaml b/Documentation/devicetree/bindings/nvmem/qfprom.yaml
> new file mode 100644
> index 0000000..7c8fc31
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/qfprom.yaml
> @@ -0,0 +1,52 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/qfprom.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Technologies Inc, QFPROM Efuse bindings
> +
> +maintainers:
> + - Ravi Kumar Bokka <rbokka@codeaurora.org>
> +
> +allOf:
> + - $ref: "nvmem.yaml#"
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,qfprom
> +
> + reg:
> + maxItems: 3
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - clocks
> + - clock-names
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,gcc-sc7180.h>
> +
> + qfprom@780000 {
> + compatible = "qcom,qfprom";
> + reg = <0 0x00780000 0 0x7a0>,
> + <0 0x00782000 0 0x100>,
> + <0 0x00784000 0 0x8ff>;
> + reg-names = "raw", "conf", "corrected";
> + clocks = <&gcc GCC_SEC_CTRL_CLK_SRC>;
> + clock-names = "secclk";
> +
> + qusb2p_hstx_trim: hstx-trim-primary@25b {
> + reg = <0x25b 0x1>;
> + bits = <1 3>;
> + };
> + };
> +
> + &qfprom {
> + vcc-supply = <&vreg_l11a_1p8>;
> + };
> +
>
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2020-06-11 12:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 9:47 [RFC v2 0/3] Add QTI QFPROM-Efuse driver support Ravi Kumar Bokka
2020-06-11 9:48 ` [RFC v2 1/3] dt-bindings: nvmem: Add devicetree bindings for qfprom-efuse Ravi Kumar Bokka
2020-06-11 12:18 ` Rajendra Nayak [this message]
2020-06-12 21:58 ` Rob Herring
2020-06-12 21:59 ` Doug Anderson
2020-06-12 23:15 ` Doug Anderson
2020-06-15 10:44 ` Srinivas Kandagatla
2020-06-15 14:17 ` Rob Herring
2020-06-15 14:27 ` Doug Anderson
2020-06-15 14:28 ` Srinivas Kandagatla
2020-06-11 9:48 ` [RFC v2 2/3] drivers: nvmem: Add QTI qfprom-efuse support Ravi Kumar Bokka
2020-06-13 20:33 ` Doug Anderson
2020-06-15 10:44 ` Srinivas Kandagatla
2020-06-15 17:13 ` Doug Anderson
2020-06-17 14:54 ` Doug Anderson
2020-06-15 9:56 ` Srinivas Kandagatla
2020-06-11 9:48 ` [RFC v2 3/3] arm64: dts: qcom: sc7180: Add qfprom-efuse Ravi Kumar Bokka
2020-06-13 20:23 ` Doug Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ef8c7c4-3560-274d-3043-ddf5b87e794a@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=c_rbokka@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dhavalp@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkurumel@codeaurora.org \
--cc=mturney@codeaurora.org \
--cc=rbokka@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=sparate@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).