History log of /netbsd/usr.sbin/gpioctl/gpioctl.c (Results 1 – 25 of 28)
Revision Date Author Comments
# fa616ef4 13-Dec-2022 jakllsch <jakllsch@NetBSD.org>

If we can't read a pin while listing pins, simply continue on to next
pin rather than abort.


# d564a57e 20-Oct-2019 tnn <tnn@NetBSD.org>

gpioctl: implement support for "gpioctl gpioN list". Like pcictl(8).

For drivers that name their pins, this can be used to determine how the
logical pins are mapped to physical pins. Example from su

gpioctl: implement support for "gpioctl gpioN list". Like pcictl(8).

For drivers that name their pins, this can be used to determine how the
logical pins are mapped to physical pins. Example from sunxigpio(4):

# gpioctl gpio0 list
0: PA0
1: PA1
2: PA2
...

show more ...


# cc17ee2e 27-Jan-2019 pgoyette <pgoyette@NetBSD.org>

Merge the [pgoyette-compat] branch


# 73e87e7a 19-Oct-2018 christos <christos@NetBSD.org>

add __RCSID


# 6b591661 19-May-2018 thorpej <thorpej@NetBSD.org>

Overhaul of GPIO interrupt support (that wasn't even used by anything).
- Remove the old, not-expressive-enough interrupt flags, and replace them
with a new set of interrupt-specific flags that can

Overhaul of GPIO interrupt support (that wasn't even used by anything).
- Remove the old, not-expressive-enough interrupt flags, and replace them
with a new set of interrupt-specific flags that can express a wide
variety of interrupt configurations (pos, neg, and double-edge, high
and low level).
- Remove old, unused gpio_pin_ctl_intr() and gpio_pin_irqen(), and
replace them with gpio_intr_establish(), gpio_intr_disestablish(),
and gpio_intr_str(). Corresponding fields in the gpio_chipset_tag
are also added for back-end controllers, which now handle the actual
dispatch of GPIO interrupts in order to properly support level-triggered
interrupts as well as interoperate properly with FDT-registered
interrupts.

Piggy-back on the 8.99.18 version bump.

Inspired by initial work from Brad Spencer.
PR kern/51676

show more ...


# 999b6622 05-Apr-2016 bouyer <bouyer@NetBSD.org>

Fix pasto for GPIO_PIN_EVENTS/GPIO_PIN_LEVEL/GPIO_PIN_FALLING
(not used at this time)


# e27bab72 06-Dec-2015 mlelstv <mlelstv@NetBSD.org>

pass new pin configuration flags to driver.


# b8415de4 29-Jan-2015 christos <christos@NetBSD.org>

use strtonum from libc (Kamil Rytarowski)


# 1bdc60c3 19-May-2013 mbalmer <mbalmer@NetBSD.org>

Make it easier to use gpioctl(8) in shell scripts: Add a -s flag which
instructs gpioctl(8) to only output a single numeric value, either the
number of pins if no pin number was passed as argumenti,

Make it easier to use gpioctl(8) in shell scripts: Add a -s flag which
instructs gpioctl(8) to only output a single numeric value, either the
number of pins if no pin number was passed as argumenti, or, the current
state of the pin.

show more ...


# e680da6b 13-Nov-2011 mbalmer <mbalmer@NetBSD.org>

Remove software pulsing in gpio(4), this functionality is now provided
by the gpiopwm(4) driver.


# 029bcf8d 12-Nov-2011 mbalmer <mbalmer@NetBSD.org>

Second part of typo fixing cycle...


# 2dd1115f 12-Nov-2011 mbalmer <mbalmer@NetBSD.org>

Fix typo.


# dc2d28b2 03-Oct-2011 mbalmer <mbalmer@NetBSD.org>

Remove the GPIODETACH gpio(4) ioctl (it is still available in COMPAT_50) and
the 'detach' command line option from gpioctl(8). Drivers that are
attached to gpio pins can be detached using the drvctl

Remove the GPIODETACH gpio(4) ioctl (it is still available in COMPAT_50) and
the 'detach' command line option from gpioctl(8). Drivers that are
attached to gpio pins can be detached using the drvctl(8) command.

show more ...


# 3b72c2b3 02-Oct-2011 mbalmer <mbalmer@NetBSD.org>

It's actually 'the flag locator', not 'flags' (as 'flags' can not be used
as a locator name for reasons unknown to me.)


# be149ed8 02-Oct-2011 mbalmer <mbalmer@NetBSD.org>

Add a ga_flags field to the gpio_attach structure to hand driver
specific flags to drivers being attached at gpio pins. gpioiic(4)
uses this to reverse the SDA/SCL signal order. gpioctl(8) accepts

Add a ga_flags field to the gpio_attach structure to hand driver
specific flags to drivers being attached at gpio pins. gpioiic(4)
uses this to reverse the SDA/SCL signal order. gpioctl(8) accepts
the flag values as optional argument to the attach command.
While here, make sure we retain backwards compatability and wrap compat
code in #ifdef COMPAT_50/#endif.

show more ...


# ffeab64f 15-Sep-2011 mbalmer <mbalmer@NetBSD.org>

Bump (c) year.


# c45de77d 30-Aug-2011 joerg <joerg@NetBSD.org>

static + __dead


# da668cdf 28-Aug-2011 mbalmer <mbalmer@NetBSD.org>

Add a new ioctl, GPIOPULSE to gpio(4) to allow for pulsing a pin.
If a pin can pulse in hardware, that will be used, else it will
be pulsed in software. There is no way yet to set the pulse frequenc

Add a new ioctl, GPIOPULSE to gpio(4) to allow for pulsing a pin.
If a pin can pulse in hardware, that will be used, else it will
be pulsed in software. There is no way yet to set the pulse frequency
for pins that pulse in hardware. While here, make the code mpsafe and
allow more than one thread in the driver (access to ioctl is serialized).

show more ...


# 6f8ac9a6 12-Aug-2011 mbalmer <mbalmer@NetBSD.org>

use my NetBSD email address


# 57ef84d0 12-Aug-2011 mbalmer <mbalmer@NetBSD.org>

Make some functions static, use getprogname() instead of
'extern char *__progname'.


# 98c90767 25-Sep-2009 mbalmer <mbalmer@NetBSD.org>

Rename 'pulse' to 'pulsate' to make clear it is a continuous strain of
pulses and and not a single shot pulse that is emitted by devices
supporting this kind of operation.


# e5d5fe6e 25-Sep-2009 mbalmer <mbalmer@NetBSD.org>

Jonatha Kollasch has a GPIO device that can pulse the output lines.
Support it wuth the GPIO_PIN_PULSE attribute and the 'pulse' paramater
to gpioctl. Discussed with Jonathan.


# 32eeaba5 25-Jul-2009 mbalmer <mbalmer@NetBSD.org>

Reworked gpioctl(8) command to reflect recent gpio(4) changes.


# 00e40eb3 09-Jan-2008 xtraeme <xtraeme@NetBSD.org>

Staticify fully now.


# 9b5c4f42 09-Jan-2008 xtraeme <xtraeme@NetBSD.org>

KNF: bzero -> memset, use EXIT_{FAILURE,SUCCESS}, setprogname() and
getprogname(), etc.


12