kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Adding GPIO/SPI/I2C functionality to FTDI driver
Date: Tue, 22 Sep 2015 12:02:03 -0700	[thread overview]
Message-ID: <20150922190203.GA31705@kroah.com> (raw)
In-Reply-To: <20150922162847.GC16144@hephaistos.amsuess.com>

On Tue, Sep 22, 2015 at 06:28:47PM +0200, chrysn wrote:
> Hello kernelnewbies list,
> 
> I've run into situations where it would be practical to have the GPIO,
> I2C and SPI functionality some FTDI chips provide as kernel devices.
> (The chips are more often used as USB serial adapters; only that feature
> is supported by the current kernel drivers).
> 
> The presence of an extensive userspace library (libftdi) and the
> observation of a project in a similar situation[1] that has not made it
> into the kernel makes me doubt that implementing that in the kernel is
> the way to go.
> 
> I've written up more thoughts on this on [2], including exploration of
> userspace SPI/GPIO/I2C devices (think FUSE / USBIP / uinput), but it
> boils down to a simple question:
> 
> 
> Is support for alternative operation modes in FTDI chips something that
> is welcome and (easily) feasible in the kernel?

This comes up every other month or so on the linux-usb mailing list.
See the discussions there about how to do this properly in a way that
will be accepted by the USB maintainers if you wish to do this work.

And yes, this would be very welcome, but no one seems to be willing to
do the work :(

thanks,

greg k-h

  reply	other threads:[~2015-09-22 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 16:28 Adding GPIO/SPI/I2C functionality to FTDI driver chrysn
2015-09-22 19:02 ` Greg KH [this message]
2015-09-23 15:40   ` chrysn
2015-09-24  0:19     ` Philipp Hachtmann
2015-09-26 18:20     ` Johan Hovold

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=20150922190203.GA31705@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).