From: Mikko Rapeli <ext-mikko.rapeli@nokia.com>
To: ext Mike Rapoport <mike.rapoport@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"mturquette@ti.com" <mturquette@ti.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>
Subject: Re: [PATCH v2] twl4030 reboot workaround
Date: Fri, 30 Jul 2010 08:48:15 +0300 [thread overview]
Message-ID: <20100730054815.GN12063@edollo> (raw)
In-Reply-To: <AANLkTi=OkfRGvW05ZTOaSU+-r7jo40wHFK_pkQM9Hmw=@mail.gmail.com>
On Thu, Jul 29, 2010 at 09:10:43PM +0200, ext Mike Rapoport wrote:
> 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.
Yes, I think this patch would be a good idea too since it fixes a real
issue.
-Mikko
next prev parent reply other threads:[~2010-07-30 5:48 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 [this message]
2010-07-30 6:35 ` Gopinath, Thara
2010-07-30 18:39 ` Mike Turquette
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=20100730054815.GN12063@edollo \
--to=ext-mikko.rapeli@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=mike.rapoport@gmail.com \
--cc=mturquette@ti.com \
--cc=sameo@linux.intel.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.