[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150320193119.GA28194@amd>
Date: Fri, 20 Mar 2015 20:31:19 +0100
From: Pavel Machek <pavel@....cz>
To: NeilBrown <neil@...wn.name>
Cc: Mark Rutland <mark.rutland@....com>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Peter Hurley <peter@...leysoftware.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Sebastian Reichel <sre@...nel.org>,
Grant Likely <grant.likely@...aro.org>,
Jiri Slaby <jslaby@...e.cz>,
GTA04 owners <gta04-owner@...delico.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] tty slave device support - version 3.
Hi!
> here is version 3 of support for tty-slaves.
>
> This version introduces a new bus-type for tty-slaves, and causes
> a tty-slave device to appear in /sys/devices between the uart and the
> tty.
> It effectively intercepts and calls from the tty to the uart (i.e. any
> tty_operations) and applies extra functionality at that point.
>
> Currently the only driver intercepts open and close.
> It powers on the device on open, and powers off at last-close.
>
> Power can be controlled by a regulator or by toggling a GPIO.
>
> I think I've incorporated most of the feed back I received from
> previous versions, but if I missed something - I apologize. If
> this approach is structurally acceptable then I can fix up all the
> smaller issues.
Do you have dts example? Anyway, we'll need something similar for
bluetooth on N900. But we'd like the /dev/ttyXX not to be visible to
the userspace in that case.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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