From: Greg KH <gregkh@linuxfoundation.org>
To: Preston Fick <pffick@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, preston.fick@silabs.com
Subject: Re: [PATCH 3/3] usb: cp210x: Add ioctl for GPIO support
Date: Wed, 2 May 2012 13:03:56 -0700 [thread overview]
Message-ID: <20120502200356.GA25915@kroah.com> (raw)
In-Reply-To: <1335845210-5147-3-git-send-email-preston.fick@silabs.com>
On Mon, Apr 30, 2012 at 11:06:50PM -0500, Preston Fick wrote:
> This patch adds support for GPIO for CP210x devices that support it through two
> IOCTLs to get or set the GPIO latch on a CP210x device. The specification for
> this can be found in Silicon Labs AN571 document on section 5.27.1-4.
>
> Signed-off-by: Preston Fick <preston.fick@silabs.com>
> ---
> drivers/usb/serial/cp210x.c | 98 +++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 98 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
> index b3646b8..9d1e542 100644
> --- a/drivers/usb/serial/cp210x.c
> +++ b/drivers/usb/serial/cp210x.c
> @@ -35,6 +35,8 @@
> */
> static int cp210x_open(struct tty_struct *tty, struct usb_serial_port *);
> static void cp210x_close(struct usb_serial_port *);
> +static int cp210x_ioctl(struct tty_struct *tty,
> + unsigned int cmd, unsigned long arg);
> static void cp210x_get_termios(struct tty_struct *,
> struct usb_serial_port *port);
> static void cp210x_get_termios_port(struct usb_serial_port *port,
> @@ -175,6 +177,7 @@ static struct usb_serial_driver cp210x_device = {
> .bulk_out_size = 256,
> .open = cp210x_open,
> .close = cp210x_close,
> + .ioctl = cp210x_ioctl,
> .break_ctl = cp210x_break_ctl,
> .set_termios = cp210x_set_termios,
> .tiocmget = cp210x_tiocmget,
> @@ -195,6 +198,10 @@ static struct usb_serial_driver * const serial_drivers[] = {
> #define CP2104_PARTNUM 0x04
> #define CP2105_PARTNUM 0x05
>
> +/* IOCTLs */
> +#define IOCTL_GPIOGET 0x8000
> +#define IOCTL_GPIOSET 0x8001
As Alan pointed out, we can't just add random ioctls for individual
drivers for this type of thing. We need to standardize on this.
Actually, why can't you use the GPIO subsystem for something like this?
Can't you export your device as both a usb-serial device and a gpio
device and have things work properly that way?
thanks,
greg k-h
next prev parent reply other threads:[~2012-05-02 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 4:06 [PATCH 1/3] usb: cp210x: Corrected USB request type definitions Preston Fick
2012-05-01 4:06 ` [PATCH 2/3] usb: cp210x: Added in support to get and store part number Preston Fick
2012-05-01 16:16 ` Sergei Shtylyov
[not found] ` <4FA00C49.7000105-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
2012-05-02 20:04 ` Greg KH
2012-05-01 4:06 ` [PATCH 3/3] usb: cp210x: Add ioctl for GPIO support Preston Fick
2012-05-02 20:03 ` Greg KH [this message]
2012-05-02 20:49 ` Alan Cox
2012-05-02 21:52 ` Greg KH
2012-05-02 22:10 ` Alan Cox
2012-05-02 22:27 ` Greg KH
2012-05-02 22:59 ` Alan Cox
2012-05-03 8:58 ` [PATCH 1/3] usb: cp210x: Corrected USB request type definitions Bjørn Mork
2012-05-08 13:56 ` Preston Fick
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=20120502200356.GA25915@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pffick@gmail.com \
--cc=preston.fick@silabs.com \
/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).