Rename gpiobus.c to gpiolib.c so we can move other parts in there too.
Requested by Jared.

Move (the one and only) gpiobus_* function(s) into a separate file
that is build if we have gpiobus (independent of having gpio or not).

branches: 1.16.40;
Add a 1PPS-over-GPIO driver, originally by Brad Spencer, with changes by
me to adapt to the new GPIO interrupt interface and support a wider variety
of GPIO pin configuations.

PR kern/51676

Add an example "gpioirq" driver that demonstrates interrupts on GPIO
pins. Will be enhanced in the future to support sending events to
user space on edge-triggered interrupt events.

Based on initial work by Brad Spencer.
PR kern/51676

branches: 1.14.16;
pull in sysmon_taskq

Use needs-count for # of pseudo instances; suggested by cube@.

Simple driver for GPIO power/sleep buttons.

Simple driver for gpio control of rf enable/disable pins.

branches: 1.10.10; 1.10.18; 1.10.28;
gpiopwm(4) is a driver to pulse GPIO pins in software. This obsoletes
the software pulsing facilities in gpio(4) (and gpioctl(8)) which will
later be removed.

branches: 1.9.2;
Add the flag locator (missed in the previous commit).

Add support for multi-position electro-mechanical keylocks. An example
driver, gpiolock(4), is provided as an example how to interface real hardware.
A new securemodel, securemodel_keylock, is provided to show how this can
be used to tie keylocks to overall system security. This is experimental
code. The diff has been on tech-kern for several weeks.

Reviewed by many, kauth(9) integration reviewed by Elad Efrat; approved by
tonnerre@ and tron@. Thanks to everyone who provided feedback.

gpioiic(4), a driver to do use GPIO pins in bit-banging mode to form an I2C
bus. Ported from OpenBSD.

Do not attach gpiosim(4) at root, but make it a pseudo device.
With help from Matthias Drochner, thanks!

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.

branches: 1.4.6; 1.4.64;
Dallas Semiconductor 1-Wire bus support, from OpenBSD. Currently includes
gpioow(4), attaching a bit-banging driver via a GPIO pin. Also,
owtemp(4) which supports some of the 1-Wire temperature sensors, including
the DS18b20 and DS1920 - temperatures are returned via the envsys(4)
framework.

Original drivers by Alexander Yurchenko (grange@openbsd), with envsys(4)
support and a fix to the 1-wire search algorithm (for discovering
devices on the bus) by me.

As discussed on tech-kern earlier this week.

branches: 1.3.2; 1.3.4; 1.3.6;
Flesh out the framework for attaching drivers to the GPIO pins.
From OpenBSD, Alexander Yurchenko <grange@openbsd

branches: 1.2.2; 1.2.4; 1.2.6;
merge ktrace-lwp.

branches: 1.1.6;
Import general purpose I/O framework from OpenBSD.

gpio: Use unsigned to avoid undefined behavior. Found by kUBSan

Move (the one and only) gpiobus_* function(s) into a separate file
that is build if we have gpiobus (independent of having gpio or not).

gpio(4): Add gpio_intr_{mask,unmask} functions.

For devices that use level triggered GPIO interrupts, provide an API
that allows them to mask/unmask interrupts on that pin.

branches: 1.73.6;


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.

branches: 1.72.2;
Never fib about pin count in GPIOINFO ioctl results. The number of pins
on a controller simply does not change depending on the privileges of
the caller.

I have been using this for a while and forgot to commit it. This add
a number of KERNEL_LOCK() calls and at the very least prevents gpioiic
from panicing the system. This may be a fix for kern/56438.

For device modules that provide both auto-config and /dev/xxx
interfaces, make sure that initialization and destruction
follow the proper sequence. This is triggered by the recent
changes to the devsw stuff; per riastradh@ the required call
sequence is:

devsw_attach()
config_init_component() or config_cf*_attach()
...
config_fini_component() or config_cf*_detach()
devsw_detach()

