mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: Keerthy <j-keerthy@ti.com>,
	linux-kernel@vger.kernel.org, lee.jones@linaro.org,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH] regulator: lp873x: Update the enable mask for LDOs and BUCKs
Date: Mon, 9 Oct 2017 16:50:26 +0100	[thread overview]
Message-ID: <20171009155026.63aghfli7bkemiux@sirena.co.uk> (raw)
In-Reply-To: <72182869-6102-1178-91c4-0be632d4be32@ti.com>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On Mon, Oct 09, 2017 at 06:35:14PM +0300, Tero Kristo wrote:

> The EN signal coming in to the PMIC is actually used to poweroff the system
> completely. There is no other mechanism for doing this in lp873x based
> systems, they removed the bit for controlling dev-power-off from the
> register space. If the EN bit is down for a specific regulator, it won't go
> down when attempting to poweroff the system, otherwise the state of a
> regulator is the result of (EN_PIN | EN_BIT).

This should be clear from the changelog (and probably the code as well).

> I wonder if we should tie this somehow to the system-power-controller
> property though.... If the PMIC is not system-power-controller, we should
> disable the EN_PIN_CTRL from all regulators so that they don't go down if
> the EN_PIN itself is floating for example.

Seems plausible, if someone does decided to use control at runtime the
behaviour can always be changed if the GPIO is present.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

  reply	other threads:[~2017-10-09 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 12:25 Keerthy
2017-10-09 14:20 ` Mark Brown
2017-10-09 15:35   ` Tero Kristo
2017-10-09 15:50     ` Mark Brown [this message]
2017-10-10  2:04       ` Keerthy
2017-10-10  8:55         ` Mark Brown

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=20171009155026.63aghfli7bkemiux@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=t-kristo@ti.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

all inboxes | Powered by JetHome®