linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Laxman Dewangan
	<ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: Remove 3.3V supply and modem regulators
Date: Tue, 07 Jan 2014 09:43:43 -0700	[thread overview]
Message-ID: <52CC2EBF.60106@wwwdotorg.org> (raw)
In-Reply-To: <52CBEF89.6090901-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

On 01/07/2014 05:14 AM, Laxman Dewangan wrote:
> On Tuesday 07 January 2014 02:29 AM, Stephen Warren wrote:
>> On 01/06/2014 08:25 AM, Thierry Reding wrote:
>>> GPIO 1 and 2 of the PMIC are not used for the described purpose, so
>>> remove them.
>> As far as I can tell, this patch is correct, since those GPIOs are in
>> fact used to discharge the rails after disabling them, rather than to
>> enable/disable the rails.
>>
>> Equally, these GPIOs affect multiple rails at once, so listing the GPIO
>> as a property of a single regulator seems wrong either way.
>>
>> However, PMU_REGEN1 does seem to feed the "EN" pin of U13C1, a DC/DC
>> switcher for power rail 3.3v_modem, so perhaps there's more going on
>> here than I see?
>>
>> In summary, I need Laxman to comment on this and ack the change, and
>> explain why these GPIOs were listed as regulator enables when it doesn't
>> seem that they are.
>>
> PMU_REGEN1 is going to U13C1 (DCDC switcher). So if EN is 0, the output
> will be 0 and when it is 1, the output will be 3.3V.
> Because this is coming from GPIO, it is added as the fixed regulator.

What about PMU_REGEN3, for which that isn't the case, and what about the
fact that PMU_REGEN1 does a lot more than just enable that DC/DC switcher?

  parent reply	other threads:[~2014-01-07 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 15:25 [PATCH] ARM: tegra: Remove 3.3V supply and modem regulators Thierry Reding
     [not found] ` <1389021933-6675-1-git-send-email-treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-01-06 20:59   ` Stephen Warren
     [not found]     ` <52CB192F.2020700-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-01-07 12:14       ` Laxman Dewangan
     [not found]         ` <52CBEF89.6090901-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-01-07 16:43           ` Stephen Warren [this message]
     [not found]             ` <52CC2EBF.60106-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-01-08 13:04               ` Laxman Dewangan
2014-01-08 13:41       ` Thierry Reding

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=52CC2EBF.60106@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).