While here, add a few missing calls to some of the detach
routines.

Testing of these changes has been limited to:
1. compile without build break
2. no related test failures from atf
3. modload/modunload work as well as
before.

No functional device testing done, since I don't have any
of these devices. Let me know of any damage I might cause
here!

XXX Some of the modules affected by this commit are already
XXX broken; see kern/56772. This commit does not break
any additional modules (as far as I know).

When initializing pins, try to get the default pin name from the
"gpio-line-names" property. If not present, then fall back on the
default name for the pin from the parent, if there is one.

use l->l_cred since it is available.

fix various typos in compatibility, mainly in comments.

Merge thorpej-cfargs2.

branches: 1.65.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.64.10;
gpio: make GPIOREAD return also the symbolic name of the pin, if it is set

convert more KM_NOSLEEP to KM_SLEEP and remove code to handle failures.

Merge the [pgoyette-compat] branch

branches: 1.61.2;
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.60.2;
Kill some more extern struct cfdriver declarations.

Down with externs in .c!

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.58.8; 1.58.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.57.4;
Add d_discard to all struct cdevsw instances I could find.

All have been set to "nodiscard"; some should get a real implementation.

make implementation match gpio(4) man entry. do no change configuration
if no flags are being set (allows non-destructive inquiry via GPIOSET again).

Add aprint_naive("\n") for boot -q

branches: 1.54.2;
PR/48701: Timo Buhrmester: spurious messages while booting silently (gpio,
glxsb); use aprint_normal()
>Category: kern
>Synopsis: spurious messages while booting silently (gpio, glxsb)
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net

Change (mostly mechanically) every cdevsw/bdevsw I can find to use
designated initializers.

I have not built every extant kernel so I have probably broken at
least one build; however I've also found and fixed some wrong
cdevsw/bdevsw entries so even if so I think we come out ahead.

branches: 1.52.2;
When returning the old value, use the value read from the device.

branches: 1.51.6;
Quiet down autoconfiguration by changing some printf() calls to
aprint_normal() calls.

branches: 1.50.8;
Don't ignore the gpiobus_close() return value. Found by joerg@ using clang.

Initialize ga.ga_dvname in gpio_search to prevent a stack fault in config_match

Remove an unused variable.

Remove software pulsing in gpio(4), this functionality is now provided
by the gpiopwm(4) driver.

branches: 1.46.2;
Fix non-COMPAT_50 compilation.

Unbreak and move the list of child devices to COMPAT_50.

Remove the GPIODETACH gpio(4) ioctl (it is still available in COMPAT_50) and
the 'detach' command line option from gpioctl(8). Drivers that are
attached to gpio pins can be detached using the drvctl(8) command.

Don't cast void pointers.

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.

Make sure error is not used unitialized when sc->sc_attach_busy is 0.

Remove what I committed accidentally...

gpio(4) keeps track of child devices attached using the GPIOATTACH ioctl(),
so remove those references and free the memory in gpio_childdetached().
Protect access to the list of child devices with a kcondvar.

Unconditionally include <sys/modules.h>.

Register as built-in module when compiled wo/ _MODULE.

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.

Annotate that gpiobus_close's return value is undesired here

branches: 1.33.6;
console spam

branches: 1.32.2;
A pointer typedef entails trading too much flexibility to declare const
and non-const types, and the kernel uses both const and non-const
PMF qualifiers and device suspensors, so change the pmf_qual_t and
device_suspensor_t typedefs from "pointers to const" to non-pointer,
non-const types.

branches: 1.31.2;
Unfold, bump copyright.

Expand PMF_FN_* macros.

Delete the useless activation hook. Add a child-detached hook and
a rescan hook. Detach children before detaching self.

Prevent the creation of duplicate pin names in GPIOSET.
Problem noticed by rmind a while ago.

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.

unfold short lines, fold long line.

