女人荫蒂被添全过程13种图片,亚洲+欧美+在线,欧洲精品无码一区二区三区 ,在厨房拨开内裤进入毛片

電子發(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ì)>AD7873輸入觸摸屏迪吉蒂澤Linux Driver

AD7873輸入觸摸屏迪吉蒂澤Linux Driver

2021-04-21 | pdf | 139.92KB | 次下載 | 2積分

資料介紹

This version (11 Feb 2016 21:10) was approved by Lars-Peter Clausen.The Previously approved version (05 Sep 2012 14:12) is available.Diff

AD7873 Input Touch Screen Digitizer Linux Driver

Supported Devices

Description

The AD7843/AD7873 is a 12-bit successive-approximation ADC with a synchronous serial interface and low on resistance switches for driving touch screens. The parts operates from a single 2.2 V to 5.25 V power supply and features throughput rates greater than 125 kSPS. The external reference applied to the AD7843 can be varied from 1 V to +VCC, while the analog input range is from 0 V to VREF. The device includes a shutdown mode that reduces the current consumption to less than 1 μA.

The AD7873 is similar to the AD7843 but has added functionality such as an on-chip temperature sensor (-40°C to + 85°C), on-chip 2.5 V reference and direct battery and touch-pressure measurement.

See also: AD7877 Touchscreen Device Driver See also: AD7879 Touchscreen Device Driver

Configuration

Software configurable features

Source Code

Status

Source Mainlined?
git Yes

Files

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.

21 Oct 2010 16:10

Touchscreen characteristics vary between boards and models. The platform_data for the device's “struct device” holds this information.

These snippets are all from the same file. arch/blackfin/mach-bf537/boards/stamp.c:

#if defined(CONFIG_TOUCHSCREEN_ADS7846) || defined(CONFIG_TOUCHSCREEN_ADS7846_MODULE)
#include 
static struct bfin5xx_spi_chip ad7873_spi_chip_info = {
	.bits_per_word	= 8,
};
?
static int ads7873_get_pendown_state(void)
{
	return gpio_get_value(GPIO_PF6);
}
?
static struct ads7846_platform_data __initdata ad7873_pdata = {
	.model		= 7873,		/* AD7873 */
	.x_max		= 0xfff,
	.y_max		= 0xfff,
	.x_plate_ohms	= 620,
	.debounce_max	= 1,
	.debounce_rep	= 0,
	.debounce_tol	= (~0),
	.get_pendown_state = ads7873_get_pendown_state,
};
#endif

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
static struct spi_board_info bfin_spi_board_info[] __initdata = {
#if defined(CONFIG_TOUCHSCREEN_ADS7846) || defined(CONFIG_TOUCHSCREEN_ADS7846_MODULE)
	{
		.modalias = "ads7846",
		.max_speed_hz = 2000000,     /* max spi clock (SCK) speed in HZ */
		.bus_num = 0,
		.irq = IRQ_PF6,
		.chip_select = GPIO_PF10 + MAX_CTRL_CS,	/* GPIO controlled SSEL */
		.controller_data = &ad7873_spi_chip_info, /* needed only on Blackfin */
		.platform_data = &ad7873_pdata,
		.mode = SPI_MODE_0,
	},
#endif
};

Adding Linux driver support

Configure kernel with “make menuconfig” (alternatively use “make xconfig” or “make qconfig”)

The AD7873 Driver depends on CONFIG_SPI

Input device support
  -*- Generic input layer (needed for keyboard, mouse, ...)
  < >   Support for memoryless force-feedback devices
  < >   Polled input device skeleton
  < >   Sparse keymap support library
        *** Userland interfaces ***
  < >   Mouse interface
  < >   Joystick interface
  <*>   Event interface
  < >   Event debugging
        *** Input Device Drivers ***
  [ ]   Keyboards  --->
  [ ]   Mice  --->
  [ ]   Joysticks/Gamepads  --->
  [ ]   Tablets  --->
  [*]   Touchscreens  --->
 
 	 --- Touchscreens
 	 <*>   ADS7846/TSC2046/AD7873 and AD(S)7843 based touchscreens (NEW)
 	 < >   AD7877 based touchscreens
 	 < >   Analog Devices AD7879-1/AD7889-1 touchscreen interface (NEW)
 
  [ ]   Miscellaneous devices  --->
      Hardware I/O ports  --->

Hardware configuration

Driver testing

Driver compiled as a module

