From: Rajendra Nayak <rnayak@codeaurora.org>
To: Doug Anderson <dianders@chromium.org>,
Ravi Kumar Bokka <rbokka@codeaurora.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
dhavalp@codeaurora.org, mturney@codeaurora.org
Subject: Re: [PATCH] drivers: nvmem: Fix voltage settings for QTI qfprom-efuse
Date: Thu, 25 Mar 2021 12:45:28 +0530 [thread overview]
Message-ID: <4956f067-4079-84b4-191d-c1036e04c42f@codeaurora.org> (raw)
In-Reply-To: <CAD=FV=W9YWxVY6cEEXBr1wMcMzEPak3PeyROSvmnOWewL9BiUQ@mail.gmail.com>
On 2/5/2021 8:25 PM, Doug Anderson wrote:
> Hi,
>
> On Fri, Feb 5, 2021 at 3:29 AM Ravi Kumar Bokka <rbokka@codeaurora.org> wrote:
>>
>> QFPROM controller hardware requires 1.8V min for fuse blowing.
>> So, this change sets the voltage to 1.8V, required to blow the fuse
>> for qfprom-efuse controller.
>>
>> To disable fuse blowing, we set the voltage to 0V since this may
>> be a shared rail and may be able to run at a lower rate when we're
>> not blowing fuses.
>>
>> Fixes: 93b4e49f8c86 ("nvmem: qfprom: Add fuse blowing support")
>> Reported-by: Douglas Anderson <dianders@chromium.org>
>> Suggested-by: Douglas Anderson <dianders@chromium.org>
>> Signed-off-by: Ravi Kumar Bokka <rbokka@codeaurora.org>
>> ---
>> drivers/nvmem/qfprom.c | 21 +++++++++++++++++++++
>> 1 file changed, 21 insertions(+)
>>
>> diff --git a/drivers/nvmem/qfprom.c b/drivers/nvmem/qfprom.c
>> index 6cace24..100d69d 100644
>> --- a/drivers/nvmem/qfprom.c
>> +++ b/drivers/nvmem/qfprom.c
>> @@ -127,6 +127,16 @@ static void qfprom_disable_fuse_blowing(const struct qfprom_priv *priv,
>> {
>> int ret;
>>
>> + /*
>> + * This may be a shared rail and may be able to run at a lower rate
>> + * when we're not blowing fuses. At the moment, the regulator framework
>> + * applies voltage constraints even on disabled rails, so remove our
>> + * constraints and allow the rail to be adjusted by other users.
>
> Some year maybe I'll try to fix the regulator framework to not count
> voltage constraints for disbled rails, or perhaps have it be optional.
> ;-) In theory it should be much easier after the patches we already
> landed not to count current requests for disabled rails...
>
>
>> + */
>> + ret = regulator_set_voltage(priv->vcc, 0, INT_MAX);
>> + if (ret)
>> + dev_warn(priv->dev, "Failed to set 0 voltage (ignoring)\n");
>> +
>> ret = regulator_disable(priv->vcc);
>> if (ret)
>> dev_warn(priv->dev, "Failed to disable regulator (ignoring)\n");
>> @@ -172,6 +182,17 @@ static int qfprom_enable_fuse_blowing(const struct qfprom_priv *priv,
>> goto err_clk_prepared;
>> }
>>
>> + /*
>> + * Hardware requires 1.8V min for fuse blowing; this may be
>> + * a rail shared do don't specify a max--regulator constraints
>> + * will handle.
>> + */
>> + ret = regulator_set_voltage(priv->vcc, 1800000, INT_MAX);
>> + if (ret) {
>> + dev_err(priv->dev, "Failed to set 1.8 voltage\n");
>> + goto err_clk_rate_set;
>> + }
>> +
>
> Looks right to me. Assuming that this works.
>
> Reviewed-by: Douglas Anderson <dianders@chromium.org>
Srini, any plans to queue this up for merge?
--
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:[~2021-03-25 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 11:28 [PATCH] drivers: nvmem: Fix voltage settings for QTI qfprom-efuse Ravi Kumar Bokka
2021-02-05 14:55 ` Doug Anderson
2021-03-25 7:15 ` Rajendra Nayak [this message]
2021-03-25 14:39 ` Srinivas Kandagatla
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=4956f067-4079-84b4-191d-c1036e04c42f@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dhavalp@codeaurora.org \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturney@codeaurora.org \
--cc=rbokka@codeaurora.org \
--cc=saiprakash.ranjan@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).