Fold long line.

Be more careful when attaching drivers at runtime, call the drivers match
routine before attaching the device. Prevents non-working driver instances
from being created.

Fold long line, add comment to fix possible creation of duplicates.

use device_xname

make this build w/ GPIO_DEBUG

Change one more struct device * to device_t, noticed by cegger.

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.

During shutdown, detach devices in an orderly fashion.

Call the detach routine for every device in the device tree, starting
with the leaves and moving toward the root, expecting that each
(pseudo-)device driver will use the opportunity to gracefully commit
outstandings transactions to the underlying (pseudo-)device and to
relinquish control of the hardware to the system BIOS.

Detaching devices is not suitable for every shutdown: in an emergency,
or if the system state is inconsistent, we should resort to a fast,
simple shutdown that uses only the pmf(9) shutdown hooks and the
(deprecated) shutdownhooks. For now, if the flag RB_NOSYNC is set in
boothowto, opt for the fast, simple shutdown.

Add a device flag, DVF_DETACH_SHUTDOWN, that indicates by its presence
that it is safe to detach a device during shutdown. Introduce macros
CFATTACH_DECL3() and CFATTACH_DECL3_NEW() for creating autoconf
attachments with default device flags. Add DVF_DETACH_SHUTDOWN
to configuration attachments for atabus(4), atw(4) at cardbus(4),
cardbus(4), cardslot(4), com(4) at isa(4), elanpar(4), elanpex(4),
elansc(4), gpio(4), npx(4) at isa(4), nsphyter(4), pci(4), pcib(4),
pcmcia(4), ppb(4), sip(4), wd(4), and wdc(4) at isa(4).

Add a device-detachment "reason" flag, DETACH_SHUTDOWN, that tells the
autoconf code and a device driver that the reason for detachment is
system shutdown.

Add a sysctl, kern.detachall, that tells the system to try to detach
every device at shutdown, regardless of any device's DVF_DETACH_SHUTDOWN
flag. The default for kern.detachall is 0. SET IT TO 1, PLEASE, TO
HELP TEST AND DEBUG DEVICE DETACHMENT AT SHUTDOWN.

This is a work in progress. In future work, I aim to treat
pseudo-devices more thoroughly, and to gracefully tear down a stack of
(pseudo-)disk drivers and filesystems, including cgd(4), vnd(4), and
raid(4) instances at shutdown.

Also commit some changes that are not easily untangled from the rest:

(1) begin to simplify device_t locking: rename struct pmf_private to
device_lock, and incorporate device_lock into struct device.

(2) #include <sys/device.h> in sys/pmf.h in order to get some
definitions that it needs. Stop unnecessarily #including <sys/device.h>
in sys/arch/x86/include/pic.h to keep the amd64, xen, and i386 releases
building.

branches: 1.17.8; 1.17.14;
device_t / softc split. From Hans Rosenfeld.

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.15.2; 1.15.4;
Use PMF_FN_ARGS, PMF_FN_PROTO.

branches: 1.14.2; 1.14.6;
Use device_t.

Bug fix: record the new state (high/low) set by gpio_pin_write().
I don't know why we gpio(4) didn't do that before, but it seems
harmless.

Add naive power handling: when a gpio(4) instance is resumed, write
each pin's configuration flags and output state from the softc to
the hardware using gpiobus_pin_ctl() and gpiobus_pin_write().
While suspended, fail every ioctl() except for GPIOINFO with EBUSY.

branches: 1.12.16; 1.12.22; 1.12.24; 1.12.28;
Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

branches: 1.11.4;
__unused removal on arguments; approved by core.

- sprinkle __unused on function decls.
- fix a couple of unused bugs
- no more -Wno-unused for i386

branches: 1.9.2; 1.9.4;
add missing initializers

branches: 1.8.6;
Whitespace nit.

Use device_private().

Use device_unit().

