linux-kernel - Re: [PATCH] USB: ftdi

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]

Message-ID: <539E99AB.9030907@hachti.de>
Date:	Mon, 16 Jun 2014 09:15:55 +0200
From:	Philipp Hachtmann <hachti@...hti.de>
To:	Johan Hovold <johan@...nel.org>,
	Sascha Silbe <x-linux@...ra-silbe.de>
CC:	Johan Hovold <jhovold@...il.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Alexandre Courbot <gnurou@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: ftdi_sio: add GPIO support

Hi,

> Would this patch interfere with adding support for using the CBUS pins
> as GPIOs while operating in normal UART mode?

Most interesting question!

>> Care was taken to prevent using GPIOs if the serial device is in use
>> and vice versa.

What about CBUS GPIO support?

> Ok, so we're not extending the serial driver with support for
> controlling some unused pins (e.g. CBUS) but rather implementing support
> for a mutually exclusive mode.
For bitbang mode (on the data lines) - yes. But for bitbang on CBUS - no.


I have sent a proposal a few weeks ago but Greg did not like special 
sysfs stuff :-P
He asked me to use the GPIO subsystem for the CBUS pins. I am out of 
time until july. But I still want and need CBUS support in parallel with 
serial/FIFO operation.


Regards

Philipp
--
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/