Ok this is my suggestion based on GregKH comments and a couple of others
plus some other driver and ldisc stuff that is pending
- register the gpio lines with the gpio layer dynamically
- put them in the right place in the device tree (I'll let Greg advise on
the best way to do that bit), plus make them visible via the ioctls for
convenience and as they will be needed anyway in kernel
That provides the user space API
After that I'll add the hooks to the core tty layer code which allow an
ldisc to adjust the gpio lines.
For that we'll need
struct tty_gpio {
u32 base;
u16 num;
u16 reserved;
#define NR_TTY_GPIOMAP 8
u16 map[NR_TTY_GPIOMAP];
u32 reserved2[4];
};
and
tty->gpiomap
which will be NULL for most users.
Plus
struct tty_gpio d;
ioctl(tty, TIOCGPIO, &d)
and
ioctl(tty, TIOCSGPIO, &d)
where the only bits that can be updated will be the map.
So the normal use case from user space would be
struct tty_gpio d;
int fd = open("/dev/ttyUSB0", O_RDWR);
ioctl(tty, TIOCSGPIO, &d);
stuff using the gpio driver interfaces
close(fd);
And setting up for a kernel ldisc something like
/* Set a GPIO to LDISC signal mapping for ISO7816 */
ioctl(tty, TIOCGPIO, &d);
d.map[TTY_GPIO_ISO7816_RESET] = d.base;
d.map]TTY_GPIO_ISO7816_VCC] = d.base + 1;
ioctl(tty, TIOCSGPIO, &d);
/* Switch to the ldisc */
ld = N_ISO7816;
ioctl(tty, TCSETD, &ld);
and we can then abstract all the wiring details away to keep the ldisc
portable.
Thoughts ?
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