branches: 1.5.2; 1.5.4; 1.5.6;
Flesh out the framework for attaching drivers to the GPIO pins.
From OpenBSD, Alexander Yurchenko <grange@openbsd

branches: 1.4.2; 1.4.4; 1.4.6;
merge ktrace-lwp.

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

Add __KERNEL_RCSID.

Import general purpose I/O framework from OpenBSD.

Rename gpiobus.c to gpiolib.c so we can move other parts in there too.
Requested by Jared.

Move (the one and only) gpiobus_* function(s) into a separate file
that is build if we have gpiobus (independent of having gpio or not).

branches: 1.3.16;
Use sysmon_taskq instead of our own workqueue for submitting button events.

branches: 1.2.2;
remove debug printf

Simple driver for GPIO power/sleep buttons.

Encapsulate what's needed to attach an I2C bus into a iicbus_attach()
inline.

gpioiic(4): Use config_detach_children.

Merge thorpej-cfargs2.

branches: 1.10.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.9.10;
Cleanup i2c bus acquire / release, centralizing all of the logic into
iic_acquire_bus() / iic_release_bus(). "acquire" and "release" hooks
no longer need to be provided by back-end controller drivers (only if
they need special handling, e.g. powering on the i2c controller).
This results in the removal of a bunch of rendundant code from each
back-end controller driver.

Assert that we are not in hard interrupt context in iic_acquire_bus(),
iic_exec(), and iic_release_bus().

branches: 1.8.4;
Kill some more extern struct cfdriver declarations.

Down with externs in .c!

i2c_acquire_bus() should return 0 on success.
Fixed bug in gpioiic_bb_set_bits(), which was introduced with the SDA/SCL-
reverse feature.
Now the driver is confirmed to work. Tested with Raspberry Pi GPIO.

branches: 1.6.12; 1.6.14;
split device_t/softc for all remaining drivers.
replace "struct device *" with "device_t".
use device_xname(), device_unit(), etc.

branches: 1.5.2; 1.5.12;
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.

Switch von u_int_XY to uintXY

When reading the bits from the I2C bus, also report SCL. Fixes PR43275.
Fix originally from Maxim Weber, thanks.

Delete unnecessary device-activation hooks. Simplify the rest.

branches: 1.1.2;
gpioiic(4), a driver to do use GPIO pins in bit-banging mode to form an I2C
bus. Ported from OpenBSD.

fix various typos in comments and log messages.

For /dev/ reads against gpioirq(4) implement the following:

o O_NONBLOCK on reads

o Add a d_poll function and associated sel[init|notify|record|destroy]
calls to the driver so that select(2) and poll(2) work as expected.


With these in place async use cases work against /dev/gpioirqN

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.

branches: 1.1.2; 1.1.36;
Add an example "gpioirq" driver that demonstrates interrupts on GPIO
pins. Will be enhanced in the future to support sending events to
user space on edge-triggered interrupt events.

Based on initial work by Brad Spencer.
PR kern/51676

branches: 1.1.4;
Rename gpiobus.c to gpiolib.c so we can move other parts in there too.
Requested by Jared.

Kill some more extern struct cfdriver declarations.

Down with externs in .c!

Check pmf_device_register return value. NFC
Appeases static analyzers.

branches: 1.3.22; 1.3.40; 1.3.44; 1.3.48;
Delete unnecessary device-activation hooks. Simplify the rest.

branches: 1.2.2;
Move the keylock.h header from sys/sys to sys/dev where it really belongs.
Add keylock options to the ALL kernel configuration.

Add support for multi-position electro-mechanical keylocks. An example
driver, gpiolock(4), is provided as an example how to interface real hardware.
A new securemodel, securemodel_keylock, is provided to show how this can
be used to tie keylocks to overall system security. This is experimental
code. The diff has been on tech-kern for several weeks.

Reviewed by many, kauth(9) integration reviewed by Elad Efrat; approved by
tonnerre@ and tron@. Thanks to everyone who provided feedback.

