| 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
| ||
|
Message-ID: <20120428203322.7680594f@pyramind.ukuu.org.uk> Date: Sat, 28 Apr 2012 20:33:22 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Uwe Bonnes <bon@...ktron.ikp.physik.tu-darmstadt.de> Cc: linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org Subject: Re: [PATCH] usb: cp210x: Added support for GPIO (CP2103/4/5) On Sat, 28 Apr 2012 20:17:07 +0200 Uwe Bonnes <bon@...ktron.ikp.physik.tu-darmstadt.de> wrote: > >>>>> "Alan" == Alan Cox <alan@...rguk.ukuu.org.uk> writes: > > ... > Alan> The other question is whether having some custom gpio poking > Alan> interface is actually a good idea. I suspect probably not. The > Alan> kernel gpio layer can help a bit but doesn't really solve the > Alan> problem as there is no way to tie a gpio to a port. Given how many > Alan> devices seem to have gpios these days I wonder if we need a gpio > Alan> setting interface via termiox. > > Is this really kernel stuff or better handled in libusb(x) Tricky to do it that way when the kernel driver owns the interface. Also it's looking increasingly like we'll need to support a variety of "serial and a couple of extra magic lines" type interfaces for things like SIM readers. 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/
Powered by blists - more mailing lists