From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] usb: cp210x: Added support for GPIO (CP2103/4/5)
Date: Sat, 28 Apr 2012 20:33:22 +0100 [thread overview]
Message-ID: <20120428203322.7680594f@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <20380.13347.472373.965813@elektron.ikp.physik.tu-darmstadt.de>
On Sat, 28 Apr 2012 20:17:07 +0200
Uwe Bonnes <bon@elektron.ikp.physik.tu-darmstadt.de> wrote:
> >>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>
> ...
> Alan> The other question is whether having some custom gpio poking
> Alan> interface is actually a good idea. I suspect probably not. The
> Alan> kernel gpio layer can help a bit but doesn't really solve the
> Alan> problem as there is no way to tie a gpio to a port. Given how many
> Alan> devices seem to have gpios these days I wonder if we need a gpio
> Alan> setting interface via termiox.
>
> Is this really kernel stuff or better handled in libusb(x)
Tricky to do it that way when the kernel driver owns the interface. Also
it's looking increasingly like we'll need to support a variety of "serial
and a couple of extra magic lines" type interfaces for things like SIM
readers.
Alan
next prev parent reply other threads:[~2012-04-28 19:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 16:55 [PATCH] usb: cp210x: Added support for GPIO (CP2103/4/5) Preston Fick
2012-04-28 18:05 ` Alan Cox
2012-04-28 18:17 ` Uwe Bonnes
2012-04-28 19:33 ` Alan Cox [this message]
2012-04-29 13:02 ` Uwe Bonnes
2012-04-29 14:35 ` Xiaofan Chen
2012-04-28 20:30 ` Preston Fick
2012-04-28 21:08 ` Alan Cox
2012-04-28 21:44 ` Preston Fick
2012-04-30 20:27 Preston Fick
2012-04-30 20:32 ` Greg KH
2012-05-03 20:34 ` Alan Cox
2012-05-04 15:27 ` Preston Fick
2012-05-05 0:32 ` Greg KH
2012-05-05 11:01 ` Alan Cox
2012-05-05 14:57 ` Greg KH
2012-05-16 15:33 ` Alan Cox
2012-05-16 23:41 ` Greg KH
2012-05-04 16:26 ` Alexander Stein
2012-05-04 16:33 ` Alan Cox
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=20120428203322.7680594f@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bon@elektron.ikp.physik.tu-darmstadt.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.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).