gpioow(4): Use config_detach_children.

Merge thorpej-cfargs2.

branches: 1.18.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.17.10;
localify

onewire:

- Re-do the signalling to be a little more forgiving and efficient.
- If bus reset fails during probe, try a second time.
- Spread out kernel threads for many busses to avoid thundering herd effect.

branches: 1.15.4;
Kill some more extern struct cfdriver declarations.

Down with externs in .c!

branches: 1.14.12;
Newline is \n, not /n.

Add glue code to build as module.

Simplify activation hook.

Register with the PMF, and when detaching, just the right order.

Don't use an identifier name that probably clashes with the C standard.
Requested by many.

unfold short line; debracket

A better match routine that checks also the number of pins instead
of checking the pins in the attach routine; malconfigured devices will
no longer attach. While here, replace some printf uses by aprint_....

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.

bzero -> memset

branches: 1.5.8; 1.5.14;
Finish device_t/softc split. Previous commit was incomplete.

device_t / softc split. From Hans Rosenfeld.

branches: 1.3.48; 1.3.50; 1.3.52;
__unused removal on arguments; approved by core.

- sprinkle __unused on function decls.
- fix a couple of unused bugs
- no more -Wno-unused for i386

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.10; 1.1.14; 1.1.18; 1.1.20; 1.1.22;
Dallas Semiconductor 1-Wire bus support, from OpenBSD. Currently includes
gpioow(4), attaching a bit-banging driver via a GPIO pin. Also,
owtemp(4) which supports some of the 1-Wire temperature sensors, including
the DS18b20 and DS1920 - temperatures are returned via the envsys(4)
framework.

Original drivers by Alexander Yurchenko (grange@openbsd), with envsys(4)
support and a fix to the 1-wire search algorithm (for discovering
devices on the bus) by me.

As discussed on tech-kern earlier this week.

Fix typo in comment.

For device modules that provide both auto-config and /dev/xxx
interfaces, make sure that initialization and destruction
follow the proper sequence. This is triggered by the recent
changes to the devsw stuff; per riastradh@ the required call
sequence is:

devsw_attach()
config_init_component() or config_cf*_attach()
...
config_fini_component() or config_cf*_detach()
devsw_detach()

While here, add a few missing calls to some of the detach
routines.

Testing of these changes has been limited to:
1. compile without build break
2. no related test failures from atf
3. modload/modunload work as well as
before.

No functional device testing done, since I don't have any
of these devices. Let me know of any damage I might cause
here!

XXX Some of the modules affected by this commit are already
XXX broken; see kern/56772. This commit does not break
any additional modules (as far as I know).

gpiopps module requires the gpio module to resolve several symbols

Fix a paste-o that prevented the 2-pin interrupt messages from being
printed correctly (but no other harmful effects). Pointed out by
Brad Spencer.

branches: 1.1.2;
Add a 1PPS-over-GPIO driver, originally by Brad Spencer, with changes by
me to adapt to the new GPIO interrupt interface and support a wider variety
of GPIO pin configuations.

PR kern/51676

Kill some more extern struct cfdriver declarations.

Down with externs in .c!

Check pmf_device_register return value. NFC
Appeases static analyzers.

branches: 1.5.2; 1.5.4;
- Use aprint*() instead of printf() in xxx_attach().
- Add missing aprint_naive("\n");
- KNF

branches: 1.4.6;
Ensure that the top level sysctl nodes (kern, vfs, net, ...) exist before
the sysctl link sets are processed, and remove redundancy.

Shaves >13kB off of an amd64 GENERIC, not to mention >1k duplicate
lines of code.

