From: Song Qiang <songqiang1304521@gmail.com>
To: johan@kernel.org, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: usb: thoughts of adding more support for FT232H
Date: Wed, 5 Dec 2018 22:10:40 +0800 [thread overview]
Message-ID: <48bc71bb-68e4-8b29-f609-940c9aedc0a9@gmail.com> (raw)
Hi Johan,
I've been developing some iio device drivers and found that some people
would like to test their devices with a qemu system which requires an
i2c or spi port on our development hosts. Usually this is achieved with
a DLN-2 adapter, while this is a bit difficult for me because it costs
~175$ in my country. Then I found that FTDI's FT232H supports both these
two modes and costs only less than 5$ but without full support in kernel.
The ftdi-sio driver supports FT232H only as a serial converter.
So I'm planning to write a mfd driver for it supports both these three
modes, here are my thoughts:
- This device cannot support these three modes together because they
share some common pins, so I'm planning to add a sysfs entry
'current_mode' for selecting which mode the device should be working
on.
- This device is in uart mode on reset, so default mode would be reset,
too. This also helps for people only want to use this as a serial
converter feels nothing has happened (compatible).
- I was trying to reuse the ftdi-sio driver but it seems like mfd can
only register platform devices, while this is a usb driver. I may
have to copy some functions from this driver.
Would you share any ideas? I'd appreciate it.
yours,
Song Qiang
next reply other threads:[~2018-12-05 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 14:10 Song Qiang [this message]
2018-12-05 15:17 ` Anatolij Gustschin
2018-12-05 15:39 ` Johan Hovold
2018-12-06 6:02 ` Song Qiang
2018-12-13 13:23 ` Johan Hovold
2018-12-16 15:45 ` Song Qiang
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=48bc71bb-68e4-8b29-f609-940c9aedc0a9@gmail.com \
--to=songqiang1304521@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®