From: Mark Brown <broonie@kernel.org>
To: Peter Chen <peter.chen@freescale.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com
Subject: Re: parent/child hierarchy for regulator
Date: Thu, 5 Mar 2015 12:22:34 +0000 [thread overview]
Message-ID: <20150305122234.GL21293@sirena.org.uk> (raw)
In-Reply-To: <20150305103534.GA19600@shlinux2>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
On Thu, Mar 05, 2015 at 06:35:36PM +0800, Peter Chen wrote:
> Any good ways at code/dts to show parent/child hierarchy for regulator?
There's plenty of examples in mainline...
> The related regulators at my platforms like below:
> PMIC (SWB 5v) --> Switch Chip (GPIO Regulator) --> USB VBUS
> PMIC has one 5V regulator (eg, swbst at pfuse), and it is the input
> for USB power switch chip, and there are two gpios at this switch
> chip to control if 5V is output or not, we register these two gpios as
> fixed regulators, currently, if regulator swbst is disabled, the
> gpio regulator has no way to know, and cause the vbus voltage is wrong.
Can you please clarify why you're registering two fixed voltage
regulators for the switch chip and how you're doing that? The picture
above looks like you should just have a single regulator there and
nothing should care if the either regulator is enabled when querying the
parent for its voltage.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-03-05 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 10:35 Peter Chen
2015-03-05 12:18 ` Stefan Wahren
2015-03-06 2:40 ` Peter Chen
2015-03-05 12:22 ` Mark Brown [this message]
2015-03-06 2:51 ` Peter Chen
2015-03-06 7:18 ` Peter Chen
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=20150305122234.GL21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@freescale.com \
/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
Powered by JetHome