branches: 1.3.2; 1.3.4;
Add some pre-processor magic to verify that the type of the data item
passed to sysctl_createv() actually matches the declared type for
the item itself.
In the places where the caller specifies a function and a structure
address (typically the 'softc') an explicit (void *) cast is now needed.
Fixes bugs in sys/dev/acpi/asus_acpi.c sys/dev/bluetooth/bcsp.c
sys/kern/vfs_bio.c sys/miscfs/syncfs/sync_subr.c and setting
AcpiGbl_EnableAmlDebugObject.
(mostly passing the address of a uint64_t when typed as CTLTYPE_INT).
I've test built quite a few kernels, but there may be some unfixed MD
fallout. Most likely passing &char[] to char *.
Also add CTLFLAG_UNSIGNED for unsiged decimals - not set yet.

branches: 1.2.8;
On detach, set the pin to low state.

gpiopwm(4) is a driver to pulse GPIO pins in software. This obsoletes
the software pulsing facilities in gpio(4) (and gpioctl(8)) which will
later be removed.

branches: 1.1.2; 1.1.18;
Simple driver for gpio control of rf enable/disable pins.

Style changes. No functional change.

Simple simulated interrupts for the simulated GPIO device gpiosim(4)

gpiosim(4): Use config_detach_children.

branches: 1.23.6;
Merge thorpej-cfargs2.

branches: 1.22.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.21.20;
Kill some more extern struct cfdriver declarations.

Down with externs in .c!

branches: 1.20.4;
Check pmf_device_register return value. NFC
Appeases static analyzers.

branches: 1.19.2; 1.19.4;
- Use aprint*() instead of printf() in xxx_attach().
- Add missing aprint_naive("\n");
- KNF

include "ioconf.h" to get the 'void <driver>attach(int count);' prototype.

Use needs-count for # of pseudo instances; suggested by cube@.

branches: 1.16.6;
Ensure that the top level sysctl nodes (kern, vfs, net, ...) exist before
the sysctl link sets are processed, and remove redundancy.

Shaves >13kB off of an amd64 GENERIC, not to mention >1k duplicate
lines of code.

branches: 1.15.2;
Make the gpiosim(4) device a 64 bit wide GPIO.

branches: 1.14.2;
Add some pre-processor magic to verify that the type of the data item
passed to sysctl_createv() actually matches the declared type for
the item itself.
In the places where the caller specifies a function and a structure
address (typically the 'softc') an explicit (void *) cast is now needed.
Fixes bugs in sys/dev/acpi/asus_acpi.c sys/dev/bluetooth/bcsp.c
sys/kern/vfs_bio.c sys/miscfs/syncfs/sync_subr.c and setting
AcpiGbl_EnableAmlDebugObject.
(mostly passing the address of a uint64_t when typed as CTLTYPE_INT).
I've test built quite a few kernels, but there may be some unfixed MD
fallout. Most likely passing &char[] to char *.
Also add CTLFLAG_UNSIGNED for unsiged decimals - not set yet.

branches: 1.13.2;
Unconditionally include <sys/modules.h>.

Register as built-in module when compiled wo/ _MODULE.

build with WARNS=3

u_int32_t -> uin32_t.

fix indents

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

Delete unnecessary device-activation hooks. Simplify the rest.

branches: 1.6.2;
Properly teardown the sysctl node and detach child driver if gpiosim gets
detached itself (e.g. when the 'drvctl -d gpiosimX' command is entered).

For the sake of correctness, call pmf_device_deregister() in the detach
function.

add dummy pmf registration to allow suspend

Do not attach gpiosim(4) at root, but make it a pseudo device.
With help from Matthias Drochner, thanks!

Simplify the use _a lot_ by hooking this to sysctl instead of bio(4).
When it attaches, it creates a hw.gpiosimN.value sysctl node which can
then be used to manipulate the simulated device state.

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.

gpio(4): Add gpio_intr_{mask,unmask} functions.

For devices that use level triggered GPIO interrupts, provide an API
that allows them to mask/unmask interrupts on that pin.

branches: 1.19.6;


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.

branches: 1.18.34;
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.