From: michael <trimarchi@gandalf.sssup.it>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: David Brownell <david-b@pacbell.net>,
linux-kernel@vger.kernel.org, Andrew Victor <linux@maxim.org.za>
Subject: Re: at91sam9260 wakeup on serial port
Date: Wed, 30 Jan 2008 01:37:38 +0100 [thread overview]
Message-ID: <479FC6D2.7040707@gandalf.sssup.it> (raw)
In-Reply-To: <20080128195114.33d7616d@dhcp-252-066.norway.atmel.com>
Hi,
> On Mon, 28 Jan 2008 10:21:57 -0800
> David Brownell <david-b@pacbell.net> wrote:
>
> There's a separate WAKE_N pin that is completely asynchronous, so with
> some external logic, we can probably wake up the CPU all the way from
> Static mode if a given input state is present. But that's definitely
> "board specific" territory, and starting the oscillators take a _long_
> time on the AP7000 (especially the 32 kHz, but then again, it barely
> consumes any power, so we might as well keep it running and keep the
> RTC going as well.)
>
Maybe is possible to create a generic device based on the gpio to provide
wakeup solutions on suspend-ram state to the peripherals
that registered to him
serial->register_gpio_wakeup x_driver->register_gpio_wakeup
serial->suspend x_driver
| |
| |
\------> gpio_power->suspend <-----------/
serial->resume x_driver
| |
| |
\------> gpio_power->resume <------------/
|----request_irq n1
gpio_power-----|----request_irq n2
|----request_irq n3
Create an attribute on the sysfs to add a wakeup reason to the user space.
Regards Michael
next prev parent reply other threads:[~2008-01-30 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 11:15 michael
2008-01-28 13:56 ` Haavard Skinnemoen
2008-01-28 18:21 ` David Brownell
2008-01-28 18:44 ` trimarchi
2008-01-28 18:51 ` Haavard Skinnemoen
2008-01-30 0:37 ` michael [this message]
2008-01-30 3:44 ` David Brownell
2008-01-30 11:47 ` Haavard Skinnemoen
2008-01-30 18:56 ` David Brownell
2008-01-30 20:34 ` Haavard Skinnemoen
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=479FC6D2.7040707@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--cc=david-b@pacbell.net \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
/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
Powered by JetHome