From: "Stevens, Nick" <Nick.Stevens-i7dp0qKlBMg@public.gmane.org>
To: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: i2c bus driver for FTDI MPSSE
Date: Thu, 14 May 2015 19:44:29 +0000 [thread overview]
Message-ID: <20150514194351.GA10672@nick.stevens-ubuntu> (raw)
Recently I've been working on I2C device drivers for a number of devices
on an embedded platform (specifically the Microchip line of A2Ds), and
I'm planning to submit patches with my changes. However, my development
is on an older system running Linux 3.10, and I'd really like to test my
drivers with a more recent kernel. Getting a PC running a recent kernel
release is straightforward, but I've found that there aren't a lot of
great options for pluggable I2C busses on the PC (the USB Tiny is about
the only one).
That leads to my question - FTDI makes a number of USB interface chips
with their Multi-Protocol Synchronous Serial Engine (MPSSE) component,
which supports I2C. Kernel support for using the MPSSE as an I2C bus
seems like it would provide a really convenient way to test I2C drivers
on a PC, especially since the FTDI chips are easily available in
multiple form factors from multiple vendors. Has anyone explored this?
Are there obvious obstacles that I'm not thinking of? Would this be
useful to anyone else?
Thanks!
Nick--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2015-05-14 19:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150514194351.GA10672@nick.stevens-ubuntu \
--to=nick.stevens-i7dp0qklbmg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).