mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Stephen Warren <swarren@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Issue seen with FET re-enable during auto discharge time
Date: Fri, 25 Oct 2013 11:16:13 +0100	[thread overview]
Message-ID: <20131025101613.GS18506@sirena.org.uk> (raw)
In-Reply-To: <5256A626.4060107@nvidia.com>

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

On Thu, Oct 10, 2013 at 06:35:42PM +0530, Laxman Dewangan wrote:
> Hi Mark,

Please send messages to advertised maintainer addresses; for me upstream
things sent to my work address will not get dealt with so quickly.

> In one of our system, we are using TPS65090 which has FET switches
> for  power control. This has also the auto discharger resistance for
> turning -off.

> We observed that when we disable the FET and re-enable before it
> completely off (during power discharge time), it does not get
> enabled. It enable only if wait for it to completely off.

> Does this mean we should also provide the disable time for tuning
> off (optional) so that disable_regulator() should return after
> actually tuning off?
> In downstream, we stressed this after putting delay and it worked fine.

This is the first time I've heard of hardware with that sort of
breakage, you probably want to interview the hardware engineers...  in
any case I'd not implement this just as a delay, it seems better to
return immediately on disable and instead store or set a timer for the
earliest time that we can reenable the regulator.  The delay can then be
implemented on enable if required.  This will be more consistent with
the normal behaviour so will avoid surprises for consumers.  Of course
this is pretty uncommon so perhaps it's as well to start off with the
trivial implementation...

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-10-25 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 13:05 Laxman Dewangan
2013-10-25 10:16 ` Mark Brown [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=20131025101613.GS18506@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@nvidia.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®