public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Greg KH <gregkh@suse.de>
Cc: keithp@keithp.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb/serial/cp2101: Add support for cp2103 GPIO pins
Date: Wed, 03 Dec 2008 00:11:11 -0800	[thread overview]
Message-ID: <1228291871.6187.23.camel@aiko.keithp.com> (raw)
In-Reply-To: <20081203071225.GC12582@suse.de>

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

On Tue, 2008-12-02 at 23:12 -0800, Greg KH wrote:

> Ick.  Ok, care to come up with some kind of hook into the gpio subsystem
> of the kernel so we don't create a new user/kernel interface for
> something that we already support?

Yeah, it does seem like exposing GPIOs to user space would be really
useful. Coming up with credible semantics seems a bit tricky though, and
may not fit the read/write model that we know and love.

> libusb can be very fast.  The new version handles multiple urbs in
> flight, and threaded applications very easily.  You might want to take a
> look at it again if it has been a while.

Sigh. Yes, I can probably use libusb for this application. Not as easily
as I can hack up the kernel, but it should do the trick.

-- 
keith.packard@intel.com

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-12-03  9:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27  8:29 [PATCH] usb/serial: Add compat_ioctl pass-through Keith Packard
2008-11-27  8:29 ` [PATCH] usb/serial/cp2101: Add support for cp2103 GPIO pins Keith Packard
2008-11-27 10:58   ` Alan Cox
2008-11-27 18:20     ` Keith Packard
2008-11-27 18:41       ` Greg KH
2008-11-28  1:31         ` Keith Packard
2008-12-03  7:12           ` Greg KH
2008-12-03  8:11             ` Keith Packard [this message]
2008-11-27 14:31 ` [PATCH] usb/serial: Add compat_ioctl pass-through Arnd Bergmann
2008-11-27 18:27   ` Keith Packard
2008-11-28 11:43     ` Arnd Bergmann
2008-11-28 14:03       ` Alan Cox
2008-11-28 15:42         ` Arnd Bergmann
2008-11-28 22:28           ` Keith Packard
2008-11-28 22:33             ` Alan Cox
2008-11-29  1:02               ` Keith Packard
2008-11-29  1:10                 ` Alan Cox
2008-11-29  1:23                   ` Arjan van de Ven
2008-11-29  1:37                     ` 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=1228291871.6187.23.camel@aiko.keithp.com \
    --to=keithp@keithp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@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