From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: NeilBrown <neilb@suse.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Peter Hurley <peter@hurleysoftware.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sebastian Reichel <sre@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Jiri Slaby <jslaby@suse.cz>, NeilBrown <neil@brown.name>,
devicetree@vger.kernel.org,
GTA04 owners <gta04-owner@goldelico.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] misc: add a driver to power on/off UART attached devices.
Date: Sat, 20 Dec 2014 12:50:20 +0000 [thread overview]
Message-ID: <20141220125020.49d0bba0@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20141220000920.13943.50943.stgit@notabene.brown>
On Sat, 20 Dec 2014 11:09:21 +1100
NeilBrown <neilb@suse.de> wrote:
> If a platform has a particular device permanently attached to a UART,
> there may be out-of-band signaling necessary to power the device
> on and off.
>
> This drive controls that signalling for a number of different devices.
> It can
> - enable/disable a regulator
> - toggle a GPIO
> - register an 'rfkill' which can for the device to be off.
>
> When the rfkill is absent of unblocked, the device will be on when the
> associated tty device is open, and closed otherwise.
>
Looks sound to me. Would drivers/tty/slave/.. be a better place for
these to collect up than "misc" ?
next prev parent reply other threads:[~2014-12-20 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 0:09 [PATCH 0/2] tty slave devices support - version 2 NeilBrown
2014-12-20 0:09 ` [PATCH 1/2] TTY: add support for "tty slave" devices NeilBrown
2014-12-21 10:20 ` Sebastian Reichel
2014-12-23 5:16 ` NeilBrown
2014-12-20 0:09 ` [PATCH 2/2] misc: add a driver to power on/off UART attached devices NeilBrown
2014-12-20 12:50 ` One Thousand Gnomes [this message]
2014-12-20 16:02 ` [Gta04-owner] " Christ van Willegen
2014-12-23 3:17 ` NeilBrown
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=20141220125020.49d0bba0@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gta04-owner@goldelico.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=neil@brown.name \
--cc=neilb@suse.de \
--cc=peter@hurleysoftware.com \
--cc=sre@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).