From: Stefan Agner <stefan@agner.ch>
To: Stefan Agner <stefan@agner.ch>,
johan@kernel.org, linus.walleij@linaro.org, gnurou@gmail.com,
grant.likely@secretlab.ca, gregkh@linuxfoundation.org,
x-linux@infra-silbe.de, hachti@hachti.de,
linux-usb@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] FTDI CBUS GPIO support
Date: Sun, 21 Jun 2015 21:44:30 +0200 [thread overview]
Message-ID: <a35f48994dedc061b54ca9ea255fdd4e@agner.ch> (raw)
In-Reply-To: <20150620234957.25729.qmail@stuge.se>
On 2015-06-21 01:49, Peter Stuge wrote:
> Stefan Agner wrote:
>> libftdi requires to detach the kernel driver to get access to the device
>
> Control transfers ought to be possible without a detach.
Good to know, thanks for this input. The detach is probably a default
behavior of libftdi... Will have a look at that.
Having kernel level gpiolib would still have advantages: It would make
the matching of the GPIO's and tty device easier, since with this patch
the gpiolib device is a sub-node of the usb-serial device in sysfs and
the user would have to use kernel interfaces only (no libftdi)...
--
Stefan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-06-21 19:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 22:12 [PATCH 0/2] FTDI CBUS GPIO support Stefan Agner
2015-06-20 22:12 ` [PATCH 1/2] USB: ftdi_sio: add CBUS mode for FT232R devices Stefan Agner
2015-06-30 6:46 ` Linus Walleij
2015-06-30 6:54 ` Johan Hovold
2015-06-20 22:12 ` [PATCH 2/2] gpio: gpio-ftdi-cbus: add driver for FTDI CBUS GPIOs Stefan Agner
2015-07-15 7:42 ` Linus Walleij
2015-06-20 23:49 ` [PATCH 0/2] FTDI CBUS GPIO support Peter Stuge
2015-06-21 19:44 ` Stefan Agner [this message]
2015-08-23 8:52 ` Grant Likely
2015-06-21 2:22 ` Philipp Hachtmann
2015-06-21 19:39 ` Stefan Agner
2015-06-22 17:26 ` Johan Hovold
2015-06-22 20:11 ` Stefan Agner
2015-06-23 9:22 ` Johan Hovold
2015-06-23 22:08 ` Stefan Agner
2015-06-24 7:56 ` 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=a35f48994dedc061b54ca9ea255fdd4e@agner.ch \
--to=stefan@agner.ch \
--cc=gnurou@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=hachti@hachti.de \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=x-linux@infra-silbe.de \
/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