资料介绍
Table of Contents
ADIS16240 IIO Programmable Impact Sensor and Recorder Linux Driver
Supported Devices
Evaluation Boards
Description
This is a Linux industrial I/O (IIO) subsystem driver, targeting serial interface Accelerometer. The industrial I/O subsystem provides a unified framework for drivers for many different types of converters and sensors using a number of different physical interfaces (i2c, spi, etc). See IIO for more information.
Source Code
Status
Files
Function | File |
---|---|
driver | drivers/staging/iio/accel/adis16240_core.c |
driver | drivers/staging/iio/accel/adis16240_ring.c |
driver | drivers/staging/iio/accel/adis16240_trigger.c |
include | drivers/staging/iio/accel/adis16240.h |
Declaring SPI slave devices
Unlike PCI or USB devices, SPI devices are not enumerated at the hardware level. Instead, the software must know which devices are connected on each SPI bus segment, and what slave selects these devices are using. For this reason, the kernel code must instantiate SPI devices explicitly. The most common method is to declare the SPI devices by bus number.
This method is appropriate when the SPI bus is a system bus, as in many embedded systems, wherein each SPI bus has a number which is known in advance. It is thus possible to pre-declare the SPI devices that inhabit this bus. This is done with an array of struct spi_board_info, which is registered by calling spi_register_board_info().
For more information see: Documentation/spi/spi-summary
Depending on the converter IC used, you may need to set the modalias accordingly, matching your part name. It may also required to adjust max_speed_hz. Please consult the datasheet, for maximum spi clock supported by the device in question.
static struct spi_board_info board_spi_board_info[] __initdata = { #if defined(CONFIG_ADIS16240) / || defined(CONFIG_ADIS16240_MODULE) { .modalias = "adis16240", .max_speed_hz = 1500000, /* max spi clock (SCK) speed in HZ */ .bus_num = 0, .chip_select = 5, /* CS, change it for your board */ .platform_data = NULL, /* No spi_driver specific config */ .mode = SPI_MODE_3, .irq = IRQ_PF4, }, #endif };
static int __init board_init(void) { [--snip--] spi_register_board_info(board_spi_board_info, ARRAY_SIZE(board_spi_board_info)); [--snip--] return 0; } arch_initcall(board_init);
Adding Linux driver support
Configure kernel with “make menuconfig” (alternatively use “make xconfig” or “make qconfig”)
The ADIS16240 Driver depends on CONFIG_SPI
Linux Kernel Configuration Device Drivers ---> [*] Staging drivers ---> <*> Industrial I/O support ---> --- Industrial I/O support -*- Enable ring buffer support within IIO -*- Industrial I/O lock free software ring -*- Enable triggered sampling support *** Accelerometers *** [--snip--] <*> Analog Devices ADIS16240 Programmable Impact Sensor and Recorder [--snip--]
Hardware configuration
Driver testing
Each and every IIO device, typically a hardware chip, has a device folder under /sys/bus/iio/devices/iio:deviceX. Where X is the IIO index of the device. Under every of these directory folders reside a set of files, depending on the characteristics and features of the hardware device in question. These files are consistently generalized and documented in the IIO ABI documentation. In order to determine which IIO deviceX corresponds to which hardware device, the user can read the name file /sys/bus/iio/devices/iio:deviceX/name. In case the sequence in which the iio device drivers are loaded/registered is constant, the numbering is constant and may be known in advance.
This specifies any shell prompt running on the target
root:/> cd /sys/bus/iio/devices/ root:/sys/bus/iio/devices> ls iio:device0 trigger0 root:/sys/bus/iio/devices> cd iio:device0 root:/sys/devices/platform/bfin-spi.0/spi0.5/iio:device0> ls -l -r--r--r-- 1 root root 4096 Jan 4 04:15 accel_xyz_squared_peak_raw drwxr-xr-x 2 root root 0 Jan 4 04:15 buffer -r--r--r-- 1 root root 4096 Jan 4 04:15 dev -rw-r--r-- 1 root root 4096 Jan 4 04:15 in_accel_x_calibbias -r--r--r-- 1 root root 4096 Jan 4 04:15 in_accel_x_raw -rw-r--r-- 1 root root 4096 Jan 4 04:15 in_accel_x_scale -rw-r--r-- 1 root root 4096 Jan 4 04:15 in_accel_y_calibbias -r--r--r-- 1 root root 4096 Jan 4 04:15 in_accel_y_raw -rw-r--r-- 1 root root 4096 Jan 4 04:15 in_accel_y_scale -rw-r--r-- 1 root root 4096 Jan 4 04:15 in_accel_z_calibbias -r--r--r-- 1 root root 4096 Jan 4 04:15 in_accel_z_raw -rw-r--r-- 1 root root 4096 Jan 4 04:15 in_accel_z_scale -r--r--r-- 1 root root 4096 Jan 4 04:15 in_temp0_raw -rw-r--r-- 1 root root 4096 Jan 4 04:15 in_temp0_scale -r--r--r-- 1 root root 4096 Jan 4 04:15 in_voltage0_supply_raw -rw-r--r-- 1 root root 4096 Jan 4 04:15 in_voltage0_supply_scale -r--r--r-- 1 root root 4096 Jan 4 04:15 in_voltage1_raw -r--r--r-- 1 root root 4096 Jan 4 04:15 name drwxr-xr-x 2 root root 0 Jan 4 04:15 power --w------- 1 root root 4096 Jan 4 04:15 reset -r--r--r-- 1 root root 4096 Jan 4 04:15 sampling_frequency_available drwxr-xr-x 2 root root 0 Jan 4 04:15 scan_elements lrwxrwxrwx 1 root root 0 Jan 4 04:15 subsystem -> ../../../../../bus/iio drwxr-xr-x 2 root root 0 Jan 4 04:15 trigger -rw-r--r-- 1 root root 4096 Jan 4 04:15 uevent
Show device name
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.5/iio:device0> cat name adis16240
ADIS16240 device attributes
For a detailed description please see: drivers/staging/iio/Documentation/sysfs-bus-iio
Device files |
---|
accel_xyz_squared_peak_raw |
in_accel_x_calibbias |
in_accel_x_raw |
in_accel_x_scale |
in_accel_y_calibbias |
in_accel_y_raw |
in_accel_y_scale |
in_accel_z_calibbias |
in_accel_z_raw |
in_accel_z_scale |
in_temp0_raw |
in_temp0_scale |
in_voltage0_supply_raw |
in_voltage0_supply_scale |
in_voltage1_raw |
name |
reset |
sampling_frequency_available |
Trigger management
This driver only supports it's own default trigger source adis16240-dev0
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.5/iio:device0> cat trigger/current_trigger adis16240-dev0
Buffer management
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.5/iio:device0/buffer> ls bytes_per_datum enable length
The Industrial I/O subsystem provides support for various ring buffer based data acquisition methods. Apart from device specific hardware buffer support, the user can chose between two different software ring buffer implementations. One is the IIO lock free software ring, and the other is based on Linux kfifo. Devices with buffer support feature an additional sub-folder in the /sys/bus/iio/devices/deviceX/ folder hierarchy. Called deviceX:bufferY, where Y defaults to 0, for devices with a single buffer.
Every buffer implementation features a set of files:
length
Get/set the number of sample sets that may be held by the buffer.
enable
Enables/disables the buffer. This file should be written last, after length and selection of scan elements.
watermark
A single positive integer specifying the maximum number of scan
elements to wait for.
Poll will block until the watermark is reached.
Blocking read will wait until the minimum between the requested
read amount or the low water mark is available.
Non-blocking read will retrieve the available samples from the
buffer even if there are less samples then watermark level. This
allows the application to block on poll with a timeout and read
the available samples after the timeout expires and thus have a
maximum delay guarantee.
data_available
A read-only value indicating the bytes of data available in the
buffer. In the case of an output buffer, this indicates the
amount of empty space available to write data to. In the case of
an input buffer, this indicates the amount of data available for
reading.
length_align_bytes
Using the high-speed interface. DMA buffers may have an alignment requirement for the buffer length.
Newer versions of the kernel will report the alignment requirements
associated with a device through the `length_align_bytes` property.
scan_elements
The scan_elements directory contains interfaces for elements that will be captured for a single triggered sample set in the buffer.
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.5/iio:device0/scan_elements>ls in_accel_x_en in_accel_z_index in_timestamp_type in_accel_x_index in_accel_z_type in_voltage0_supply_en in_accel_x_type in_temp0_en in_voltage0_supply_index in_accel_y_en in_temp0_index in_voltage0_supply_type in_accel_y_index in_temp0_type in_voltage1_en in_accel_y_type in_timestamp_en in_voltage1_index in_accel_z_en in_timestamp_index in_voltage1_type
in_voltageX_en / in_voltageX-voltageY_en / timestamp_en:
Scan element control for triggered data capture.
Writing 1 will enable the scan element, writing 0 will disable it
in_voltageX_type / in_voltageX-voltageY_type / timestamp_type:
Description of the scan element data storage within the buffer
and therefore in the form in which it is read from user-space.
Form is [s|u]bits/storage-bits. s or u specifies if signed
(2's complement) or unsigned. bits is the number of bits of
data and storage-bits is the space (after padding) that it
occupies in the buffer. Note that some devices will have
additional information in the unused bits so to get a clean
value, the bits value must be used to mask the buffer output
value appropriately. The storage-bits value also specifies the
data alignment. So u12/16 will be a unsigned 12 bit integer
stored in a 16 bit location aligned to a 16 bit boundary.
For other storage combinations this attribute will be extended
appropriately.
in_voltageX_index / in_voltageX-voltageY_index / timestamp_index:
A single positive integer specifying the position of this
scan element in the buffer. Note these are not dependent on
what is enabled and may not be contiguous. Thus for user-space
to establish the full layout these must be used in conjunction
with all _en attributes to establish which channels are present,
and the relevant _type attributes to establish the data storage
format.
More Information
- IIO mailing list: linux [dash] iio [at] vger [dot] kernel [dot] org
- ADISUSB的ADIS16240评估软件 2次下载
- EVADIIS16240 ADIS16240/PCB分线板 0次下载
- ADIS16080 IIO偏航率陀螺仪Linux驱动程序 2次下载
- ADIS16240评估板/工具概述 0次下载
- ADIS16240:低功耗、可编程冲击传感器和记录器数据表 6次下载
- ADIS16204 IIO可编程高g数字冲击传感器和记录仪Linux驱动程序 3次下载
- ADIS16480 IIO惯性测量组合Linux驱动程序 0次下载
- ADIS16136 IIO惯性测量组合Linux驱动程序 12次下载
- ADIS16400 IIO惯性测量组合Linux驱动程序 2次下载
- ADIS16130 IIO高精度角速率陀螺仪Linux驱动程序 1次下载
- ADISUSB的ADIS16240评估软件 4次下载
- ADIS16240参考代码 4次下载
- adis16240低功耗可编程冲击传感器和记录器数据表 1次下载
- 冲击传感器ADIS16240数据手册 23次下载
- 工业传感器解决方案-2009ADI公司 24次下载
- 现场可编程门阵列是什么 1520次阅读
- MEMS传感器所具备的嵌入式可编程功能 388次阅读
- 可编程电源的原理 可编程电源的优缺点 1606次阅读
- 可编程控制器的基本应用详细讲解 6207次阅读
- 如何写一个Linux设备驱动程序 4018次阅读
- Allegro推出双芯片高度可编程线性霍尔传感器 992次阅读
- 米尔科技LINUX设备驱动程序教程 1781次阅读
- 嵌入式Linux内核的驱动程序开发是怎样的 1284次阅读
- 基于嵌入式Linux内核的系统设备驱动程序开发设计 1031次阅读
- 基于Linux2.6.30开发DS18B20的驱动程序的类型和文件操作接口函数详解 1262次阅读
- 可编程控制器基本知识_可编程控制器原理及应用 5.6w次阅读
- 可动态安装的Linux设备驱动程序 882次阅读
- 基于LM57的可编程温度开关型模拟温度传感器 1803次阅读
- 温湿度传感器DHT11驱动程序 5.2w次阅读
- 电阻可编程模拟温度传感器设计方案 1600次阅读
下载排行
本周
- 1电子电路原理第七版PDF电子教材免费下载
- 0.00 MB | 1491次下载 | 免费
- 2单片机典型实例介绍
- 18.19 MB | 95次下载 | 1 积分
- 3S7-200PLC编程实例详细资料
- 1.17 MB | 27次下载 | 1 积分
- 4笔记本电脑主板的元件识别和讲解说明
- 4.28 MB | 18次下载 | 4 积分
- 5开关电源原理及各功能电路详解
- 0.38 MB | 11次下载 | 免费
- 6100W短波放大电路图
- 0.05 MB | 4次下载 | 3 积分
- 7基于单片机和 SG3525的程控开关电源设计
- 0.23 MB | 4次下载 | 免费
- 8基于AT89C2051/4051单片机编程器的实验
- 0.11 MB | 4次下载 | 免费
本月
- 1OrCAD10.5下载OrCAD10.5中文版软件
- 0.00 MB | 234313次下载 | 免费
- 2PADS 9.0 2009最新版 -下载
- 0.00 MB | 66304次下载 | 免费
- 3protel99下载protel99软件下载(中文版)
- 0.00 MB | 51209次下载 | 免费
- 4LabView 8.0 专业版下载 (3CD完整版)
- 0.00 MB | 51043次下载 | 免费
- 5555集成电路应用800例(新编版)
- 0.00 MB | 33562次下载 | 免费
- 6接口电路图大全
- 未知 | 30320次下载 | 免费
- 7Multisim 10下载Multisim 10 中文版
- 0.00 MB | 28588次下载 | 免费
- 8开关电源设计实例指南
- 未知 | 21539次下载 | 免费
总榜
- 1matlab软件下载入口
- 未知 | 935053次下载 | 免费
- 2protel99se软件下载(可英文版转中文版)
- 78.1 MB | 537793次下载 | 免费
- 3MATLAB 7.1 下载 (含软件介绍)
- 未知 | 420026次下载 | 免费
- 4OrCAD10.5下载OrCAD10.5中文版软件
- 0.00 MB | 234313次下载 | 免费
- 5Altium DXP2002下载入口
- 未知 | 233046次下载 | 免费
- 6电路仿真软件multisim 10.0免费下载
- 340992 | 191183次下载 | 免费
- 7十天学会AVR单片机与C语言视频教程 下载
- 158M | 183277次下载 | 免费
- 8proe5.0野火版下载(中文版免费下载)
- 未知 | 138039次下载 | 免费
评论
查看更多