All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Budhee Jamaich <budheej@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: wake up from a serial port
Date: Mon, 27 Aug 2007 04:14:06 -0700	[thread overview]
Message-ID: <20070827111405.GD13538@atomide.com> (raw)
In-Reply-To: <57314e840708270138y2c270362i54fd928538a80a87@mail.gmail.com>

* Budhee Jamaich <budheej@gmail.com> [070827 01:38]:
> On 8/27/07, Tony Lindgren <tony@atomide.com> wrote:
> > * Budhee Jamaich <budheej@gmail.com> [070827 00:00]:
> > > i am working on 2430 and I need to enable
> > > wakeup from a serial port.
> > >
> > > a patch which does this very thing has just been posted on lkml:
> > > http://article.gmane.org/gmane.linux.kernel/574545
> > >
> > > is it relevant to me ?
> > >
> > > or is there already a way to do that ?
> >
> > You also need to use the omap serial wake-up events, or mux rx pin
> > temporarily to a wake-up capable GPIO pin.
> 
> Are there any examples how to do either of these ?

Well it used to work at least for 5912OSK. Maybe grep for 
CONFIG_OMAP_SERIAL_WAKE.

> If I mux the rx pin to a wake-up capable GPIO pin - should I still apply the
> patch I mentioned above ?

That means you still have to have the functional clock for the UART
on, which will block omap retention. So using the async GPIO wake-up
events will be better.

> (And how can I do this muxing ? Is there an API for that ?)

See CONFIG_OMAP_SERIAL_WAKE.

> Thank you very much Tony.

No problem, if you get it working on 2430, please send patches :)

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.

Regards,

Tony

  reply	other threads:[~2007-08-27 11:14 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 [this message]
2007-08-27 12:21       ` Woodruff, Richard
2007-08-31 17:40         ` Tony Lindgren
  -- 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=20070827111405.GD13538@atomide.com \
    --to=tony@atomide.com \
    --cc=budheej@gmail.com \
    --cc=linux-omap-open-source@linux.omap.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.