| 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
| ||
|
Date: Mon, 02 Jun 2014 03:48:53 +0200 From: Philipp Hachtmann <hachti@...hti.de> To: Greg KH <gregkh@...uxfoundation.org> CC: jhovold@...il.com, linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] usb/ftdi_sio: Add support for setting CBUS pins on FT232H 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 -- 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/
Powered by blists - more mailing lists