devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Komal Bajaj <quic_kbajaj@quicinc.com>
To: <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>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support
Date: Mon, 24 Jul 2023 14:10:36 +0530	[thread overview]
Message-ID: <15e5e159-643e-06bd-c6a3-51e4935d340f@quicinc.com> (raw)
In-Reply-To: <20230724083849.8277-1-quic_kbajaj@quicinc.com>

Sorry for the spam, sent the same series twice.

Thanks
Komal

On 7/24/2023 2:08 PM, Komal Bajaj wrote:
> Changes in v5 -
>   - Separating this from original series [1].
>   - Added description of driver to secure qfprom binding.
>   - Replaced pm_runtime_enable() withh devm_pm_runtime_enable().
>   - Changed module license to GPL instead of GPL v2.
>
> This series introduces a new driver for reading secure fuse region and adding
> dt-bindings for same.
>
> [1] https://lore.kernel.org/linux-arm-msm/20230623141806.13388-1-quic_kbajaj@quicinc.com/
>
>
> Komal Bajaj (2):
>    dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom
>    nvmem: sec-qfprom: Add Qualcomm secure QFPROM support
>
>   .../bindings/nvmem/qcom,sec-qfprom.yaml       |  58 ++++++++++
>   drivers/nvmem/Kconfig                         |  13 +++
>   drivers/nvmem/Makefile                        |   2 +
>   drivers/nvmem/sec-qfprom.c                    | 101 ++++++++++++++++++
>   4 files changed, 174 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/nvmem/qcom,sec-qfprom.yaml
>   create mode 100644 drivers/nvmem/sec-qfprom.c
>
> --
> 2.40.1
>


  parent reply	other threads:[~2023-07-24  8:41 UTC|newest]

Thread overview: 19+ 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
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 ` Komal Bajaj [this message]
2023-07-24 16:53 ` [PATCH v5 0/2] " 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

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=15e5e159-643e-06bd-c6a3-51e4935d340f@quicinc.com \
    --to=quic_kbajaj@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=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;
as well as URLs for NNTP newsgroup(s).