public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Igor Stoppa <igor.stoppa@nokia.com>
To: "ext Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Kevin Hilman <khilman@deeprootsystems.com>
Subject: RE: [PATCH 0/3] OMAP: PM: enable UART clock disabling when idle
Date: Mon, 01 Dec 2008 08:07:08 +0200	[thread overview]
Message-ID: <1228111628.26105.15.camel@localhost> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE8967162036CE5028C@dlee02.ent.ti.com>

On Sat, 2008-11-29 at 21:35 -0600, ext Woodruff, Richard wrote:
> > From: Igor Stoppa [mailto:igor.stoppa@nokia.com]
> > Sent: Saturday, November 29, 2008 10:07 AM
> 
> > On Sat, 2008-11-29 at 07:55 -0600, ext Woodruff, Richard wrote:
> >
> > > Not unless you use some kind of flow control or protocol retransmits.
> >
> > What about bitbanging the entire first character?
> 
> Huh?
> 
> Typically for development you are just hooked to your PC.  It doesn't do anything special.

but for some reason there seemed to be people who did now want to loose
the first character, so i was wondering if the entire first character
could be bitbanged in gpio mode and put into the sw buffer for the
serial port, which would be reinserted into the foodchain after the
completion of the first character.

Of course in the case of human input it would probably mean that all the
characters could be bitbanged, if the timeout for entering low power
states is short enough, but wouldn't that be very close to reality
where, like in the internet tablets, the serial port is disabled in
production mode?

What we usually see is that during development as soon as we enable
production mode (iow no active serial port, not even with timeout) those
drivers which were relying on it to provide some sort of wakeup, fail.

Just a thought.

-- 

Cheers, Igor

---

Igor Stoppa
Maemo Software - Nokia Devices R&D - Helsinki

      reply	other threads:[~2008-12-01  6:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27  0:29 [PATCH 0/3] OMAP: PM: enable UART clock disabling when idle Kevin Hilman
2008-11-27  0:29 ` [PATCH 1/3] OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X Kevin Hilman
2008-11-27  0:29   ` [PATCH 2/3] OMAP3: PM: UART: disable clocks when idle Kevin Hilman
2008-11-27  0:30     ` [PATCH 3/3] OMAP3: PM: UART save/restore support for OFF-mode Kevin Hilman
2008-11-29 12:52 ` [PATCH 0/3] OMAP: PM: enable UART clock disabling when idle Felipe Contreras
2008-11-29 13:55   ` Woodruff, Richard
2008-11-29 16:06     ` Igor Stoppa
2008-11-30  3:35       ` Woodruff, Richard
2008-12-01  6:07         ` Igor Stoppa [this message]

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=1228111628.26105.15.camel@localhost \
    --to=igor.stoppa@nokia.com \
    --cc=felipe.contreras@gmail.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox