电子发烧友App
创作
发文章
发帖 
提问 
发资料
发视频资料介绍
Table of Contents
Digital Potentiometer Linux Driver
Supported Devices
Reference Circuits
Evaluation Boards
- PMOD-DPOT
Description
The ad525x_dpot driver exports a simple sysfs interface. This allows you to work with the immediate resistance settings as well as update the saved startup settings. Access to the factory programmed tolerance is also provided, but interpretation of this settings is required by the end application according to the specific part in use.
Files
Each dpot device will have a set of eeprom, rdac, and tolerance files. How many depends on the actual part you have, as will the range of allowed values.
The eeprom files are used to program the startup value of the device.
The rdac files are used to program the immediate value of the device.
The tolerance files are the read-only factory programmed tolerance settings and may vary greatly on a part-by-part basis. For exact interpretation of this field, please consult the datasheet for your part. This is presented as a hex file for easier parsing.
Source Code
Status
Files
| Function | File |
|---|---|
| driver | drivers/misc/ad525x_dpot.c |
| i2c bus support | drivers/misc/ad525x_dpot-i2c.c |
| spi bus support | drivers/misc/ad525x_dpot-spi.c |
| include | drivers/misc/ad525x_dpot.h |
Example platform device initialization
For compile time configuration, it’s common Linux practice to keep board- and application-specific configuration out of the main driver file, instead putting it into the board support file.
For devices on custom boards, as typical of embedded and SoC-(system-on-chip) based hardware, Linux uses platform_data to point to board-specific structures describing devices and how they are connected to the SoC. This can include available ports, chip variants, preferred modes, default initialization, additional pin roles, and so on. This shrinks the board-support packages (BSPs) and minimizes board and application specific #ifdefs in drivers.
Example Platform / Board file (I2C Interface)
Declaring I2C devices
Unlike PCI or USB devices, I2C devices are not enumerated at the hardware level. Instead, the software must know which devices are connected on each I2C bus segment, and what address these devices are using. For this reason, the kernel code must instantiate I2C devices explicitly. There are different ways to achieve this, depending on the context and requirements. However the most common method is to declare the I2C devices by bus number.
This method is appropriate when the I2C bus is a system bus, as in many embedded systems, wherein each I2C bus has a number which is known in advance. It is thus possible to pre-declare the I2C devices that inhabit this bus. This is done with an array of struct i2c_board_info, which is registered by calling i2c_register_board_info().
So, to enable such a driver one need only edit the board support file by adding an appropriate entry to i2c_board_info.
For more information see: Documentation/i2c/instantiating-devices
static struct i2c_board_info __initdata bfin_i2c_board_info[] = { #if defined(CONFIG_AD525X_DPOT) || defined(CONFIG_AD525X_DPOT_MODULE) { I2C_BOARD_INFO("ad5245", 0x2c), }, { I2C_BOARD_INFO("ad5245", 0x2d), }, #endif }
Example Platform / Board file (SPI Interface)
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
static struct spi_board_info bfin_spi_board_info[] __initdata = { #if defined(CONFIG_AD525X_DPOT) || defined(CONFIG_AD525X_DPOT_MODULE) { .modalias = "ad5291", .max_speed_hz = 5000000, /* max spi clock (SCK) speed in HZ */ .bus_num = 0, .chip_select = 1, }, #endif };
Old Method
static struct spi_board_info bfin_spi_board_info[] __initdata = { #if defined(CONFIG_AD525X_DPOT) || defined(CONFIG_AD525X_DPOT_MODULE) { .modalias = "ad_dpot", .platform_data = "ad5291", .max_speed_hz = 5000000, /* max spi clock (SCK) speed in HZ */ .bus_num = 0, .chip_select = 1, }, #endif };
Adding Linux driver support
Configure kernel with “make menuconfig” (alternatively use “make xconfig” or “make qconfig”)
The ad525x_dpot driver depends on CONFIG_SPI or CONFIG_I2C
Device Drivers --->
[*] Misc devices --->
<*> Analog Devices Digital Potentiometers
<*> support I2C bus connection
<*> support SPI bus connection
Hardware configuration
Driver testing
Locate the device in your sysfs tree. This is probably easiest by going into the common i2c directory and locating the device by the i2c slave address.
# ls /sys/bus/i2c/devices/ 0-0022 0-0027 0-002fSo assuming the device in question is on the first i2c bus and has the slave address of 0x2f, we descend (unrelated sysfs entries have been trimmed).
# ls /sys/bus/i2c/devices/0-002f/ eeprom0 rdac0 tolerance0You can use simple reads/writes to access these files:
# cd /sys/bus/i2c/devices/0-002f/ # cat eeprom0 0 # echo 10 > eeprom0 # cat eeprom0 10 # cat rdac0 5 # echo 3 > rdac0 # cat rdac0 3
More Information
- 嵌入式Linux驱动程序开发 6次下载
- 数字电位器X9C103的测试程序代码下载 52次下载
- AD9834 IIO直接数字合成Linux驱动程序 1次下载
- AD9832 IIO直接数字合成Linux驱动程序 3次下载
- STM32F103数字电位器X9C103的驱动程序免费下载 156次下载
- 优化数字电位器电路设计方案 11次下载
- TI达芬奇Linux驱动程序LSP 2.10的详细资料介绍 3次下载
- Linux驱动程序缺陷检测研究 9次下载
- Linux系统网络驱动程序的编写 0次下载
- 基于Linux下的LCD驱动程序实现 12次下载
- 第9章 Linux驱动程序设计 3次下载
- DAC与数字电位器 62次下载
- 理解和应用数字电位器 52次下载
- 从机械式电位器升级到数字电位器 45次下载
- 步进电机的Linux驱动程序 45次下载
- 数字电位器取代机械电位器 1477次阅读
- AD8400系列数字电位器的驱动设计与实现 2668次阅读
- AD527x系列数字电位器的驱动设计与实现 1514次阅读
- 米尔科技LINUX设备驱动程序教程 1781次阅读
- 可动态安装的Linux设备驱动程序 882次阅读
- 数字电位器AD5160测试程序 2w次阅读
- 如何理解数字电位器 8980次阅读
- 如何制作数字电位器_数字电位器制作方法 1.9w次阅读
- 常用数字电位器芯片有哪些 10.9w次阅读
- 数字电位器x9c103应用电路 4.5w次阅读
- 数字电位器工作原理详解_数字电位器应用_数字电位器选型指南 5.7w次阅读
- 数字电位器控制原理图 3.2w次阅读
- 数字电位器应用实例_数字电位器四大应用电路 4.3w次阅读
- 数字电位器怎么选型_数字电位器选型指南 8504次阅读
- 数字电位器串口设计与仿真 1589次阅读
上传资料赚积分下载排行
本周
- 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次下载 | 免费
工商网监
评论