From: Rajendra Nayak <rnayak@codeaurora.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Ravi Kumar Bokka <rbokka@codeaurora.org>
Subject: Re: [PATCH 2/2] nvmem: qfprom: Add support for fuse blowing on sc7280
Date: Wed, 7 Apr 2021 12:19:38 +0530 [thread overview]
Message-ID: <758bab6a-834c-a83d-dada-813679202df8@codeaurora.org> (raw)
In-Reply-To: <CAD=FV=VT6xUmUK7Kss8cpF1wjw9tLx67wJMtiV6yTDaVYXXrqA@mail.gmail.com>
On 3/31/2021 2:49 AM, Doug Anderson wrote:
> Hi,
>
> On Wed, Mar 24, 2021 at 10:45 PM Rajendra Nayak <rnayak@codeaurora.org> wrote:
>>
>> @@ -111,6 +113,15 @@ static const struct qfprom_soc_compatible_data sc7180_qfprom = {
>> .nkeepout = ARRAY_SIZE(sc7180_qfprom_keepout)
>> };
>>
>> +static const struct nvmem_keepout sc7280_qfprom_keepout[] = {
>> + {.start = 0x128, .end = 0x148},
>> + {.start = 0x238, .end = 0x248}
>> +};
>> +
>> +static const struct qfprom_soc_compatible_data sc7280_qfprom = {
>> + .keepout = sc7280_qfprom_keepout,
>> + .nkeepout = ARRAY_SIZE(sc7280_qfprom_keepout)
>> +};
>> /**
>
> nit: blank line between structure and comment?
>
>
>> @@ -187,9 +199,9 @@ static int qfprom_enable_fuse_blowing(const struct qfprom_priv *priv,
>> * a rail shared do don't specify a max--regulator constraints
>> * will handle.
>> */
>> - ret = regulator_set_voltage(priv->vcc, 1800000, INT_MAX);
>> + ret = regulator_set_voltage(priv->vcc, qfprom_blow_uV, INT_MAX);
>> if (ret) {
>> - dev_err(priv->dev, "Failed to set 1.8 voltage\n");
>> + dev_err(priv->dev, "Failed to set %duV\n", qfprom_blow_uV);
>
> nit: the comment above this block (not in the unified diff)
> specifically calls out 1.8V. It'd be nice if you updated the comment
> since it's no longer fixed at 1.8V.
>
>
>> @@ -379,6 +399,8 @@ static int qfprom_probe(struct platform_device *pdev)
>>
>> if (major_version == 7 && minor_version == 8)
>> priv->soc_data = &qfprom_7_8_data;
>> + if (major_version == 7 && minor_version == 15)
>> + priv->soc_data = &qfprom_7_15_data;
>
> nit: "else if" instead of "if"?
>
>
> I guess I'm a little late since I think this already got applied, but
> all the above are nits. Maybe you could send a follow-up patch to
> address them?
Thanks Doug for the review, yes, I'll send a follow-up patch since
Srini already has these pulled in.
--
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-04-07 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 5:44 [PATCH 1/2] dt-bindings: nvmem: Add SoC compatible for sc7280 Rajendra Nayak
2021-03-25 5:44 ` [PATCH 2/2] nvmem: qfprom: Add support for fuse blowing on sc7280 Rajendra Nayak
2021-03-30 21:19 ` Doug Anderson
2021-04-07 6:49 ` Rajendra Nayak [this message]
2021-03-27 17:40 ` [PATCH 1/2] dt-bindings: nvmem: Add SoC compatible for sc7280 Rob Herring
2021-03-30 10:52 ` 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=758bab6a-834c-a83d-dada-813679202df8@codeaurora.org \
--to=rnayak@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rbokka@codeaurora.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