99精品伊人亚洲|最近国产中文炮友|九草在线视频支援|AV网站大全最新|美女黄片免费观看|国产精品资源视频|精彩无码视频一区|91大神在线后入|伊人终合在线播放|久草综合久久中文

電子發(fā)燒友App

硬聲App

0
  • 聊天消息
  • 系統(tǒng)消息
  • 評(píng)論與回復(fù)
登錄后你可以
  • 下載海量資料
  • 學(xué)習(xí)在線課程
  • 觀看技術(shù)視頻
  • 寫文章/發(fā)帖/加入社區(qū)
會(huì)員中心
創(chuàng)作中心

完善資料讓更多小伙伴認(rèn)識(shí)你,還能領(lǐng)取20積分哦,立即完善>

3天內(nèi)不再提示
創(chuàng)作
電子發(fā)燒友網(wǎng)>電子資料下載>類型>參考設(shè)計(jì)>AD5360 IIO多通道Linux驅(qū)動(dòng)程序DAC

AD5360 IIO多通道Linux驅(qū)動(dòng)程序DAC

2021-05-23 | pdf | 87.28KB | 次下載 | 2積分

資料介紹

This version (05 Jan 2021 17:02) was approved by Ioana Chelaru.The Previously approved version (01 Sep 2020 09:31) is available.Diff

AD5360 IIO Multi-Channel DAC Linux Driver

Supported Devices

Evaluation Boards

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

Source Mainlined?
git Yes

Files

Function File
driver drivers/iio/dac/ad5360.c

Example device tree

	fragment@0 {
		target-path = "/";
		__overlay__ {
			vref0: fixedregulator@0 {
				compatible = "regulator-fixed";
				regulator-name = "fixed-supply";
				regulator-min-microvolt = <3000000>;
				regulator-max-microvolt = <3000000>;
				regulator-boot-on;
			};
			vref1: fixedregulator@1 {
				compatible = "regulator-fixed";
				regulator-name = "fixed-supply";
				regulator-min-microvolt = <3000000>;
				regulator-max-microvolt = <3000000>;
				regulator-boot-on;
			};
		};
	};
?
	fragment@1 {
		target = <&spi0>;
		__overlay__ {
			#address-cells = <1>;
			#size-cells = <0>;
			status = "okay";
?
			ad5370@0{
				compatible = "adi,ad5370";
				reg = <0>;
				spi-max-frequency = <1000000>;
				spi-cpha;
				vref0-supply = <&vref0>;
				vref1-supply = <&vref1>;
			};
		};
	};
};

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.

Except for the AD5371 devices expect two supplies named “vref0” and “vref1”. The AD5371 expects a third supply named “vref2”.

