linux-kernel - Re: [PATCH] atmel_serial: update the powersave handler to match serial core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <866907.89401.qm@web26206.mail.ukl.yahoo.com>
Date:	Fri, 19 Sep 2008 16:33:09 +0000 (GMT)
From:	Michael Trimarchi <trimarchimichael@...oo.it>
To:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
Cc:	linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
	Andrew Victor <linux@...im.org.za>,
	Anti Sullin <anti.sullin@...ecdesign.ee>
Subject: Re: [PATCH] atmel_serial: update the powersave handler to match serial core

Hi,



----- Messaggio originale -----
> Da: Haavard Skinnemoen <haavard.skinnemoen@...el.com>
> A: Michael Trimarchi <trimarchimichael@...oo.it>
> Cc: linux-serial@...r.kernel.org; linux-kernel@...r.kernel.org; Andrew Victor <linux@...im.org.za>; Anti Sullin <anti.sullin@...ecdesign.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 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/