From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: wake up from a serial port
Date: Fri, 31 Aug 2007 10:40:45 -0700 [thread overview]
Message-ID: <20070831174045.GK12350@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D91302742901B8CFED@dlee13.ent.ti.com>
* Woodruff, Richard <r-woodruff2@ti.com> [070827 05:21]:
> >
> > BTW, I never got the 2420 serial wake events to work, maybe they
> > need separate interrupt handlers registered. But the GPIO trick
> > should still work even if the serial wake-up events won't work.
>
> These in 2420 can't wake core from RETETION. They can wake the core
> from clockstop.
OK, thanks that explains. So multiplexing the rx lines for GPIO
temporarily is the way to go then.
> I'll throw rough numbers out for (chip) each domain has its own
> combination. Each lower state requires the previous state to be hit all
> at 1.05v. clcokstop=~1.2mA, ~retention=150uA, off=~50uA. Clock stop can
> be higher depending on the 'partial' activity necessary, and perhaps
> also lower.
OK
Tony
next prev parent reply other threads:[~2007-08-31 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 22:38 wake up from a serial port Budhee Jamaich
2007-08-27 7:06 ` Tony Lindgren
2007-08-27 8:38 ` Budhee Jamaich
2007-08-27 11:14 ` Tony Lindgren
2007-08-27 12:21 ` Woodruff, Richard
2007-08-31 17:40 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-10 8:31 + wake-up-from-a-serial-port.patch added to -mm tree akpm
[not found] ` <20070910132703.2dd92485@the-village.bc.nu>
[not found] ` <Pine.LNX.4.60.0709102251250.5200@poirot.grange>
[not found] ` <20070911081220.GA20847@flint.arm.linux.org.uk>
[not found] ` <Pine.LNX.4.60.0709111217470.19259@poirot.grange>
[not found] ` <20070911121057.34b9e066@the-village.bc.nu>
2007-09-12 18:50 ` [PATCH] wake up from a serial port Guennadi Liakhovetski
2007-09-12 21:06 ` Michael Mauch
2007-09-13 20:29 ` Guennadi Liakhovetski
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=20070831174045.GK12350@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@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.