gpioirq(4) version 2

This update makes this driver more than just an example and allows for:

o More than one pin to be attached to a gpioirq instance. That is,
the mask parameter can be greater than 0x01 now.

o A /dev/gpioirqN device that allows GPIO pin interrupts to be
transported into userland. This is a device that can be opened for
reading with a simple fixed output indicating the device unit, pin
number and current pin state.


This update was used as part of a physical intrusion detection system
where multiple switches (i.e. window magnetic reed switches and etc.)
are tied to a bunch of GPIO inputs with userland software that reacts
to the pins changing state.

Overhaul of GPIO interrupt support (that wasn't even used by anything).
- Remove the old, not-expressive-enough interrupt flags, and replace them
with a new set of interrupt-specific flags that can express a wide
variety of interrupt configurations (pos, neg, and double-edge, high
and low level).
- Remove old, unused gpio_pin_ctl_intr() and gpio_pin_irqen(), and
replace them with gpio_intr_establish(), gpio_intr_disestablish(),
and gpio_intr_str(). Corresponding fields in the gpio_chipset_tag
are also added for back-end controllers, which now handle the actual
dispatch of GPIO interrupts in order to properly support level-triggered
interrupts as well as interoperate properly with FDT-registered
interrupts.

Piggy-back on the 8.99.18 version bump.

Inspired by initial work from Brad Spencer.
PR kern/51676

branches: 1.17.4;
Let the controller provide a default name for pins. This makes pins easier
to locate when we have multiple banks and a variable number of pins per
bank.

branches: 1.16.10;
As proposed in
http://mail-index.netbsd.org/tech-kern/2016/04/28/msg020504.html
add gpio interrupt support to the gpio framework, and an implementation
for the allwinner gpio backend (tested on A20 only).
gpio(4) has new public functions:
- gpio_intr() called by backends when an interrupt condition for
a gpio pin is present
- gpio_find_device() and gpio_get_name(), support functions for
gpio(4) users, wich respectively returns a void * cookie for a gpio device
given its name, and returns the name given the cookie.
- gpio_pin_ctl_intr(), which is used to configure interrupts on a gpio pin and
registers a callback.
- gpio_pin_irqen(), which is used to mask/unmask interrupts on a pin.

Nothing in the NetBSD tree uses this yet, but I have a i2c driver
(at https://github.com/mbouyer/marine_chartplotter/tree/master/software/NetBSD/driver) which uses it.

branches: 1.15.10; 1.15.18; 1.15.28;
Remove software pulsing in gpio(4), this functionality is now provided
by the gpiopwm(4) driver.

branches: 1.14.2;
Add a ga_flags field to the gpio_attach structure to hand driver
specific flags to drivers being attached at gpio pins. gpioiic(4)
uses this to reverse the SDA/SCL signal order. gpioctl(8) accepts
the flag values as optional argument to the attach command.
While here, make sure we retain backwards compatability and wrap compat
code in #ifdef COMPAT_50/#endif.

Remove what I committed accidentally...

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).

gpio(4) and gpiosim(4) can now be built and used as modules. While here,
make some functions static.

Before trying to attach a child device driver, make sure the GPIO pins can
be mapped. This prevents drivers from later failing in the attach routine.
Problem found by me, solution suggested by jmcneill.

Use device_t instead of struct device * per cegger's request.

Rework the GPIO framework. Tie it to the kauth(9) framework to control
access to the GPIO pins. Device drivers using GPIO pins can now be
attached and detached at runtime. GPIO pins can be named for easier
reference from userland programs. Introduce a new gpiosim(4) driver,
which is used for development.

Reviewed by many.

Both legs of a diagraph must return the same type.

branches: 1.6.2;
#include <sys/device.h> for device_t definition.

branches: 1.5.2;
gpio(4): Extend with open/close to request/release the ppbus(4) on open/close.
ppbus(4): Extend to attach on gpiobus.
From Hans Rosenfeld from tech-kern:
http://mail-index.netbsd.org/tech-kern/2008/04/28/msg001168.html
Hint: Hans sent me this diff which differs in the one from tech-kern in:
- 2-clause license
- sprinkled some consts

branches: 1.4.12; 1.4.66; 1.4.68; 1.4.70;
Flesh out the framework for attaching drivers to the GPIO pins.
From OpenBSD, Alexander Yurchenko <grange@openbsd

branches: 1.3.2; 1.3.4; 1.3.6;
merge ktrace-lwp.

branches: 1.2.6;
-kill gba_name in attach arg
-use constants from locators.h

Import general purpose I/O framework from OpenBSD.

Overhaul of GPIO interrupt support (that wasn't even used by anything).
- Remove the old, not-expressive-enough interrupt flags, and replace them
with a new set of interrupt-specific flags that can express a wide
variety of interrupt configurations (pos, neg, and double-edge, high
and low level).
- Remove old, unused gpio_pin_ctl_intr() and gpio_pin_irqen(), and
replace them with gpio_intr_establish(), gpio_intr_disestablish(),
and gpio_intr_str(). Corresponding fields in the gpio_chipset_tag
are also added for back-end controllers, which now handle the actual
dispatch of GPIO interrupts in order to properly support level-triggered
interrupts as well as interoperate properly with FDT-registered
interrupts.

Piggy-back on the 8.99.18 version bump.

Inspired by initial work from Brad Spencer.
PR kern/51676

branches: 1.17.4;
Let the controller provide a default name for pins. This makes pins easier
to locate when we have multiple banks and a variable number of pins per
bank.

branches: 1.16.10;
As proposed in
http://mail-index.netbsd.org/tech-kern/2016/04/28/msg020504.html
add gpio interrupt support to the gpio framework, and an implementation
for the allwinner gpio backend (tested on A20 only).
gpio(4) has new public functions:
- gpio_intr() called by backends when an interrupt condition for
a gpio pin is present
- gpio_find_device() and gpio_get_name(), support functions for
gpio(4) users, wich respectively returns a void * cookie for a gpio device
given its name, and returns the name given the cookie.
- gpio_pin_ctl_intr(), which is used to configure interrupts on a gpio pin and
registers a callback.
- gpio_pin_irqen(), which is used to mask/unmask interrupts on a pin.

Nothing in the NetBSD tree uses this yet, but I have a i2c driver
(at https://github.com/mbouyer/marine_chartplotter/tree/master/software/NetBSD/driver) which uses it.

branches: 1.15.10; 1.15.18; 1.15.28;
Remove software pulsing in gpio(4), this functionality is now provided
by the gpiopwm(4) driver.

branches: 1.14.2;
Add a ga_flags field to the gpio_attach structure to hand driver
specific flags to drivers being attached at gpio pins. gpioiic(4)
uses this to reverse the SDA/SCL signal order. gpioctl(8) accepts
the flag values as optional argument to the attach command.
While here, make sure we retain backwards compatability and wrap compat
code in #ifdef COMPAT_50/#endif.

Remove what I committed accidentally...

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).

gpio(4) and gpiosim(4) can now be built and used as modules. While here,
make some functions static.

Before trying to attach a child device driver, make sure the GPIO pins can
be mapped. This prevents drivers from later failing in the attach routine.
Problem found by me, solution suggested by jmcneill.

Use device_t instead of struct device * per cegger's request.

Rework the GPIO framework. Tie it to the kauth(9) framework to control
access to the GPIO pins. Device drivers using GPIO pins can now be
attached and detached at runtime. GPIO pins can be named for easier
reference from userland programs. Introduce a new gpiosim(4) driver,
which is used for development.

Reviewed by many.

Both legs of a diagraph must return the same type.

branches: 1.6.2;
#include <sys/device.h> for device_t definition.

branches: 1.5.2;
gpio(4): Extend with open/close to request/release the ppbus(4) on open/close.
ppbus(4): Extend to attach on gpiobus.
From Hans Rosenfeld from tech-kern:
http://mail-index.netbsd.org/tech-kern/2008/04/28/msg001168.html
Hint: Hans sent me this diff which differs in the one from tech-kern in:
- 2-clause license
- sprinkled some consts

branches: 1.4.12; 1.4.66; 1.4.68; 1.4.70;
Flesh out the framework for attaching drivers to the GPIO pins.
From OpenBSD, Alexander Yurchenko <grange@openbsd

branches: 1.3.2; 1.3.4; 1.3.6;
merge ktrace-lwp.

branches: 1.2.6;
-kill gba_name in attach arg
-use constants from locators.h

Import general purpose I/O framework from OpenBSD.

Let the controller provide a default name for pins. This makes pins easier
to locate when we have multiple banks and a variable number of pins per
bank.

As proposed in
http://mail-index.netbsd.org/tech-kern/2016/04/28/msg020504.html
add gpio interrupt support to the gpio framework, and an implementation
for the allwinner gpio backend (tested on A20 only).
gpio(4) has new public functions:
- gpio_intr() called by backends when an interrupt condition for
a gpio pin is present
- gpio_find_device() and gpio_get_name(), support functions for
gpio(4) users, wich respectively returns a void * cookie for a gpio device
given its name, and returns the name given the cookie.
- gpio_pin_ctl_intr(), which is used to configure interrupts on a gpio pin and
registers a callback.
- gpio_pin_irqen(), which is used to mask/unmask interrupts on a pin.

Nothing in the NetBSD tree uses this yet, but I have a i2c driver
(at https://github.com/mbouyer/marine_chartplotter/tree/master/software/NetBSD/driver) which uses it.

branches: 1.15.18; 1.15.28;
Remove software pulsing in gpio(4), this functionality is now provided
by the gpiopwm(4) driver.

branches: 1.14.2;
Add a ga_flags field to the gpio_attach structure to hand driver
specific flags to drivers being attached at gpio pins. gpioiic(4)
uses this to reverse the SDA/SCL signal order. gpioctl(8) accepts
the flag values as optional argument to the attach command.
While here, make sure we retain backwards compatability and wrap compat
code in #ifdef COMPAT_50/#endif.

Remove what I committed accidentally...

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).

gpio(4) and gpiosim(4) can now be built and used as modules. While here,
make some functions static.

Before trying to attach a child device driver, make sure the GPIO pins can
be mapped. This prevents drivers from later failing in the attach routine.
Problem found by me, solution suggested by jmcneill.

Use device_t instead of struct device * per cegger's request.

Rework the GPIO framework. Tie it to the kauth(9) framework to control
access to the GPIO pins. Device drivers using GPIO pins can now be
attached and detached at runtime. GPIO pins can be named for easier
reference from userland programs. Introduce a new gpiosim(4) driver,
which is used for development.

Reviewed by many.

Both legs of a diagraph must return the same type.

branches: 1.6.2;
#include <sys/device.h> for device_t definition.

branches: 1.5.2;
gpio(4): Extend with open/close to request/release the ppbus(4) on open/close.
ppbus(4): Extend to attach on gpiobus.
From Hans Rosenfeld from tech-kern:
http://mail-index.netbsd.org/tech-kern/2008/04/28/msg001168.html
Hint: Hans sent me this diff which differs in the one from tech-kern in:
- 2-clause license
- sprinkled some consts

branches: 1.4.12; 1.4.66; 1.4.68; 1.4.70;
Flesh out the framework for attaching drivers to the GPIO pins.
From OpenBSD, Alexander Yurchenko <grange@openbsd

branches: 1.3.2; 1.3.4; 1.3.6;
merge ktrace-lwp.

branches: 1.2.6;
-kill gba_name in attach arg
-use constants from locators.h

Import general purpose I/O framework from OpenBSD.

As proposed in
http://mail-index.netbsd.org/tech-kern/2016/04/28/msg020504.html
add gpio interrupt support to the gpio framework, and an implementation
for the allwinner gpio backend (tested on A20 only).
gpio(4) has new public functions:
- gpio_intr() called by backends when an interrupt condition for
a gpio pin is present
- gpio_find_device() and gpio_get_name(), support functions for
gpio(4) users, wich respectively returns a void * cookie for a gpio device
given its name, and returns the name given the cookie.
- gpio_pin_ctl_intr(), which is used to configure interrupts on a gpio pin and
registers a callback.
- gpio_pin_irqen(), which is used to mask/unmask interrupts on a pin.

Nothing in the NetBSD tree uses this yet, but I have a i2c driver
(at https://github.com/mbouyer/marine_chartplotter/tree/master/software/NetBSD/driver) which uses it.

branches: 1.15.18; 1.15.28;
Remove software pulsing in gpio(4), this functionality is now provided
by the gpiopwm(4) driver.

branches: 1.14.2;
Add a ga_flags field to the gpio_attach structure to hand driver
specific flags to drivers being attached at gpio pins. gpioiic(4)
uses this to reverse the SDA/SCL signal order. gpioctl(8) accepts
the flag values as optional argument to the attach command.
While here, make sure we retain backwards compatability and wrap compat
code in #ifdef COMPAT_50/#endif.

Remove what I committed accidentally...

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).

gpio(4) and gpiosim(4) can now be built and used as modules. While here,
make some functions static.

Before trying to attach a child device driver, make sure the GPIO pins can
be mapped. This prevents drivers from later failing in the attach routine.
Problem found by me, solution suggested by jmcneill.

Use device_t instead of struct device * per cegger's request.

Rework the GPIO framework. Tie it to the kauth(9) framework to control
access to the GPIO pins. Device drivers using GPIO pins can now be
attached and detached at runtime. GPIO pins can be named for easier
reference from userland programs. Introduce a new gpiosim(4) driver,
which is used for development.

Reviewed by many.

Both legs of a diagraph must return the same type.

branches: 1.6.2;
#include <sys/device.h> for device_t definition.

branches: 1.5.2;
gpio(4): Extend with open/close to request/release the ppbus(4) on open/close.
ppbus(4): Extend to attach on gpiobus.
From Hans Rosenfeld from tech-kern:
http://mail-index.netbsd.org/tech-kern/2008/04/28/msg001168.html
Hint: Hans sent me this diff which differs in the one from tech-kern in:
- 2-clause license
- sprinkled some consts

branches: 1.4.12; 1.4.66; 1.4.68; 1.4.70;
Flesh out the framework for attaching drivers to the GPIO pins.
From OpenBSD, Alexander Yurchenko <grange@openbsd

branches: 1.3.2; 1.3.4; 1.3.6;
merge ktrace-lwp.

branches: 1.2.6;
-kill gba_name in attach arg
-use constants from locators.h

Import general purpose I/O framework from OpenBSD.