電子發燒友App
創作
發文章
發帖 
提問 
發資料
發視頻資料介紹
Table of Contents
AD5064 IIO Quad-Channel DAC Linux Driver
Supported Devices
- AD5625, (Upstream v4.6+)
- AD5625R, (Upstream v4.6+)
- AD5627, (Upstream v4.6+)
- AD5627R, (Upstream v4.6+)
- AD5645R, (Upstream v4.6+)
- AD5647R, (Upstream v4.6+)
- AD5665, (Upstream v4.6+)
- AD5665R, (Upstream v4.6+)
- AD5667, (Upstream v4.6+)
- AD5667R, (Upstream v4.6+)
- LTC2606, (Upstream v4.5+)
- LTC2607, (Upstream v4.5+)
- LTC2609, (Upstream v4.5+)
- LTC2616, (Upstream v4.5+)
- LTC2617, (Upstream v4.5+)
- LTC2619, (Upstream v4.5+)
- LTC2626, (Upstream v4.5+)
- LTC2627, (Upstream v4.5+)
- LTC2629, (Upstream v4.5+)
Reference Circuits
Evaluation Boards
- PMOD-DA4
Description
This is a Linux industrial I/O (IIO) subsystem driver, targeting multi-channel serial interface DACs. 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/iio/dac/ad5064.c |
Example platform device initialization
Specifying reference voltage via the regulator framework
Below example specifies a 2.5 Volt reference for the SPI device 3 on SPI-Bus 0. (spi0.3) In this example all 4 reference voltage are supplied by the same regulator.
#if defined(CONFIG_REGULATOR_FIXED_VOLTAGE) || defined(CONFIG_REGULATOR_FIXED_VOLTAGE_MODULE) static struct regulator_consumer_supply ad5064_consumer_supplies[] = { REGULATOR_SUPPLY("vrefA", "spi0.3"), REGULATOR_SUPPLY("vrefB", "spi0.3"), REGULATOR_SUPPLY("vrefC", "spi0.3"), REGULATOR_SUPPLY("vrefD", "spi0.3"), }; ? static struct regulator_init_data stamp_avdd_reg_init_data = { .constraints = { .name = "2V5", .valid_ops_mask = REGULATOR_CHANGE_STATUS, }, .consumer_supplies = ad5624_consumer_supplies, .num_consumer_supplies = ARRAY_SIZE(ad5624_consumer_supplies), }; ? static struct fixed_voltage_config stamp_vdd_pdata = { .supply_name = "board-2V5", .microvolts = 2500000, .gpio = -EINVAL, .enabled_at_boot = 0, .init_data = &stamp_avdd_reg_init_data, }; static struct platform_device brd_voltage_regulator = { .name = "reg-fixed-voltage", .id = -1, .num_resources = 0, .dev = { .platform_data = &stamp_vdd_pdata, }, }; #endif
static struct platform_device *board_devices[] __initdata = { #if defined(CONFIG_REGULATOR_FIXED_VOLTAGE) || defined(CONFIG_REGULATOR_FIXED_VOLTAGE_MODULE) &brd_voltage_regulator #endif };
static int __init board_init(void) { [--snip--] ? platform_add_devices(board_devices, ARRAY_SIZE(board_devices)); ? [--snip--] ? return 0; } arch_initcall(board_init);
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_AD5064_SPI) || / defined(CONFIG_AD5064_SPI_MODULE) { /* the modalias must be the same as spi device driver name */ .modalias = "ad5064", /* Name of spi_driver for this device */ .max_speed_hz = 1000000, /* max spi clock (SCK) speed in HZ */ .bus_num = 0, /* Framework bus number */ .chip_select = 3, /* Framework chip select */ .mode = SPI_MODE_1, }, #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 AD5064 Driver depends on CONFIG_SPI
Linux Kernel Configuration
Device Drivers --->
...
<*> Industrial I/O support --->
--- Industrial I/O support
...
Digital to analog converters --->
...
<*> Analog Devices AD5064 and similar multi-channel DAC driver
...
...
...
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 root:/sys/bus/iio/devices> cd iio:device0 root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> ls -l -r--r--r-- 1 root root 4096 Jan 1 03:29 dev -r--r--r-- 1 root root 4096 Jan 1 03:29 name -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage0_powerdown -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage0_powerdown_mode -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage0_raw -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage0_scale -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage1_powerdown -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage1_powerdown_mode -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage1_raw -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage1_scale -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage2_powerdown -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage2_powerdown_mode -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage2_raw -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage2_scale -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage3_powerdown -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage3_powerdown_mode -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage3_raw -rw-r--r-- 1 root root 4096 Jan 1 03:29 out_voltage3_scale -r--r--r-- 1 root root 4096 Jan 1 03:29 out_voltage_powerdown_mode_available drwxr-xr-x 2 root root 0 Jan 3 16:50 power lrwxrwxrwx 1 root root 0 Jan 3 16:50 subsystem -> ../../../../../bus/iio -rw-r--r-- 1 root root 4096 Jan 3 16:50 uevent
The number of channels depends on the chip model.
Show device name
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> cat name ad5064
Show scale
Description:
/sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
scale to be applied to out_voltage0_raw in order to obtain the measured voltage in millivolts.
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> cat out_voltage0_scale 0.038140
Set channel Y output voltage
Description:
/sys/bus/iio/devices/iio:deviceX/out_voltageY_raw
Raw (unscaled, no bias etc.) output voltage for channel Y.
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> echo 10000 > out_voltage0_raw
U = out_voltage0_raw * out_voltage0_scale = 10000 * 0,038140 mV = 381,14 mV
List available power down modes
/sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode_available
Description:
Lists all available output power down modes.
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> cat out_voltage_powerdown_mode_available 1kohm_to_gnd 100kohm_to_gnd three_state
Set power down mode
/sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown_mode
Description:
Specifies the output power down mode.
DAC output stage is disconnected from the amplifier and
| 1kohm_to_gnd | connected to ground via an 1kOhm resistor |
| 100kohm_to_gnd | connected to ground via an 100kOhm resistor |
| three_state | left floating |
For a list of available output power down options read out_voltage_powerdown_mode_available.
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> echo three_state > out_voltage_powerdown_mode root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> cat out_voltage_powerdown_mode three_state
Enable power down mode on output Y
/sys/bus/iio/devices/iio:deviceX/out_voltageY_powerdown
Description:
Writing 1 causes output Y to enter the power down mode specified
by the corresponding out_voltageY_powerdown_mode. Clearing returns to
normal operation.
This specifies any shell prompt running on the target
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> echo 1 > out_voltage0_powerdown root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> cat out_voltage0_powerdown 1 root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> echo 0 > out_voltage0_powerdown root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> cat out_voltage0_powerdown 0
PMOD-DA4
The PMOD-DA4 is a PMOD board made by Digilent Inc. which features the AD5628
The following example shows how to connect the PMOD-DA4 to a Blackfin BF537-STAMP board.
Hardware configuration
| BF537-STAMP (P9) SPI header | PMOD-DA4 | ||
|---|---|---|---|
| PIN | Function | PIN | Function |
| 2 | (+3.3V) | 6 | VDD |
| 5 | SPI_MOSI | 2 | DIN |
| 8 | SPI_SCK | 4 | SCLK |
| 10 | SPI_SS | 1 | SYNC |
| 20 | GND | 5 | GND |
More Information
- IIO mailing list: linux [dash] iio [at] vger [dot] kernel [dot] org
- AD5449 IIO DAC Linux驅動程序
- AD5380 IIO多通道Linux驅動程序DAC
- AD5421 IIO DAC Linux驅動程序
- AD5360 IIO多通道Linux驅動程序DAC
- AD7303 IIO DAC Linux驅動程序
- AD5446 IIO DAC Linux驅動程序
- AD5764 IIO四通道Linux驅動程序DAC
- AD5624 IIO四通道Linux驅動程序DAC
- AD7606 IIO多通道同步采樣ADC Linux驅動程序
- IIO單通道串行ADC Linux驅動程序
- AD9834 IIO直接數字合成Linux驅動程序
- AD9832 IIO直接數字合成Linux驅動程序
- AD7998 IIO ADC Linux驅動程序
- AD7887 IIO ADC Linux驅動程序
- AD5677R NanDAC+IIO Linux驅動程序
- 基于LM3900四通道放大器的簡單多通道混音器電路 5285次閱讀
- 基于ADI AD522集成16位單元方案設置DAC四參數測量 3285次閱讀
- 四通道異步收發器TL16C554芯片特點、工作原理及實現應用設計 1.1w次閱讀
- 如何寫一個Linux設備驅動程序 4535次閱讀
- 米爾科技LINUX設備驅動程序教程 2105次閱讀
- 嵌入式Linux內核的驅動程序開發是怎樣的 1524次閱讀
- 節能型四通道低邊智能電源開關的介紹 3364次閱讀
- 基于Linux2.6.30開發DS18B20的驅動程序的類型和文件操作接口函數詳解 1500次閱讀
- 可動態安裝的Linux設備驅動程序 1013次閱讀
- 14位125MSPS四通道ADC電路圖（通過后端數字求和增強SNR性能） 4905次閱讀
- 高性能65 MHz帶寬四通道中頻接收機電路圖 4824次閱讀
- 14位125MSPS四通道ADC，通過后端數字求和增強SNR性能 2380次閱讀
- 用于車載供電的四通道電源管理IC PCB布局指南 2108次閱讀
- MAX14954四通道均衡器/轉接驅動器 1700次閱讀
- 四通道溫度傳感器電路圖 3517次閱讀
上傳資料賺積分下載排行
本周
- 1AN-1267: 使用ADSP-CM408F ADC控制器的電機控制反饋采樣時序
- 1.41MB | 3次下載 | 免費
- 2AN158 GD32VW553 Wi-Fi開發指南
- 1.51MB | 2次下載 | 免費
- 3AN148 GD32VW553射頻硬件開發指南
- 2.07MB | 1次下載 | 免費
- 4AN-1154: 采用恒定負滲漏電流優化ADF4157和ADF4158 PLL的相位噪聲和雜散性能
- 199.28KB | 次下載 | 免費
- 5AN-960: RS-485/RS-422電路實施指南
- 380.8KB | 次下載 | 免費
- 6EE-249：使用VisualDSP在ADSP-218x DSP上實現軟件疊加
- 60.02KB | 次下載 | 免費
- 7AN-1111: 使用ADuCM360/ADuCM361時的降低功耗選項
- 306.09KB | 次下載 | 免費
- 8AN-904: ADuC7028評估板參考指南
- 815.82KB | 次下載 | 免費
本月
- 1ADI高性能電源管理解決方案
- 2.43 MB | 450次下載 | 免費
- 2免費開源CC3D飛控資料（電路圖&PCB源文件、BOM、
- 5.67 MB | 138次下載 | 1 積分
- 3基于STM32單片機智能手環心率計步器體溫顯示設計
- 0.10 MB | 130次下載 | 免費
- 4使用單片機實現七人表決器的程序和仿真資料免費下載
- 2.96 MB | 44次下載 | 免費
- 5美的電磁爐維修手冊大全
- 1.56 MB | 24次下載 | 5 積分
- 6如何正確測試電源的紋波
- 0.36 MB | 18次下載 | 免費
- 7感應筆電路圖
- 0.06 MB | 10次下載 | 免費
- 8萬用表UT58A原理圖
- 0.09 MB | 9次下載 | 5 積分
總榜
- 1matlab軟件下載入口
- 未知 | 935121次下載 | 10 積分
- 2開源硬件-PMP21529.1-4 開關降壓/升壓雙向直流/直流轉換器 PCB layout 設計
- 1.48MB | 420062次下載 | 10 積分
- 3Altium DXP2002下載入口
- 未知 | 233088次下載 | 10 積分
- 4電路仿真軟件multisim 10.0免費下載
- 340992 | 191367次下載 | 10 積分
- 5十天學會AVR單片機與C語言視頻教程 下載
- 158M | 183335次下載 | 10 積分
- 6labview8.5下載
- 未知 | 81581次下載 | 10 積分
- 7Keil工具MDK-Arm免費下載
- 0.02 MB | 73810次下載 | 10 積分
- 8LabVIEW 8.6下載
- 未知 | 65988次下載 | 10 積分
工商網監
評論