public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Trimarchi <trimarchimichael@yahoo.it>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Victor <linux@maxim.org.za>,
	Anti Sullin <anti.sullin@artecdesign.ee>
Subject: Re: [PATCH] atmel_serial: update the powersave handler to match serial core
Date: Fri, 19 Sep 2008 16:33:09 +0000 (GMT)	[thread overview]
Message-ID: <866907.89401.qm@web26206.mail.ukl.yahoo.com> (raw)

Hi,



----- Messaggio originale -----
> Da: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
> A: Michael Trimarchi <trimarchimichael@yahoo.it>
> Cc: linux-serial@vger.kernel.org; linux-kernel@vger.kernel.org; Andrew Victor <linux@maxim.org.za>; Anti Sullin <anti.sullin@artecdesign.ee>
> Inviato: Venerdì 19 settembre 2008, 18:15:51
> Oggetto: Re: [PATCH] atmel_serial: update the powersave handler to match serial core
> 

> I agree it would be useful. It would require changing the port mux
> configuration from the driver though, and there's no standardized
> interface for doing that. Maybe this is a good motivation to come up
> with one?
> 

I think that a driver can do the request to a the gpio layer (may can be implemented
by the gpio-lib ) and give it only the gpio. The "gpio-lib" can save and restore
the status of the gpio, and request the handler, passing the gpio-id as 
a data. So when the handler fire, we can now which peripheral is
interested on the wake-up event.

> Btw, I assume the first character you receive will be lost when you do
> this, right?
>

Yes, I haven't done a lot of test to see how many chars are lost (sure one I think). 
Depends on the time spent after

 /* Wait for interrupt to wake us up */ 
  mcr p15, 0, r0, c7, c0, 4 
 
> Haavard

Regards Michael


__________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi 
http://mail.yahoo.it 

             reply	other threads:[~2008-09-19 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-19 16:33 Michael Trimarchi [this message]
2008-09-19 18:35 ` [PATCH] atmel_serial: update the powersave handler to match serial core Haavard Skinnemoen
2008-09-19 21:49   ` Anti Sullin
2008-09-20 13:01     ` Haavard Skinnemoen
  -- strict thread matches above, loose matches on Subject: below --
2008-09-20  9:31 Michael Trimarchi
2008-09-19 16:01 Michael Trimarchi
2008-09-19 16:15 ` Haavard Skinnemoen
2008-09-19 15:33 Michael Trimarchi
2008-09-19 15:46 ` Haavard Skinnemoen
2008-09-19 15:11 Haavard Skinnemoen
2008-09-19 15:19 ` Anti Sullin

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=866907.89401.qm@web26206.mail.ukl.yahoo.com \
    --to=trimarchimichael@yahoo.it \
    --cc=anti.sullin@artecdesign.ee \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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