#if defined(CONFIG_REGULATOR_FIXED_VOLTAGE) || defined(CONFIG_REGULATOR_FIXED_VOLTAGE_MODULE)
static struct regulator_consumer_supply ad5360_consumer_supplies[] = {
	REGULATOR_SUPPLY("vref0", "spi0.3"),
	REGULATOR_SUPPLY("vref1", "spi0.3"),
	REGULATOR_SUPPLY("vref2", "spi0.3"),
};
?
static struct regulator_init_data stamp_avdd_reg_init_data = {
	.constraints	= {
		.name	= "2V5",
		.valid_ops_mask = REGULATOR_CHANGE_STATUS,
	},
	.consumer_supplies = ad5360_consumer_supplies,
	.num_consumer_supplies = ARRAY_SIZE(ad5360_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

21 Oct 2010 16:10

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_AD5360_SPI) || /
 	defined(CONFIG_AD5360_SPI_MODULE)
	{
		/* the modalias must be the same as spi device driver name */
		.modalias = "ad5360", /* 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 AD5360 Driver depends on CONFIG_SPI

Linux Kernel Configuration
    Device Drivers  --->
        ...
        <*>     Industrial I/O support --->
            --- Industrial I/O support
            ...
            Digital to analog converters  ---> 
                ...
                <*>  Analog Devices Analog Devices AD5360/61/62/63/70/71/73 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.

02 Mar 2011 15:16

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  2 21:54 dev
-r--r--r--    1 root     root          4096 Jan  2 21:54 name
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage0_calibbias
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage0_calibscale
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage0_offset
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage0_raw
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage0_scale
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage10_calibbias
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage10_calibscale
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage10_offset
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage10_raw
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage10_scale
...
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage_powerdown
drwxr-xr-x    2 root     root             0 Jan  2 21:54 power
lrwxrwxrwx    1 root     root             0 Jan  2 21:54 subsystem -> ../../../../../bus/iio
-rw-r--r--    1 root     root          4096 Jan  2 21:54 uevent

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
ad5360

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

Calibrate channel Y gain

Description:
/sys/bus/iio/devices/iio:deviceX/out_voltageY_calibscale

Each channel has an adjustable gain which can be used to calibrate the channel's scale and compensate for full-scale errors. The default value is 65535.

If scale calibration is used the following formula can be used calculate the output voltage: U = ( ( out_voltageY_raw * ( out_voltageY_calibscale + 1 ) ) / 2^16 - out_voltageY_calibbias ) * out_voltageY_scale

Calibrate channel Y offset

Description:
/sys/bus/iio/devices/iio:deviceX/out_voltageY_calibbias

Each channel has an adjustable offset which can be used to calibrate the channel's offset and compensate for zero-scale errors. The default value is 0.

If offset calibration is used the following formula can be used calculate the output voltage: U = ( ( out_voltageY_raw * ( out_voltageY_calibscale + 1 ) ) / 2^16 - out_voltageY_calibbias ) * out_voltageY_scale

Enable power down mode for the device

/sys/bus/iio/devices/iio:deviceX/out_voltage_powerdown

Description:
Writing 1 causes the device to enter power down 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_voltage_powerdown
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> cat out_voltage_powerdown
1
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> echo 0 > out_voltage_powerdown
root:/sys/devices/platform/bfin-spi.0/spi0.3/iio:device0> cat out_voltage_powerdown
0

More Information

下載該資料的人也在下載 下載該資料的人還在閱讀
更多 >

評(píng)論

查看更多

下載排行

本周

  1. 1AN-1267: 使用ADSP-CM408F ADC控制器的電機(jī)控制反饋采樣時(shí)序
  2. 1.41MB   |  3次下載  |  免費(fèi)
  3. 2AN158 GD32VW553 Wi-Fi開發(fā)指南
  4. 1.51MB   |  2次下載  |  免費(fèi)
  5. 3AN148 GD32VW553射頻硬件開發(fā)指南
  6. 2.07MB   |  1次下載  |  免費(fèi)
  7. 4AN-1154: 采用恒定負(fù)滲漏電流優(yōu)化ADF4157和ADF4158 PLL的相位噪聲和雜散性能
  8. 199.28KB   |  次下載  |  免費(fèi)
  9. 5AN-960: RS-485/RS-422電路實(shí)施指南
  10. 380.8KB   |  次下載  |  免費(fèi)
  11. 6EE-249:使用VisualDSP在ADSP-218x DSP上實(shí)現(xiàn)軟件疊加
  12. 60.02KB   |  次下載  |  免費(fèi)
  13. 7AN-1111: 使用ADuCM360/ADuCM361時(shí)的降低功耗選項(xiàng)
  14. 306.09KB   |  次下載  |  免費(fèi)
  15. 8AN-904: ADuC7028評(píng)估板參考指南
  16. 815.82KB   |  次下載  |  免費(fèi)

本月

  1. 1ADI高性能電源管理解決方案
  2. 2.43 MB   |  450次下載  |  免費(fèi)
  3. 2免費(fèi)開源CC3D飛控資料(電路圖&PCB源文件、BOM、
  4. 5.67 MB   |  138次下載  |  1 積分
  5. 3基于STM32單片機(jī)智能手環(huán)心率計(jì)步器體溫顯示設(shè)計(jì)
  6. 0.10 MB   |  130次下載  |  免費(fèi)
  7. 4使用單片機(jī)實(shí)現(xiàn)七人表決器的程序和仿真資料免費(fèi)下載
  8. 2.96 MB   |  44次下載  |  免費(fèi)
  9. 5美的電磁爐維修手冊大全
  10. 1.56 MB   |  24次下載  |  5 積分
  11. 6如何正確測試電源的紋波
  12. 0.36 MB   |  18次下載  |  免費(fèi)
  13. 7感應(yīng)筆電路圖
  14. 0.06 MB   |  10次下載  |  免費(fèi)
  15. 8萬用表UT58A原理圖
  16. 0.09 MB   |  9次下載  |  5 積分

總榜

  1. 1matlab軟件下載入口
  2. 未知  |  935121次下載  |  10 積分
  3. 2開源硬件-PMP21529.1-4 開關(guān)降壓/升壓雙向直流/直流轉(zhuǎn)換器 PCB layout 設(shè)計(jì)
  4. 1.48MB  |  420062次下載  |  10 積分
  5. 3Altium DXP2002下載入口
  6. 未知  |  233088次下載  |  10 積分
  7. 4電路仿真軟件multisim 10.0免費(fèi)下載
  8. 340992  |  191367次下載  |  10 積分
  9. 5十天學(xué)會(huì)AVR單片機(jī)與C語言視頻教程 下載
  10. 158M  |  183335次下載  |  10 積分
  11. 6labview8.5下載
  12. 未知  |  81581次下載  |  10 積分
  13. 7Keil工具M(jìn)DK-Arm免費(fèi)下載
  14. 0.02 MB  |  73810次下載  |  10 積分
  15. 8LabVIEW 8.6下載
  16. 未知  |  65988次下載  |  10 積分