root:~> modprobe evdev
root:~> modprobe ads7846
ads7846 spi0.18: touchscreen, irq 56
input: ADS7873 Touchscreen as /devices/platform/bfin-spi.0/spi0.18/input/input0

Driver compiled into the kernel

Your kernel startup messages should include something like this

ads7846 spi0.18: touchscreen, irq 56
input: ADS7873 Touchscreen as /devices/platform/bfin-spi.0/spi0.18/input/input0

Checking for proper installation

After the kernel boot your device folder should include at least one device node for the touchscreen

root:/> ls -al /dev/input/
drw-r--r--    2 root     root            0 Jan  1 00:03 .
drwxr-xr-x    5 root     root            0 Jan  1 00:03 ..
crw-rw-r--    1 root     root      13,  64 Jan  1 00:03 event0
root:/>

Check that the interrupt is registered.

root:~> cat /proc/interrupts | grep ads7846
56:         16      GPIO  ads7846

root:~> cat /sys/class/input/input0/name
ADS7873 Touchscreen

Use the event_test utility to test proper function

root:/> event_test /dev/input/event0                                                                           
Input driver version is 1.0.0                                                                                  
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0                                                    
Input device name: "ADS7873 Touchscreen"                                                                       
Supported events:                                                                                              
  Event type 0 (Reset)                                                                                         
    Event code 0 (Reset)                                                                                       
    Event code 1 (Key)                                                                                         
    Event code 3 (Absolute)                                                                                    
  Event type 1 (Key)                                                                                           
  Event type 3 (Absolute)                                                                                      
    Event code 0 (X)                                                                                           
      Value    760                                                                                             
      Min        0                                                                                             
      Max     4095                                                                                             
    Event code 1 (Y)                                                                                           
      Value   1973                                                                                             
      Min        0                                                                                             
      Max     4095                                                                                             
    Event code 24 (Pressure)                                                                                   
      Value      0                                                                                             
      Min        0                                                                                             
      Max        0                                                                                             
Testing ... (interrupt to exit)                                                                                
Event: time 258292.823196, type 1 (Key), code 330 (Touch), value 1
Event: time 258292.823209, type 3 (Absolute), code 0 (X), value 776
Event: time 258292.823214, type 3 (Absolute), code 1 (Y), value 505
Event: time 258292.823220, type 3 (Absolute), code 24 (Pressure), value 491
Event: time 258292.823225, type 0 (Reset), code 0 (Reset), value 0
Event: time 258292.828643, type 3 (Absolute), code 0 (X), value 789
Event: time 258292.828653, type 3 (Absolute), code 1 (Y), value 489
Event: time 258292.828659, type 3 (Absolute), code 24 (Pressure), value 485
Event: time 258292.828664, type 0 (Reset), code 0 (Reset), value 0
Event: time 258292.834085, type 3 (Absolute), code 0 (X), value 790
Event: time 258292.834095, type 3 (Absolute), code 1 (Y), value 499
Event: time 258292.834101, type 3 (Absolute), code 24 (Pressure), value 482
Event: time 258292.834106, type 0 (Reset), code 0 (Reset), value 0
Event: time 258292.839527, type 3 (Absolute), code 0 (X), value 789
Event: time 258292.839538, type 3 (Absolute), code 1 (Y), value 502
Event: time 258292.839544, type 3 (Absolute), code 24 (Pressure), value 481
Event: time 258292.839549, type 0 (Reset), code 0 (Reset), value 0

In case you touch the surface and don't receive events, it's likely that something with your /PENIRQ Interrupt is wrong.
check irq number in your platform device file

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美的電磁爐維修手冊(cè)大全
  10. 1.56 MB   |  24次下載  |  5 積分
  11. 6如何正確測(cè)試電源的紋波
  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 積分
主站蜘蛛池模板: 苍溪县| 木里| 灵寿县| 田东县| 浦城县| 铁力市| 和田市| 溧水县| 延庆县| 海阳市| 博爱县| 盈江县| 登封市| 松桃| 大理市| 阳谷县| 高密市| 木兰县| 临夏县| 泰兴市| 北京市| 祁门县| 治县。| 左贡县| 都匀市| 丰台区| 且末县| 玉环县| 祁门县| 安龙县| 南华县| 盐亭县| 定边县| 灵山县| 襄樊市| 沂南县| 汝阳县| 新竹县| 衡阳市| 金华市| 宁河县|