From: Greg KH <gregkh@linuxfoundation.org>
To: Philipp Hachtmann <hachti@hachti.de>
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: Sat, 31 May 2014 19:31:06 -0700 [thread overview]
Message-ID: <20140601023106.GA4961@kroah.com> (raw)
In-Reply-To: <538A7063.8010205@hachti.de>
On Sun, Jun 01, 2014 at 02:14:27AM +0200, Philipp Hachtmann wrote:
> On 01.06.2014 02:00, Peter Stuge wrote:
> >Philipp Hachtmann wrote:
> >>This patch adds a sysfs attribute "cbus" which allows to set the
> >>four CBUS pins on the FT232H.
> >
> >I think this should be implemented with the gpio subsystem instead.
> The GPIO subsystem seems to be made for GPIO pins connected directly to the
> computer. The Beaglebone with its AM335x SoC seems to be a good example of
> a computer with many GPIOs in the sense of the GPIO subsystem.
> And the GPIO pins have fixed unique numbers. No, I don't think that the GPIO
> subsystem has anything to do with the additional pins on some USB device.
> Please correct me if I'm completely wrong.
As they are GPIO pins on this device, it should be the subsystem that
controls it. That way, userspace programs that are used to talk to a
GPIO device will "just work", and not have to be customized just for
this specific device and sysfs file.
So please use the GPIO subsystem instead of creating your own interface.
thanks,
greg k-h
next prev parent reply other threads:[~2014-06-01 2:31 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 [this message]
2014-06-02 0:57 ` Philipp Hachtmann
2014-06-02 1:38 ` Greg KH
2014-06-02 1:48 ` Philipp Hachtmann
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=20140601023106.GA4961@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hachti@hachti.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox