From: Pavan Kondeti <quic_pkondeti@quicinc.com>
To: Komal Bajaj <quic_kbajaj@quicinc.com>
Cc: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<srinivas.kandagatla@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom
Date: Thu, 27 Jul 2023 14:39:41 +0530 [thread overview]
Message-ID: <33f2d056-e65d-4bc2-8a1b-bb5815752014@quicinc.com> (raw)
In-Reply-To: <20230724083849.8277-2-quic_kbajaj@quicinc.com>
On Mon, Jul 24, 2023 at 02:08:48PM +0530, Komal Bajaj wrote:
> This patch adds bindings for secure qfprom found in QCOM SOCs.
> Secure QFPROM driver is based on simple nvmem framework.
>
> Signed-off-by: Komal Bajaj <quic_kbajaj@quicinc.com>
> ---
> .../bindings/nvmem/qcom,sec-qfprom.yaml | 58 +++++++++++++++++++
> 1 file changed, 58 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/qcom,sec-qfprom.yaml
>
[...]
> +$id: http://devicetree.org/schemas/nvmem/qcom,sec-qfprom.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm Technologies Inc, Secure QFPROM Efuse
> +
> +maintainers:
> + - Komal Bajaj <quic_kbajaj@quicinc.com>
> +
> +description: |
> + For some of the Qualcomm SoC's, it is possible that
> + the qfprom region is protected from non-secure access.
> + In such situations, linux will have to use secure calls
> + to read the region.
> +
> +allOf:
> + - $ref: nvmem.yaml#
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - qcom,qdu1000-sec-qfprom
> + - const: qcom,sec-qfprom
> +
> + reg:
> + items:
> + - description: The secure qfprom corrected region.
> +
> +required:
> + - compatible
> + - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/qcom,gcc-sc7180.h>
> +
minor nitpick:
Since this device does not have any clocks, the above header inclusion
can be dropped.
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + efuse@221c8000 {
> + compatible = "qcom,qdu1000-sec-qfprom", "qcom,sec-qfprom";
> + reg = <0 0x221c8000 0 0x1000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + multi_chan_ddr: multi-chan-ddr@12b {
> + reg = <0x12b 0x1>;
> + bits = <0 2>;
> + };
> + };
> + };
> +
Thanks,
Pavan
next prev parent reply other threads:[~2023-07-27 9:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 8:38 [PATCH v5 0/2] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support Komal Bajaj
2023-07-24 8:38 ` [PATCH v5 1/2] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom Komal Bajaj
2023-07-26 16:40 ` Rob Herring
2023-07-28 13:54 ` Komal Bajaj
2023-07-27 9:09 ` Pavan Kondeti [this message]
2023-07-28 13:57 ` Komal Bajaj
2023-07-24 8:38 ` [PATCH v5 2/2] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support Komal Bajaj
2023-07-26 6:17 ` Bjorn Andersson
2023-07-27 6:39 ` Mukesh Ojha
2023-07-27 13:26 ` Mukesh Ojha
2023-07-31 16:35 ` Bjorn Andersson
2023-08-01 6:10 ` Komal Bajaj
2023-07-27 10:44 ` Srinivas Kandagatla
2023-07-28 8:25 ` Mukesh Ojha
2023-08-01 6:11 ` Komal Bajaj
2023-07-24 8:40 ` [PATCH v5 0/2] " Komal Bajaj
2023-07-24 16:53 ` Conor Dooley
2023-07-24 16:54 ` Conor Dooley
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 8:29 Komal Bajaj
2023-07-24 8:29 ` [PATCH v5 1/2] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom Komal Bajaj
2023-07-24 9:48 ` Krzysztof Kozlowski
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=33f2d056-e65d-4bc2-8a1b-bb5815752014@quicinc.com \
--to=quic_pkondeti@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_kbajaj@quicinc.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®