Searched hist:da668cdf (Results 1 – 6 of 6) sorted by relevance
| /netbsd/sys/sys/ |
| H A D | gpio.h | da668cdf Sun Aug 28 07:48:50 GMT 2011 mbalmer <mbalmer@NetBSD.org> Add a new ioctl, GPIOPULSE to gpio(4) to allow for pulsing a pin.
If a pin can pulse in hardware, that will be used, else it will
be pulsed in software. There is no way yet to set the pulse frequency
for pins that pulse in hardware. While here, make the code mpsafe and
allow more than one thread in the driver (access to ioctl is serialized).
|
| /netbsd/usr.sbin/gpioctl/ |
| H A D | gpioctl.8 | da668cdf Sun Aug 28 07:48:50 GMT 2011 mbalmer <mbalmer@NetBSD.org> Add a new ioctl, GPIOPULSE to gpio(4) to allow for pulsing a pin.
If a pin can pulse in hardware, that will be used, else it will
be pulsed in software. There is no way yet to set the pulse frequency
for pins that pulse in hardware. While here, make the code mpsafe and
allow more than one thread in the driver (access to ioctl is serialized).
|
| H A D | gpioctl.c | da668cdf Sun Aug 28 07:48:50 GMT 2011 mbalmer <mbalmer@NetBSD.org> Add a new ioctl, GPIOPULSE to gpio(4) to allow for pulsing a pin.
If a pin can pulse in hardware, that will be used, else it will
be pulsed in software. There is no way yet to set the pulse frequency
for pins that pulse in hardware. While here, make the code mpsafe and
allow more than one thread in the driver (access to ioctl is serialized).
|
| /netbsd/sys/dev/gpio/ |
| H A D | gpiovar.h | da668cdf Sun Aug 28 07:48:50 GMT 2011 mbalmer <mbalmer@NetBSD.org> Add a new ioctl, GPIOPULSE to gpio(4) to allow for pulsing a pin.
If a pin can pulse in hardware, that will be used, else it will
be pulsed in software. There is no way yet to set the pulse frequency
for pins that pulse in hardware. While here, make the code mpsafe and
allow more than one thread in the driver (access to ioctl is serialized).
|
| H A D | gpio.c | da668cdf Sun Aug 28 07:48:50 GMT 2011 mbalmer <mbalmer@NetBSD.org> Add a new ioctl, GPIOPULSE to gpio(4) to allow for pulsing a pin.
If a pin can pulse in hardware, that will be used, else it will
be pulsed in software. There is no way yet to set the pulse frequency
for pins that pulse in hardware. While here, make the code mpsafe and
allow more than one thread in the driver (access to ioctl is serialized).
|
| /netbsd/share/man/man4/ |
| H A D | gpio.4 | da668cdf Sun Aug 28 07:48:50 GMT 2011 mbalmer <mbalmer@NetBSD.org> Add a new ioctl, GPIOPULSE to gpio(4) to allow for pulsing a pin.
If a pin can pulse in hardware, that will be used, else it will
be pulsed in software. There is no way yet to set the pulse frequency
for pins that pulse in hardware. While here, make the code mpsafe and
allow more than one thread in the driver (access to ioctl is serialized).
|