| Age | Commit message (Collapse) | Author |
|---|
|
ok grange@
|
|
something, then it MUST return zero on DVACT_ACTIVATE, not EOPNOTSUPP;
this very popular bug has been cut and pasted a lot of times...
ok deraadt@ mickey@
|
|
in read-only mode. Spotted by form@.
|
|
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@
|
|
|
|
|
|
|
|
|
|
|
|
- use gpio_pin_caps() while configuring pins
- try to deal not only with open-drain outputs
|
|
|
|
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
|
|
Not used yet.
|
|
Mainly remove space between locators parens, replace spaces with tabs
where appropriate and consistently align dependencies.
|
|
Tested by reyk@ on gpio@ath.
|
|
ok grange@
|
|
|
|
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@
|
