linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ravi Kumar Bokka <rbokka@codeaurora.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	rnayak@codeaurora.org, saiprakash.ranjan@codeaurora.org,
	dhavalp@codeaurora.org, mturney@codeaurora.org,
	sparate@codeaurora.org, c_rbokka@codeaurora.org,
	mkurumel@codeaurora.org, Ravi Kumar Bokka <rbokka@codeaurora.org>
Subject: [RFC v1 0/3] Add QTI QFPROM-Efuse driver support
Date: Tue, 12 May 2020 23:47:57 +0530	[thread overview]
Message-ID: <1589307480-27508-1-git-send-email-rbokka@codeaurora.org> (raw)

This patch series adds qfprom-efuse controller driver support.

This driver can access the raw qfprom regions for fuse blowing.

The current existed qfprom driver is only supports for cpufreq, thermal sensors
drivers by read out calibration data, speed bins..etc which is stored by
qfprom efuses. 

Ravi Kumar Bokka (3):
  dt-bindings: nvmem: Add devicetree bindings for qfprom-efuse
  drivers: nvmem: Add driver for QTI qfprom-efuse support
  arm64: dts: qcom: sc7180: Add qfprom-efuse

 .../devicetree/bindings/nvmem/qfprom-efuse.yaml    |  40 ++
 arch/arm64/boot/dts/qcom/sc7180-idp.dts            |   4 +
 arch/arm64/boot/dts/qcom/sc7180.dtsi               |   9 +
 drivers/nvmem/Kconfig                              |  10 +
 drivers/nvmem/Makefile                             |   2 +
 drivers/nvmem/qfprom-efuse.c                       | 476 +++++++++++++++++++++
 6 files changed, 541 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/nvmem/qfprom-efuse.yaml
 create mode 100644 drivers/nvmem/qfprom-efuse.c

-- 
Qualcomm INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by the Linux Foundation.


             reply	other threads:[~2020-05-12 18:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 18:17 Ravi Kumar Bokka [this message]
2020-05-12 18:17 ` [RFC v1 1/3] dt-bindings: nvmem: Add devicetree bindings for qfprom-efuse Ravi Kumar Bokka
2020-05-12 22:36   ` Rob Herring
2020-05-12 23:03   ` Doug Anderson
2020-05-12 18:17 ` [RFC v1 2/3] drivers: nvmem: Add driver for QTI qfprom-efuse support Ravi Kumar Bokka
2020-05-12 19:20   ` Randy Dunlap
2020-05-12 23:02   ` Doug Anderson
2020-05-13 13:20   ` Srinivas Kandagatla
2020-05-14 12:26     ` Ravi Kumar Bokka (Temp)
2020-05-14 18:21       ` Doug Anderson
2020-05-17 14:57         ` Ravi Kumar Bokka (Temp)
2020-05-18 10:33         ` Ravi Kumar Bokka (Temp)
2020-05-15 11:09       ` Srinivas Kandagatla
2020-05-18 10:39         ` Ravi Kumar Bokka (Temp)
2020-05-18 10:44           ` Srinivas Kandagatla
2020-05-18 18:31             ` Doug Anderson
2020-05-20 14:35               ` Srinivas Kandagatla
2020-05-20 22:48                 ` Doug Anderson
2020-05-21 15:00                   ` Srinivas Kandagatla
2020-05-21 15:10                     ` Doug Anderson
2020-05-21 15:55                       ` Srinivas Kandagatla
2020-05-21 21:28                         ` Doug Anderson
2020-05-22 11:18                           ` Srinivas Kandagatla
2020-05-26 22:31                             ` Doug Anderson
2020-06-01  9:24                               ` Srinivas Kandagatla
2020-06-01 18:08                                 ` Doug Anderson
2020-06-02 10:56                                   ` Srinivas Kandagatla
2020-05-12 18:18 ` [RFC v1 3/3] arm64: dts: qcom: sc7180: Add qfprom-efuse Ravi Kumar Bokka
2020-05-12 23:03 ` [RFC v1 0/3] Add QTI QFPROM-Efuse driver support Doug Anderson
     [not found]   ` <fb7f601f-388f-8a77-bb22-e1398f90326f@codeaurora.org>
2020-05-14 18:21     ` 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=1589307480-27508-1-git-send-email-rbokka@codeaurora.org \
    --to=rbokka@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=rnayak@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).