linux-kernel - Re: [PATCH] usb/serial/cp2101: Add support for cp2103 GPIO pins

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 Nov 2008 10:58:23 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Keith Packard <keithp@...thp.com>
Cc:	linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>,
	Keith Packard <keithp@...thp.com>
Subject: Re: [PATCH] usb/serial/cp2101: Add support for cp2103 GPIO pins

On Thu, 27 Nov 2008 00:29:36 -0800
Keith Packard <keithp@...thp.com> wrote:

> The cp2103 is programmed the same as the cp2101/cp2102 except for the
> addition of a set of four GPIO pins which can be directly controlled by the
> host. Access to this is done through a custom ioctl.

Only concern I have is that a custom ioctl means every time a new serial
chip grows GPIO pins we end up with more ioctls.

We have an LED class driver which might perhaps do the job but isn't
really oriented that way but would keep the tty and gpio pins separate
and available to different applications at the same time.

Failing that a rename to make it a generic tty gpio ioctl might be more
futurerpoof ?

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/