M-A

Ported from https://github.com/google/periph/issues/200. This is to fully utilize the Beaglebone hardware. This is a fairly complex endeavor. This requires 3 parts: - Compiler - Communication - Higher level abstraction

Ported from https://github.com/google/periph/issues/185. This one is risky, since it assumes a lot from the Go own scheduler.

am335x: implement memory mapped GPIO access

1

Ported from https://github.com/google/periph/issues/199. This is the CPU powering the Beaglebone Black and Green. It's a pretty nice board but it is starting to become outdated.

Ported from https://github.com/google/periph/issues/125. It's an inconvenience.

Ported from https://github.com/google/periph/issues/167. See documentation at https://www.kernel.org/doc/html/v4.12/driver-api/iio/core.html#iio-device-sysfs-interface.

Ported from https://github.com/google/periph/issues/227. But frankly, it should be done automatically.

Ported from https://github.com/google/periph/issues/271.

Ported from https://github.com/google/periph/issues/310.

Ported from https://github.com/google/periph/issues/358. Sadly libgpiod as listed in issue #39 doesn't expose PWM support, thus the older interface should be kept.

sysfs-gpio: use new /sys/bus/gpio/devices/gpiochipN, also listed as /dev/gpiochipN

4

Ported from https://github.com/google/periph/issues/371 It's the "new" GPIO API for linux kernels above 4.8, based on ioctl on a single handle instead of having to open multiple handles. There isn't a...