From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Stephen Boyd <stephen.boyd@linaro.org>,
Andy Gross <andy.gross@linaro.org>,
Rob Clark <robdclark@gmail.com>, Vinay Simha <simhavcs@gmail.com>,
David Brown <david.brown@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 2/2] ARM: dts: nexus7: Add regulator tweaks and wcnss entry to support wifi
Date: Sat, 13 May 2017 12:19:41 -0700 [thread overview]
Message-ID: <20170513191941.GZ15143@minitux> (raw)
In-Reply-To: <1494623898-27230-3-git-send-email-john.stultz@linaro.org>
On Fri 12 May 14:18 PDT 2017, John Stultz wrote:
> lvs7 {
> bias-pull-down;
> + regulator-always-on;
> };
Looking at the downstream regulator definition lvs7 is identified as
"pll_vdd" - which I believe is what Qualcomm abbreviates as "px". It's
supplied by S4 and as such will provide 1.8V to something. So it's quite
likely that I picked the wrong regulator in the dtsi and that this is
the px supply of the wcnss.
Unfortunately I don't have any 8064 device (with wcnss) hooked up and I
can't find any schematics :/
Would you mind changing the riva-pil vddpx-supply to &pm8921_lvs7 and
give this a spin?
Regards,
Bjorn
prev parent reply other threads:[~2017-05-13 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 21:18 [RFC][PATCH 0/2] Few DTS changes needed for Nexus7 support John Stultz
2017-05-12 21:18 ` [PATCH 1/2] ARM: dts: qcom-apq8064: Collapse usb support into one node John Stultz
2017-05-14 3:23 ` Bjorn Andersson
2017-05-12 21:18 ` [PATCH 2/2] ARM: dts: nexus7: Add regulator tweaks and wcnss entry to support wifi John Stultz
2017-05-13 19:19 ` Bjorn Andersson [this message]
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=20170513191941.GZ15143@minitux \
--to=bjorn.andersson@linaro.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.dechesne@linaro.org \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=simhavcs@gmail.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stephen.boyd@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