From: chrysn@fsfe.org (chrysn)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Adding GPIO/SPI/I2C functionality to FTDI driver
Date: Wed, 23 Sep 2015 17:40:58 +0200 [thread overview]
Message-ID: <20150923154058.GB24018@hephaistos.amsuess.com> (raw)
In-Reply-To: <20150922190203.GA31705@kroah.com>
Hallo Stefan, hallo Philipp,
hello Johan and Greg,
On Tue, Sep 22, 2015 at 12:02:03PM -0700, Greg KH wrote:
> On Tue, Sep 22, 2015 at 06:28:47PM +0200, chrysn wrote:
> > 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.
I've overlooked your two recent approaches when looking for existing
approaches towards extending FTDI support in the kernel (probably due to
me being too focused at SPI).
Stefan and Philipp, has any of your patch sets received updates in the
meantime that have not been sent to the mailing list?
It seems that one issue that needs to be solved for either of those to
continue is the decision of whether to base the FTDI driver on the MFD
infrastructure (which would probably be a first step then before even
implementing any of SPI, GPIO or I2C interfaces). There have been
conflicting opinions on this in different threads ([1], [2]); my
impression is that it would be a good idea, given that many of the more
recent FTDI devices can be switched to half a dozen configurations, and
that they are also shipped in products[3] where several of them would be
used in a coordinated fashion similar to the shields of widespread
embedded systems.
Johan and Greg, can you reconcile your opinions on that? Or whom is that
question best discussed with? devicetree? linux-usb? linux-gpio / -spi
/ -i2c?
Best regards
chrysn
PS. I've updated the summary I'm keeping of what led to this thread on
[4] -- all directly relevant information / questions should be in the
mails, but the page should provide further background for the curious.
[1] https://lkml.org/lkml/2014/6/1/250
[2] https://lkml.org/lkml/2015/6/22/451
[3] http://www.mikroe.com/click/usb-adapter/
[4] http://christian.amsuess.com/idea-incubator/ftdi-kernel-support/
--
I shouldn't have written all those tank programs.
-- Kevin Flynn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150923/a46e66ab/attachment-0001.bin
next prev parent reply other threads:[~2015-09-23 15:40 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
2015-09-23 15:40 ` chrysn [this message]
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=20150923154058.GB24018@hephaistos.amsuess.com \
--to=chrysn@fsfe.org \
--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).