cpu_soekris(4) [debian man page]

CPU_ELAN(4)						 BSD/i386 Kernel Interfaces Manual					       CPU_ELAN(4)

NAME

     CPU_ELAN -- AMD Elan 520 CPU support

SYNOPSIS

     options CPU_ELAN
     options CPU_ELAN_PPS
     options CPU_ELAN_XTAL
     machdep.elan_gpio_config
     machdep.elan_freq
     options CPU_SOEKRIS

DESCRIPTION

     The options CPU_ELAN enables support for the AMD Elan 520 CPU.

     A device /dev/elan-mmcr exports the MMCR register bank to userland using mmap(2).

     The i8254 timer will be adjusted to the slightly unorthodox frequency 1189161 Hz (32768 * 45 * 25 / 31) employed by the Elan.

     A timecounter named ``ELAN'' is implemented using the general purpose timer 2, but it will not be usable unless HZ is configured at 150 or
     higher.  This timecounter is much better than the ``i8254'' timecounter and should be used at all times.

     The machdep.elan_gpio_config sysctl(8) variable enables configuration of the GPIO pins of the CPU.  The string must be exactly 32 characters
     long.  A '-' means the GPIO is unavailable.  A 'l' (lower-case ell) configures a led(4) device (active low).  A 'L' configures a led(4)
     device (active high).  A '.' means no configuration for this GPIO.  These led(4) devices will be named /dev/led/gpio%d.  For meaning of 'P',
     'e' and 'E', see under options CPU_ELAN_PPS.

     The options CPU_ELAN_XTAL and the machdep.elan_freq sysctl(8) variable can be used to set the CPU clock crystal frequency in Hz.  The default
     is 33333333 Hz.

     The options CPU_ELAN_PPS enables precision timestamping using the RFC2783 PPS-API via the /dev/elan-mmcr device.  The resolution will be
     approximately 125 nsec and the precision +- 125 nsec.  (For 125 nsec read ``4 / CPU clock crystal frequency''.)

     The input signal must be connected to the TMR1IN pin and a GPIO pin.  The GPIO pin must be configured with a 'P' in machdep.elan_gpio_config.

     In addition, one GPIO pin can be configured with either 'e' (active low) or 'E' (active high) to become a ``echo'' output of the input sig-
     nal.  Please notice that this signal is not suitable for calibration.

     If the options CPU_SOEKRIS is given, the support will additionally be tailored to the Soekris Engineering 45xx series of embedded computers.
     The ``error'' led will be configured (as /dev/led/error) and the GPIO pins which are not available will be disabled.

SEE ALSO

     led(4), sysctl(8)

HISTORY

     The CPU_ELAN code first appeared in FreeBSD 4.7.

AUTHORS

     Poul-Henning Kamp <phk@FreeBSD.org>

BSD
								 November 23, 2003							       BSD

GPIOCTL(8)						    BSD System Manager's Manual 						GPIOCTL(8)

NAME

     gpioctl -- control GPIO devices

SYNOPSIS

     gpioctl [-q] device attach device offset mask [flag]
     gpioctl [-q] device pin [0 | 1 | 2]
     gpioctl [-q] device pin [on | off | toggle]
     gpioctl [-q] device pin set [flags] [name]
     gpioctl [-q] device pin unset

DESCRIPTION

     The gpioctl program allows manipulation of GPIO (General Purpose Input/Output) device pins.  Such devices can be either part of the chipset
     or embedded CPU, or a separate chip.  The usual way of using GPIO is to connect some simple devices such as LEDs and 1-wire thermal sensors
     to its pins.

     Each GPIO device has an associated device file in the /dev directory.  device can be specified with or without the /dev prefix.  For example,
     /dev/gpio0 or gpio0.

     GPIO pins can be either ``read'' or ``written'' with the values of logical 0 or 1.  If only a pin number is specified on the command line,
     the pin state will be read from the GPIO controller and displayed.  To write to a pin, a value must be specified after the pin number.  Val-
     ues can be either 0 or 1.	A value of 2 ``toggles'' the pin, i.e. changes its state to the opposite.  Instead of the numerical values, the
     word on, off, or toggle can be used.

     To

     Only pins that have been configured at securelevel 0, typically during system startup, are accessible once the securelevel has been raised.
     Pins can be given symbolic names for easier use.  Besides using individual pins, device drivers that use GPIO pins can be attached to a
     gpio(4) device using the gpioctl command.	Such drivers can be detached at runtime using the drvctl(8) command.

     The following configuration flags are supported by the GPIO framework:

	   in	   input direction
	   out	   output direction
	   inout   bi-directional
	   od	   open-drain output
	   pp	   push-pull output
	   tri	   tri-state (output disabled)
	   pu	   internal pull-up enabled
	   pd	   internal pull-down enabled
	   iin	   invert input
	   iout    invert output
	   pulsate
		   pulsate output at a hardware-defined frequency and duty cycle

     Note that not all the flags may be supported by the particular GPIO controller.

     When executed with only the gpio(4) device name as argument, gpioctl reads information about the GPIO device and displays it.  At securelevel
     0 the number of physically available pins is displayed, at higher securelevels the number of configured (set) pins is displayed.

     The options are as follows:

     -q      Operate quietly i.e. nothing is printed to stdout.

FILES

     /dev/gpiou  GPIO device unit u file.

EXAMPLES

     Configure pin 20 to have push-pull output:

	   # gpioctl gpio0 20 set out pp

     Write logical 1 to pin 20:

	   # gpioctl gpio0 20 1

     Attach a onewire(4) bus on a gpioow(4) device on pin 4:

	   # gpioctl gpio0 attach gpioow 4 0x01

     Detach the gpioow0 device:

	   # drvctl -d gpioow0

     Configure pin 5 as output and name it error_led:

	   # gpioctl gpio0 5 set out error_led

     Toggle the error_led:

	   # gpioctl gpio0 error_led 2

SEE ALSO

     gpio(4), drvctl(8)

HISTORY

     The gpioctl command first appeared in OpenBSD 3.6 and NetBSD 4.0.

AUTHORS

     The gpioctl program was written by Alexander Yurchenko <grange@openbsd.org>.  Device attachment was added by Marc Balmer <marc@msys.ch>.

BSD
								 November 13, 2011							       BSD