All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@ti.com>
To: "Gopinath, Thara" <thara@ti.com>
Cc: Mike Rapoport <mike.rapoport@gmail.com>,
	Mikko Rapeli <ext-mikko.rapeli@nokia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>
Subject: Re: [PATCH v2] twl4030 reboot workaround
Date: Fri, 30 Jul 2010 13:39:20 -0500	[thread overview]
Message-ID: <4C531C58.4020803@ti.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0323D40C6F@dbde02.ent.ti.com>

Gopinath, Thara wrote:
> 
>>> -----Original Message-----
>>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Mike
>>> Rapoport
>>> Sent: Friday, July 30, 2010 12:41 AM
>>> To: Mikko Rapeli
>>> Cc: linux-omap@vger.kernel.org; Turquette, Mike; sameo@linux.intel.com
>>> Subject: Re: [PATCH v2] twl4030 reboot workaround
>>>
>>> Hi
>>>
>>> On Thu, Jul 29, 2010 at 9:41 AM, Mikko Rapeli
>>> <ext-mikko.rapeli@nokia.com> wrote:
>>>> From: Mikko Rapeli <ext-mikko.rapeli@nokia.com>
>>>>
>>>> Original patch: http://marc.info/?l=linux-omap&m=126522625032441&w=2
>>>>
>>>> "Removes TWL4030 sleep script prior to rebooting, only on OMAP3. This is
>>>> necessary since DPLL3 reset causes SYS_OFFMODE pin to go low, resulting
>>>> in the sleep script being executed on TWL4030. This usually results in
>>>> VDD1 & VDD2 voltage collapse while ROM code is executing, followed by an
>>>> MPU Watch Dog reset or worse, an irrecoverable hang."
>>> I had a similar issue when my system hanged on hard reset when there
>>> was a TWL sleep script installed.
>>> The workaround I've found was to install the sleep script immediately
>>> before entering the suspend state and remove the script on the resume
>>> path.
>>> If you think that such approach is appropriate I can send a patch.
> 
> How do you hit the off state(Vdd's at 0 V) in the idle path then? Or do you do this every
> time in the idle thread also?

I do not think it is appropriate to add/remove the sleep script 
before/after every OFF mode case.  The script should be programmed once 
and left alone EXCEPT in the case of warm reset.

If there are other corner cases where SYS_OFFMODE goes low, then we 
should cover those with similar fixes to the warm reset fix, but in 
general I think the policy should be to leave the scripts alone once 
programmed

Dynamically programming/removing the scripts around OFF transitions 
increases software overhead for those transitions even more which is 
very undesirable.

Mike

> Regards
> Thara


  reply	other threads:[~2010-07-30 18:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 19:43 [RFC] OMAP3: PM: disable twl4030 sleep sequence before reboot Mike Turquette
2010-02-03 19:43 ` [PATCH 1/2] MFD: TWL4030: introduce remove_script function Mike Turquette
2010-02-03 19:43   ` [PATCH 2/2] OMAP3: PM: remove TWL4030 A2S script before reboot Mike Turquette
2010-02-09 22:35     ` Tony Lindgren
2010-07-28  9:41     ` [PATCH] twl4030 reboot workaround Mikko Rapeli
2010-07-28 10:07       ` Gopinath, Thara
2010-07-29  6:07         ` Mikko Rapeli
2010-07-28 10:18       ` Peter 'p2' De Schrijver
2010-07-29  6:06         ` Mikko Rapeli
2010-07-28 15:47       ` Mike Turquette
2010-07-29  6:16         ` Mikko Rapeli
2010-07-29  6:41           ` [PATCH v2] " Mikko Rapeli
2010-07-29 19:10             ` Mike Rapoport
2010-07-30  5:48               ` Mikko Rapeli
2010-07-30  6:35               ` Gopinath, Thara
2010-07-30 18:39                 ` Mike Turquette [this message]
2010-07-30 19:11                   ` Gopinath, Thara
2010-08-01  6:31                     ` Mike Rapoport

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=4C531C58.4020803@ti.com \
    --to=mturquette@ti.com \
    --cc=ext-mikko.rapeli@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike.rapoport@gmail.com \
    --cc=sameo@linux.intel.com \
    --cc=thara@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.