色哟哟视频在线观看-色哟哟视频在线-色哟哟欧美15最新在线-色哟哟免费在线观看-国产l精品国产亚洲区在线观看-国产l精品国产亚洲区久久

電子發燒友App

硬聲App

0
  • 聊天消息
  • 系統消息
  • 評論與回復
登錄后你可以
  • 下載海量資料
  • 學習在線課程
  • 觀看技術視頻
  • 寫文章/發帖/加入社區
會員中心
創作中心

完善資料讓更多小伙伴認識你,還能領取20積分哦,立即完善>

3天內不再提示
創作
電子發燒友網>電子資料下載>類型>參考設計>AD5380 IIO多通道Linux驅動程序DAC

AD5380 IIO多通道Linux驅動程序DAC

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

資料介紹

This version (05 Jan 2021 17:02) was approved by Ioana Chelaru.The Previously approved version (11 Feb 2016 20:51) is available.Diff

AD5380 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/ad5380.c

Example platform device initialization

Specifying reference voltage via the regulator framework

The AD538X/AD539X can either use an internal or an external reference voltage. To use an external reference voltage use the regulator framework to provide a regulator supply. The supply should be calledvref”.

Below example specifies a 2.5 Volt reference for the SPI device 3 on SPI-Bus 0. (spi0.3)

