linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: PXA: Zipit Z2: Fix oops in z2_power_off
Date: Mon, 9 Jan 2012 17:25:04 +0100	[thread overview]
Message-ID: <201201091725.04631.marek.vasut@gmail.com> (raw)
In-Reply-To: <20120109132100.GO21765@n2100.arm.linux.org.uk>

> On Mon, Jan 09, 2012 at 01:38:29PM +0100, Marek Vasut wrote:
> > > On Mon, Jan 09, 2012 at 01:13:31PM +0100, Marek Vasut wrote:
> > > > > 2012/1/9 Marek Vasut <marek.vasut@gmail.com>:
> > > > > >> Nope, it does not work. Looks like device disables power on
> > > > > >> memory in deepsleep.
> > > > > > 
> > > > > > Why?
> > > > > 
> > > > > In deepsleep PXA27x deasserts SYS_EN pin, and looks like when it's
> > > > > deasserted there's no power on SDRAM (on Zipit). Just guess.
> > > > 
> > > > Then maybe implement suspend-to-disk ? There was a patch for omap on
> > > > the list, maybe it's even merged.
> > > 
> > > What are hell you going on about?
> > 
> > Cool your jets Russell.
> > 
> > > Why would someone want to even try
> > > implementing suspend-to-disk in the power off hook?
> > 
> > I'm not talking about the powerdown hook anymore, but a way how to avoid
> > it as much as possible via standard means.
> 
> Maybe you should state that you are deviating from the subject of this
> email thread to aid your readers understanding?

I think it was pretty clear already. OK

> 
> > > Why would you even
> > > want to try to preserve the system state in a power off hook?
> > 
> > Not in poweroff hook. Btw. I'm still convinced the bootloader should
> > handle this -- the powerdown should just reset the thing and tell
> > bootloader to deepsleep it.
> 
> Why should the boot loader be involved?  The boot loader is all about
> bringing the system _up_, not taking it down.

Why would you bloat kernel with non-standard crap? The firmware should handle 
this if the hardware is broken (and even if this sounds acpi-ish, I still 
consider this particular thing should be handled by firmware). Especially since 
what the device does in the end is simply restart anyway.

M

  reply	other threads:[~2012-01-09 16:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08  8:33 [PATCH] ARM: PXA: Zipit Z2: Fix oops in z2_power_off Vasily Khoruzhick
2012-01-08  8:56 ` Marek Vasut
2012-01-08  9:51   ` Vasily Khoruzhick
2012-01-08 10:40     ` Marek Vasut
2012-01-08 11:37       ` Russell King - ARM Linux
2012-01-08 21:40       ` Vasily Khoruzhick
2012-01-08 23:58         ` Marek Vasut
2012-01-09  8:51           ` Vasily Khoruzhick
2012-01-09 12:13             ` Marek Vasut
2012-01-09 12:17               ` Russell King - ARM Linux
2012-01-09 12:38                 ` Marek Vasut
2012-01-09 13:21                   ` Russell King - ARM Linux
2012-01-09 16:25                     ` Marek Vasut [this message]
2012-01-09 17:50                       ` Russell King - ARM Linux

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=201201091725.04631.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).