All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Rajendra Nayak <rnayak@codeaurora.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.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 (Temp)" <rbokka@codeaurora.org>
Subject: Re: [PATCH] arm64: dts: qcom: sc7280-idp: Add vcc-supply for qfprom
Date: Mon, 13 Sep 2021 14:19:08 -0700	[thread overview]
Message-ID: <CAD=FV=UV4odosuOTKCdQCa4pmMEF0gn_eKmsR-2FEtt_eF+98w@mail.gmail.com> (raw)
In-Reply-To: <CAE-0n51miUjP4dg4wQR_JBwNNvMNqAafv7jFvEKU+MrfQmhV5A@mail.gmail.com>

Hi,

On Mon, Sep 13, 2021 at 12:57 PM Stephen Boyd <swboyd@chromium.org> wrote:
>
> Quoting Rajendra Nayak (2021-09-13 03:58:55)
> > Add vcc-supply for the IDP boards that was missed when the
> > qfprom device tree properties were added for the sc7280 SoC.
> >
> > Fixes: c1b2189a19cf ("arm64: dts: qcom: sc7280: Add qfprom node")
> > Reported-by: satya priya <skakit@codeaurora.org>
> > Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> > ---
>
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>
>
> >  arch/arm64/boot/dts/qcom/sc7280-idp.dtsi | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/sc7280-idp.dtsi b/arch/arm64/boot/dts/qcom/sc7280-idp.dtsi
> > index 371a2a9..99f9ee5 100644
> > --- a/arch/arm64/boot/dts/qcom/sc7280-idp.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/sc7280-idp.dtsi
> > @@ -207,6 +207,10 @@
> >         };
> >  };
> >
> > +&qfprom {
>
> Maybe that node should also be marked status = "disabled" by default so
> that it can only be marked OK if the board has setup the regulator
> properly?

I don't think that's a good idea. You still want to be able to use the
nvmem in "read only" mode and it doesn't seem to need the regulator
for that. This is only for burning.

I believe that actually everything will work out fine-ish for boards
that leave this regulator off. They'll get a dummy regulator. When
they start trying to burn fuses and the call the
regulator_set_voltage() happens then that'll fail (you can't do that
on a dummy) and we should error out of writing. Reading will work
fine. It would probably be better if qfprom_probe() used
devm_regulator_get_optional() though and fell back to read-only mode.
I'm happy to review a patch that does that.

-Doug

  reply	other threads:[~2021-09-13 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 10:58 [PATCH] arm64: dts: qcom: sc7280-idp: Add vcc-supply for qfprom Rajendra Nayak
2021-09-13 19:57 ` Stephen Boyd
2021-09-13 21:19   ` Doug Anderson [this message]
2021-09-13 21:38 ` 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='CAD=FV=UV4odosuOTKCdQCa4pmMEF0gn_eKmsR-2FEtt_eF+98w@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbokka@codeaurora.org \
    --cc=rnayak@codeaurora.org \
    --cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.