| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Coverity CIDs 1453046, 1453184.
|
| |
|
|
|
|
| |
after discussions with beck deraadt kettenis.
|
|
|
|
|
|
| |
value to swap the SDA and SCL pins assigment during attach.
Mostly from work with mbalmer@NetBSD.
ok miod@
|
|
|
|
|
|
| |
driver's ca_match function. (only offender in the whole tree)
ok deraadt@
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
in read-only mode. Spotted by form@.
|
| |
|
|
|
|
| |
Not used yet.
|
|
|
|
| |
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@
|