Hi,
> > Maybe this is a better solution, especially considering aversion to do
> > this by the module parameters.
> >
> > Or maybe it is better to give support for I2C, SPI to ftdi_sio module and
> > use sysfs to switch betwen uart/ic2c/spi ...
>
> If can do this on interface basis per-device it looks better.
I try add support for I2C to ftdi_sio with sysfs config interface,
probably in this week.
> > > However back to the SPI/I2C
> > > thingy. You ignore one uart port and decide to use it as SPI host
> > > right? So you should get a reference somehow to this port so you can
> > > register a SPI host to the system right? How do you do this?
> >
> > I plan do this with other kernel module, matching to the same device, but
> > serving other interface. I haven't complete module yet, but in first
> > tests this concept works ok.
>
> How generic is this? I mean is this SPI mode something the chip supports or
> is this just SPI over UART since you enough wires?
This is feature of ft2232 and ft4232 chips ("Multi-Protocol Synchronous
Serial Engine Interface"). More info in data sheet and
http://www.ftdichip.com/Support/SoftwareExamples/MPSSE.htm
> Sebastian
Regards,
Robert
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
