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-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 30 Apr 2012 15:51:59 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	NeilBrown <neilb@...e.de>, Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	linux-serial@...r.kernel.org, linux-pm@...r.kernel.org,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Question:  How to power-manage UART-attached devices.

On 04/30/2012 03:22 PM, NeilBrown wrote:
> 
> What I would really like is to integrate it closely with the state
> of the UART.  i.e. if the /dev/ttyO1 device is open, then the GPS
> is "on".  If not then it is "off".  Similarly if /dev/tty/O0 is
> open, bluetooth is "on", else "off". However I cannot find any way
> to "plug in" to the tty or serial drivers to perform an arbitrary
> action on first-open or last-close.  Is something like that
> possible? If not, is it a reasonable thing to ask? Any suggests
> about where to put such a hook?
> 

I don't think that's the right interface.  Just because the port is
currently open doesn't mean the device is active, nor vice versa.  ALL
it means is that someone currently has an access handle to it.

Since a serial port models, well, a *port*, it is logical to think of
a (hypothetical) socket containing an RS-232 connector as well as a
power outlet.  Given that, it would be logical to drive the "power
connector" using the same type of interface used for the other parts
of an RS-232 control, meaning either with termios flags or via a
dedicated control ioctl (TIOCPOWER?).

	-hpa

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