From: Randy Dunlap <rdunlap@infradead.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,
rnayak@codeaurora.org, saiprakash.ranjan@codeaurora.org,
dhavalp@codeaurora.org, mturney@codeaurora.org,
sparate@codeaurora.org, c_rbokka@codeaurora.org,
mkurumel@codeaurora.org
Subject: Re: [RFC v1 2/3] drivers: nvmem: Add driver for QTI qfprom-efuse support
Date: Tue, 12 May 2020 12:20:51 -0700 [thread overview]
Message-ID: <ceb55c31-ae49-213a-6d12-7c55cb78b60d@infradead.org> (raw)
In-Reply-To: <1589307480-27508-3-git-send-email-rbokka@codeaurora.org>
On 5/12/20 11:17 AM, Ravi Kumar Bokka wrote:
> diff --git a/drivers/nvmem/Kconfig b/drivers/nvmem/Kconfig
> index d7b7f6d..c9345c5 100644
> --- a/drivers/nvmem/Kconfig
> +++ b/drivers/nvmem/Kconfig
> @@ -121,6 +121,16 @@ config QCOM_QFPROM
> This driver can also be built as a module. If so, the module
> will be called nvmem_qfprom.
>
> +config QTI_QFPROM_EFUSE
> + tristate "QTI_QFPROM_EFUSE Support"
> + depends on HAS_IOMEM
> + help
> + Say y here to enable QFPROM-Efuse support. This driver provides access
access to
> + QTI qfprom efuse via nvmem interface.
> +
> + This driver can also be built as a module. If so, the module
> + will be called nvmem_qfprom-efuse.
The last 3 non-blank lines should be indented with one tab + 2 spaces
instead of lots of spaces.
> +
> config NVMEM_SPMI_SDAM
> tristate "SPMI SDAM Support"
> depends on SPMI
--
~Randy
next prev parent reply other threads:[~2020-05-12 19:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 18:17 [RFC v1 0/3] Add QTI QFPROM-Efuse driver support Ravi Kumar Bokka
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 [this message]
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=ceb55c31-ae49-213a-6d12-7c55cb78b60d@infradead.org \
--to=rdunlap@infradead.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=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).