History log of /openbsd-src/sys/dev/gpio/files.gpio (Results 1 – 11 of 11)
Revision Date Author Comments
# 854a1b2d 24-Jan-2020 jsg <jsg@openbsd.org>

cleanup unused headers generated by config

ok tedu@ krw@ deraadt@


# 947eb244 07-Jun-2015 claudio <claudio@openbsd.org>

The Swiss Federal Government decided to shut down HBG at the end of 2011.
On 6 September 2012 at 12:02:00 UTC both antenna towers were demolished by
controlled explosives. So this is not coming back

The Swiss Federal Government decided to shut down HBG at the end of 2011.
On 6 September 2012 at 12:02:00 UTC both antenna towers were demolished by
controlled explosives. So this is not coming back and we can tedu the
support for HBG form the DCF77 drivers.
Remided by mbalmer

show more ...


# 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@


# c9851b67 28-Nov-2008 mbalmer <mbalmer@openbsd.org>

Welcome gpiodcf(4), a driver that attaches to a GPIO pin, decodes the
signal from an attached DCF77, HG, or TDF receiver and provides a timedelta.


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


# f8c248a6 04-Mar-2006 grange <grange@openbsd.org>

Dallas 1-Wire bus support. Includes the following drivers:

gpioow(4) 1-Wire bus bit-banging through GPIO pin
onewire(4) 1-Wire bus driver
owid(4) 1-Wire ID family type device
owtemp(4) 1-Wire tempe

Dallas 1-Wire bus support. Includes the following drivers:

gpioow(4) 1-Wire bus bit-banging through GPIO pin
onewire(4) 1-Wire bus driver
owid(4) 1-Wire ID family type device
owtemp(4) 1-Wire temperature family type device

Drivers for RS-232 and USB bus masters will follow.

ok deraadt@

show more ...


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

Add a comment.


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

Support for I2C bus bit-banging through the GPIO pins.
Now Soekris people can enjoy our fancy I2C stuff, too:

nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS
gpio1 at nsclpcsio0: 29

Support for I2C bus bit-banging through the GPIO pins.
Now Soekris people can enjoy our fancy I2C stuff, too:

nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS
gpio1 at nsclpcsio0: 29 pins
gpioiic0 at gpio1 pins 17 19
iic0 at gpioiic0
maxds0 at iic0 addr 0x48: ds1624, starting
maxds1 at iic0 addr 0x49: ds1624, starting

show more ...


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

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


# 66ed6627 08-Mar-2005 tdeval <tdeval@openbsd.org>

Cosmetics...
Mainly remove space between locators parens, replace spaces with tabs
where appropriate and consistently align dependencies.


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