Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-08-23 Thread Grant Likely
On Sun, 21 Jun 2015 21:44:30 +0200 , Stefan Agner wrote: > On 2015-06-21 01:49, Peter Stuge wrote: > > Stefan Agner wrote: > >> libftdi requires to detach the kernel driver to get access to the device > > > > Control transfers ought to be possible without a detach. > > Good to know, thanks for

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-24 Thread Johan Hovold
On Wed, Jun 24, 2015 at 12:08:50AM +0200, Stefan Agner wrote: > On 2015-06-23 11:22, Johan Hovold wrote: > > On Mon, Jun 22, 2015 at 10:11:35PM +0200, Stefan Agner wrote: > >> On 2015-06-22 19:26, Johan Hovold wrote: > > > >> > Instead, hang the gpio chip directly off the usb interface (not the >

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-23 Thread Stefan Agner
On 2015-06-23 11:22, Johan Hovold wrote: > On Mon, Jun 22, 2015 at 10:11:35PM +0200, Stefan Agner wrote: >> On 2015-06-22 19:26, Johan Hovold wrote: > >> > Instead, hang the gpio chip directly off the usb interface (not the >> > port), add a new config option, and keep the gpio implementation unde

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-23 Thread Johan Hovold
On Mon, Jun 22, 2015 at 10:11:35PM +0200, Stefan Agner wrote: > On 2015-06-22 19:26, Johan Hovold wrote: > > Instead, hang the gpio chip directly off the usb interface (not the > > port), add a new config option, and keep the gpio implementation under > > drivers/usb/serial (possibly in its own fi

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-22 Thread Stefan Agner
On 2015-06-22 19:26, Johan Hovold wrote: > On Sun, Jun 21, 2015 at 12:12:55AM +0200, Stefan Agner wrote: >> Bit Bang mode, the pins need to be reprogrammed to I/O mode first >> (EEPROM). All three modes are supported from userspace by libftdi afaik. > > Is there a way to retrieve the settings fro

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-22 Thread Johan Hovold
On Sun, Jun 21, 2015 at 12:12:55AM +0200, Stefan Agner wrote: > Yet another FTDI GPIO patchset. Yet somewhat different to previous > implementations... > > There are three GPIO modes supported by FTDI devices: > 1. Asynchronous Bit Bang Mode (used in Sacha's patch) > 2. Synchronous Bit Bang Mode (

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-21 Thread Stefan Agner
On 2015-06-21 01:49, Peter Stuge wrote: > Stefan Agner wrote: >> libftdi requires to detach the kernel driver to get access to the device > > Control transfers ought to be possible without a detach. Good to know, thanks for this input. The detach is probably a default behavior of libftdi... Will

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-21 Thread Stefan Agner
Hi Philipp, On 2015-06-21 04:22, Philipp Hachtmann wrote: > Am 21.06.2015 um 00:12 schrieb Stefan Agner: >> There are three GPIO modes supported by FTDI devices: >> 1. Asynchronous Bit Bang Mode (used in Sacha's patch) >> 2. Synchronous Bit Bang Mode (used in Philipp's patch) >> 3. CBUS Bit Bang M

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-20 Thread Philipp Hachtmann
Am 21.06.2015 um 00:12 schrieb Stefan Agner: There are three GPIO modes supported by FTDI devices: 1. Asynchronous Bit Bang Mode (used in Sacha's patch) 2. Synchronous Bit Bang Mode (used in Philipp's patch) 3. CBUS Bit Bang Mode (used in Philipp's patch and this patchset) 1. No idea, could be

Re: [PATCH 0/2] FTDI CBUS GPIO support

2015-06-20 Thread Peter Stuge
Stefan Agner wrote: > libftdi requires to detach the kernel driver to get access to the device Control transfers ought to be possible without a detach. //Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in

[PATCH 0/2] FTDI CBUS GPIO support

2015-06-20 Thread Stefan Agner
Yet another FTDI GPIO patchset. Yet somewhat different to previous implementations... There are three GPIO modes supported by FTDI devices: 1. Asynchronous Bit Bang Mode (used in Sacha's patch) 2. Synchronous Bit Bang Mode (used in Philipp's patch) 3. CBUS Bit Bang Mode (used in Philipp's patch an