From: Philipp Hachtmann <hachti@hachti.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: jhovold@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] usb/ftdi_sio: Add support for setting CBUS pins on FT232H
Date: Mon, 02 Jun 2014 03:48:53 +0200 [thread overview]
Message-ID: <538BD805.5040306@hachti.de> (raw)
In-Reply-To: <20140602013839.GA831@kroah.com>
On 02.06.2014 03:38, Greg KH wrote:
>> Yes but... I should have avoided the term "GPIO".> No, you used the right
term :)
Sorry for using the right term :)
> No, I am not going to add custom ioctls to a single driver for this.
I did neither request nor expect that - did it sound that way?
> It would not be lost at all, you can see that relationship in sysfs
> between the gpio device and the tty device, they are both attached to
> the same "parent" usb interface.
Ok, I understand. This is a real argument for the GPIO stuff. I'm just beginning
to understand that using the GPIO stuff will make everyone happy.
> This comes up every 6 months or so, you aren't the first to ask for
> custom ioctls / sysfs files for this chip. But no one seems to want to
> to do the work to make it a proper gpio device, which is sad :(
Ok, ok. I will do it but it will take some time. I will resend my two patches then.
Kind regards
Philipp
next prev parent reply other threads:[~2014-06-02 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 23:31 [PATCH 0/2] Add synchronous FIFO and CBUS support for FT232H Philipp Hachtmann
2014-05-31 23:31 ` [PATCH 1/2] usb/ftdi_sio: Add synchronous FIFO mode " Philipp Hachtmann
2014-05-31 23:31 ` [PATCH 2/2] usb/ftdi_sio: Add support for setting CBUS pins on FT232H Philipp Hachtmann
2014-06-01 0:00 ` Peter Stuge
2014-06-01 0:14 ` Philipp Hachtmann
2014-06-01 2:31 ` Greg KH
2014-06-02 0:57 ` Philipp Hachtmann
2014-06-02 1:38 ` Greg KH
2014-06-02 1:48 ` Philipp Hachtmann [this message]
2014-06-01 0:04 ` Philipp Hachtmann
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=538BD805.5040306@hachti.de \
--to=hachti@hachti.de \
--cc=gregkh@linuxfoundation.org \
--cc=jhovold@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.