History log of /openbsd-src/sys/dev/gpio/gpio.c (Results 1 – 17 of 17)
Revision Date Author Comments
# 894c7bfe 11-Apr-2022 visa <visa@openbsd.org>

gpio: Add missing device_unref() calls

device_lookup() returns a reference that the caller has to release.

OK jca@


# 471aeecf 06-Apr-2022 naddy <naddy@openbsd.org>

constify struct cfattach


# 3adc742d 18-Aug-2017 jsg <jsg@openbsd.org>

Test for device_lookup() returning NULL in gpioioctl() and gpioclose().
Coverity CIDs 1453046, 1453184.


# fb9e5ef0 27-Aug-2015 deraadt <deraadt@openbsd.org>

simple sizes for free()


# aa3cabd0 12-Jul-2014 tedu <tedu@openbsd.org>

add a size argument to free. will be used soon, but for now default to 0.
after discussions with beck deraadt kettenis.


# 7d434456 03-Oct-2011 matthieu <matthieu@openbsd.org>

Add a 'flag' locator to gpioiic(4), and define a first flag
value to swap the SDA and SCL pins assigment during attach.
Mostly from work with mbalmer@NetBSD.
ok miod@


# 9585af64 29-Aug-2009 miod <miod@openbsd.org>

submatch functions used with config_found_sm() are required to invoke the
driver's ca_match function. (only offender in the whole tree)

ok deraadt@


# bf4b8d0a 26-Nov-2008 mbalmer <mbalmer@openbsd.org>

Add my copyright here, too.


# a388edca 26-Nov-2008 mbalmer <mbalmer@openbsd.org>

Change the semantics of gpio(4) devices by locking down pin
configuration and device attachment/detachment to securelevel 0.

GPIO pins can now only be configured at securelevel 0. Once the
securele

Change the semantics of gpio(4) devices by locking down pin
configuration and device attachment/detachment to securelevel 0.

GPIO pins can now only be configured at securelevel 0. Once the
securelevel is raised, only pins that have been configured and set
for securelevel access using the GPIOPINSET ioctl are accessible.
This also adds the possibility to give GPIO pins a name.

ok uwe@

show more ...


# fca40c6a 24-Nov-2008 mbalmer <mbalmer@openbsd.org>

- Add two new ioctls to gpio(4), GPIOATTACH and GPIODETACH, to allow to attach
and detach devices on a gpiobus at runtime. The offset and mask locators
in kernel config files can still be used for s

- Add two new ioctls to gpio(4), GPIOATTACH and GPIODETACH, to allow to attach
and detach devices on a gpiobus at runtime. The offset and mask locators
in kernel config files can still be used for static configuration, so this
does not break existing custome kernel configs.

- Have gpioow(4) unmap the pins it used from the gpiobus during detach

Changes to gpioctl(8) will be a separate committ.

ok uwe

show more ...


# 6ec0d2e1 26-Mar-2006 grange <grange@openbsd.org>

Don't allow to change gpio pin state if /dev/gpio was opened
in read-only mode. Spotted by form@.


# df8d0d17 14-Jan-2006 grange <grange@openbsd.org>

Add gpio_pin_caps() method to provide pin capabilities.


# aca51624 05-Jan-2006 grange <grange@openbsd.org>

Finish framework for attaching kernel drivers to the GPIO pins.
Not used yet.


# 30b09c33 23-Nov-2004 grange <grange@openbsd.org>

Let gpio_detach() do something useful.
Tested by reyk@ on gpio@ath.


# a92078b1 22-Nov-2004 reyk <reyk@openbsd.org>

added detach function to support hotpluggable gpios.
ok grange@


# 1f410c2f 15-Sep-2004 grange <grange@openbsd.org>

Tweak in comment.


# 3615eacb 03-Jun-2004 grange <grange@openbsd.org>

A framework for supporting various General Purpose Input/Output (GPIO)
devices. Such devices provide a set of pins that you can use to connect
for example leds to it.
The pins can be accessed either

A framework for supporting various General Purpose Input/Output (GPIO)
devices. Such devices provide a set of pins that you can use to connect
for example leds to it.
The pins can be accessed either from userland through the /dev/gpio*
device files or from the kernel drivers. The latter is necessary
for implementing timing-sensitive things like i2c or 1-wire master
controller.

ok deraadt@

show more ...