#if IS_ENABLED(CONFIG_REGULATOR_FIXED_VOLTAGE)
static struct regulator_consumer_supply ad5380_consumer_supplies[] = {
	REGULATOR_SUPPLY("vref", "spi0.3"),
};
?
static struct regulator_init_data stamp_avdd_reg_init_data = {
	.constraints	= {
		.name	= "2V5",
		.valid_ops_mask = REGULATOR_CHANGE_STATUS,
	},
	.consumer_supplies = ad5380_consumer_supplies,
	.num_consumer_supplies = ARRAY_SIZE(ad5380_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 IS_ENABLED(CONFIG_REGULATOR_FIXED_VOLTAGE)
	&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 IS_ENABLED(CONFIG_AD5380)
	{
		/* the modalias must be the same as spi device driver name */
		.modalias = "ad5380-5", /* 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);

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

21 Oct 2010 16:10

Depending on the converter IC used, you may need to set the modalias accordingly, matching your part name.

The part name needs a -3 or -5 depending on whether a 1.25V or 2.5V internal reference is used. E.g. “ad5380-5” or “ad5391-3”.

The I2C device id depends on the AD0 and AD1 pin settings and needs to be set according to your board setup.

AD1 AD0 I2C device id
0 0 0x54
0 1 0x55
1 0 0x56
1 1 0x57

In this example we assume ADDR0=0 and ADDR1=0.

static struct i2c_board_info __initdata bfin_i2c_board_info[] = {
?
	[--snip--]
	{
		I2C_BOARD_INFO("a5380", 0x38),
	},
	[--snip--]
}
static int __init stamp_init(void)
{
	[--snip--]
	i2c_register_board_info(0, bfin_i2c_board_info,
				ARRAY_SIZE(bfin_i2c_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 AD5380 Driver depends on CONFIG_SPI_MASTER or CONFIG_I2C

Linux Kernel Configuration
    Device Drivers  --->
        ...
        <*>     Industrial I/O support --->
            --- Industrial I/O support
            ...
            Digital to analog converters  ---> 
                ...
                <*>  Analog Devices AD5380/81/82/83/84/90/91/92 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_raw
-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_raw
...
-rw-r--r--    1 root     root          4096 Jan  3 21:54 out_voltage9_calibbias
-rw-r--r--    1 root     root          4096 Jan  3 21:54 out_voltage9_calibscale
-rw-r--r--    1 root     root          4096 Jan  3 21:54 out_voltage9_raw
-rw-r--r--    1 root     root          4096 Jan  2 21:54 out_voltage_powerdown
-rw-r--r--    1 root     root          4096 Jan  3 21:54 out_voltage_powerdown_mode
-r--r--r--    1 root     root          4096 Jan  3 21:54 out_voltage_powerdown_mode_available
-rw-r--r--    1 root     root          4096 Jan  3 21:54 out_voltage_scale
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
ad5380

Show scale

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

scale to be applied to out_voltageY_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_voltage_scale
0.305000

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,305000 mV = 305,00 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 16382. The minimum value is 0, the maximum value is 16383.

If scale calibration is used the following formula can be used calculate the output voltage:
U = ( ( out_voltageY_raw * ( out_voltageY_calibscale + 2) ) / 2^14 + 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. The minimum value is -8192, the maximum value is 8191.

If offset calibration is used the following formula can be used calculate the output voltage:
U = ( ( out_voltageY_raw * ( out_voltageY_calibscale + 2 ) ) / 2^14 + 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

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
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

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

More Information

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

評論

查看更多

下載排行

本周

  1. 1電子電路原理第七版PDF電子教材免費下載
  2. 0.00 MB  |  1491次下載  |  免費
  3. 2單片機典型實例介紹
  4. 18.19 MB  |  95次下載  |  1 積分
  5. 3S7-200PLC編程實例詳細資料
  6. 1.17 MB  |  27次下載  |  1 積分
  7. 4筆記本電腦主板的元件識別和講解說明
  8. 4.28 MB  |  18次下載  |  4 積分
  9. 5開關電源原理及各功能電路詳解
  10. 0.38 MB  |  11次下載  |  免費
  11. 6100W短波放大電路圖
  12. 0.05 MB  |  4次下載  |  3 積分
  13. 7基于單片機和 SG3525的程控開關電源設計
  14. 0.23 MB  |  4次下載  |  免費
  15. 8基于AT89C2051/4051單片機編程器的實驗
  16. 0.11 MB  |  4次下載  |  免費

本月

  1. 1OrCAD10.5下載OrCAD10.5中文版軟件
  2. 0.00 MB  |  234313次下載  |  免費
  3. 2PADS 9.0 2009最新版 -下載
  4. 0.00 MB  |  66304次下載  |  免費
  5. 3protel99下載protel99軟件下載(中文版)
  6. 0.00 MB  |  51209次下載  |  免費
  7. 4LabView 8.0 專業版下載 (3CD完整版)
  8. 0.00 MB  |  51043次下載  |  免費
  9. 5555集成電路應用800例(新編版)
  10. 0.00 MB  |  33562次下載  |  免費
  11. 6接口電路圖大全
  12. 未知  |  30320次下載  |  免費
  13. 7Multisim 10下載Multisim 10 中文版
  14. 0.00 MB  |  28588次下載  |  免費
  15. 8開關電源設計實例指南
  16. 未知  |  21539次下載  |  免費

總榜

  1. 1matlab軟件下載入口
  2. 未知  |  935053次下載  |  免費
  3. 2protel99se軟件下載(可英文版轉中文版)
  4. 78.1 MB  |  537793次下載  |  免費
  5. 3MATLAB 7.1 下載 (含軟件介紹)
  6. 未知  |  420026次下載  |  免費
  7. 4OrCAD10.5下載OrCAD10.5中文版軟件
  8. 0.00 MB  |  234313次下載  |  免費
  9. 5Altium DXP2002下載入口
  10. 未知  |  233046次下載  |  免費
  11. 6電路仿真軟件multisim 10.0免費下載
  12. 340992  |  191183次下載  |  免費
  13. 7十天學會AVR單片機與C語言視頻教程 下載
  14. 158M  |  183277次下載  |  免費
  15. 8proe5.0野火版下載(中文版免費下載)
  16. 未知  |  138039次下載  |  免費
主站蜘蛛池模板: 免费亚洲视频| 在线播放国产视频| 男人有噶坏| 国产偷国产偷亚洲高清app| 91免费永久在线地址| 偷偷鲁青春草原视频| 免费观看高清黄页网址大全| 国产午夜精品久久久久婷婷| jizzhd中国| 国产精品嫩草影院在线观看免费 | 亚洲成人三级| 欧美一区二区三区不卡免费| 久久久久久久免费| 国产亚洲精品久久久久久禁果TV| 超碰caoporn| 99午夜视频| 综合精品欧美日韩国产在线| 亚洲 欧美 中文字幕 在线| 色老99九久精品偷偷鲁| 欧美精品一区二区三区视频| 久久久久久电影| 含羞草传媒在线观看| 国产传媒18精品A片在线观看| freevideoshd| 9位美女厕所撒尿11分| 在线亚洲视频无码天堂| 亚洲午夜性春猛交XXXX| 无限资源在线观看播放| 日本日本熟妇中文在线视频| 欧美一区二区视频高清专区| 毛片免费观看的视频| 久久视频在线视频观看天天看视频| 国拍自产精品福利区| 国产人成高清在线视频99| 国产97视频在线观看| 囯产精品一区二区三区线| 粉嫩小护士| 国产精品久久久久久久久久影院| 国产AV天堂一区二区三区| 顶级少妇AAAAABBBBB片| 第四色播日韩AV第一页|