I (reference) in projects: linux-4.1.27

Searched refs:I (Results 1 – 200 of 988) sorted by relevance

/linux-4.1.27/arch/powerpc/perf/
D	hv-gpci-requests.h	`50 #include I(REQUEST_BEGIN) 66 #include I(REQUEST_END) 71 #include I(REQUEST_BEGIN) 79 #include I(REQUEST_END) 88 #include I(REQUEST_BEGIN) 93 #include I(REQUEST_END) 98 #include I(REQUEST_BEGIN) 103 #include I(REQUEST_END) 108 #include I(REQUEST_BEGIN) 117 #include I(REQUEST_END) [all …]`
/linux-4.1.27/drivers/net/ethernet/qlogic/netxen/
D	netxen_nic_hdr.h	567 #define NETXEN_NIU_GB_MAC_CONFIG_0(I) \ argument 568 (NETXEN_CRB_NIU + 0x30000 + (I)0x10000) 569 #define NETXEN_NIU_GB_MAC_CONFIG_1(I) \ argument 570 (NETXEN_CRB_NIU + 0x30004 + (I)0x10000) 571 #define NETXEN_NIU_GB_MAC_IPG_IFG(I) \ argument 572 (NETXEN_CRB_NIU + 0x30008 + (I)0x10000) 573 #define NETXEN_NIU_GB_HALF_DUPLEX_CTRL(I) \ argument 574 (NETXEN_CRB_NIU + 0x3000c + (I)0x10000) 575 #define NETXEN_NIU_GB_MAX_FRAME_SIZE(I) \ argument 576 (NETXEN_CRB_NIU + 0x30010 + (I)*0x10000) [all …]
/linux-4.1.27/Documentation/block/
D	stat.txt	23 read I/Os requests number of read I/Os processed 24 read merges requests number of read I/Os merged with in-queue I/O 27 write I/Os requests number of write I/Os processed 28 write merges requests number of write I/Os merged with in-queue I/O 31 in_flight requests number of I/Os currently in flight 35 read I/Os, write I/Os 38 These values increment when an I/O request completes. 43 These values increment when an I/O request is merged with an 44 already-queued I/O request. 52 counters are incremented when the I/O completes. [all …]
D	data-integrity.txt	14 support for appending integrity metadata to an I/O. The integrity 18 for some protection schemes also that the I/O is written to the right 24 between adjacent nodes in the I/O path. The interesting thing about 26 is well defined and every node in the I/O path can verify the 27 integrity of the I/O and reject it if corruption is detected. This 70 match up for an I/O to complete. 82 to be pinned to I/Os and sent to/received from controllers that 105 that's attached to the I/O. 108 generate the protection information for any I/O. Eventually the 110 user data. Metadata and other I/O that originates within the kernel [all …]
D	request.txt	`23 I I/O scheduler member 38 void *elevator_private I I/O scheduler private data`
D	writeback_cache_control.txt	`9 write back caches. That means the devices signal I/O completion to the 25 has been flushed before the actual I/O operation is started. This explicitly 29 flush without any dependent I/O. It is recommend to use 37 filesystem and will make sure that I/O completion for this request is only`
/linux-4.1.27/include/linux/i2c/
D	adp8870.h	`86 #define ADP8870_BL_CUR_mA(I) ((I * 127) / 30) argument 91 #define ADP8870_L2_COMP_CURR_uA(I) ((I * 255) / 1106) argument 96 #define ADP8870_L3_COMP_CURR_uA(I) ((I * 255) / 551) argument 101 #define ADP8870_L4_COMP_CURR_uA(I) ((I * 255) / 275) argument 106 #define ADP8870_L5_COMP_CURR_uA(I) ((I * 255) / 138) argument`
D	adp8860.h	`89 #define ADP8860_BL_CUR_mA(I) ((I * 127) / 30) argument 94 #define ADP8860_L2_COMP_CURR_uA(I) ((I * 255) / 1106) argument 99 #define ADP8860_L3_COMP_CURR_uA(I) ((I * 255) / 138) argument`
/linux-4.1.27/crypto/
D	cast6_generic.c	`35 #define F1(D, r, m) ((I = ((m) + (D))), (I = rol32(I, (r))), \ 36 (((s1[I >> 24] ^ s2[(I>>16)&0xff]) - s3[(I>>8)&0xff]) + s4[I&0xff])) 37 #define F2(D, r, m) ((I = ((m) ^ (D))), (I = rol32(I, (r))), \ 38 (((s1[I >> 24] - s2[(I>>16)&0xff]) + s3[(I>>8)&0xff]) ^ s4[I&0xff])) 39 #define F3(D, r, m) ((I = ((m) - (D))), (I = rol32(I, (r))), \ 40 (((s1[I >> 24] + s2[(I>>16)&0xff]) ^ s3[(I>>8)&0xff]) - s4[I&0xff])) 103 u32 I; in W() local 167 u32 I; in Q() local 177 u32 I; in QBAR() local`
D	cast5_generic.c	303 #define F1(D, m, r) ((I = ((m) + (D))), (I = rol32(I, (r))), \ 304 (((s1[I >> 24] ^ s2[(I>>16)&0xff]) - s3[(I>>8)&0xff]) + s4[I&0xff])) 305 #define F2(D, m, r) ((I = ((m) ^ (D))), (I = rol32(I, (r))), \ 306 (((s1[I >> 24] - s2[(I>>16)&0xff]) + s3[(I>>8)&0xff]) ^ s4[I&0xff])) 307 #define F3(D, m, r) ((I = ((m) - (D))), (I = rol32(I, (r))), \ 308 (((s1[I >> 24] + s2[(I>>16)&0xff]) ^ s3[(I>>8)&0xff]) - s4[I&0xff])) 316 u32 I; /* used by the Fx macros */ in __cast5_encrypt() local 373 u32 I; in __cast5_decrypt() local
D	sha512_generic.c	`71 static inline void LOAD_OP(int I, u64 W, const u8 input) in LOAD_OP() argument 73 W[I] = get_unaligned_be64((__u64 )input + I); in LOAD_OP() 76 static inline void BLEND_OP(int I, u64 W) in BLEND_OP() argument 78 W[I & 15] += s1(W[(I-2) & 15]) + W[(I-7) & 15] + s0(W[(I-15) & 15]); in BLEND_OP()`
D	ansi_cprng.c	`51 unsigned char I[DEFAULT_BLK_SZ]; member 99 hexdump("Input I: ", ctx->I, DEFAULT_BLK_SZ); in _get_more_prng_bytes() 114 output = ctx->I; in _get_more_prng_bytes() 124 xor_vectors(ctx->I, ctx->V, tmp, DEFAULT_BLK_SZ); in _get_more_prng_bytes() 154 xor_vectors(ctx->rand_data, ctx->I, tmp, in _get_more_prng_bytes() 180 hexdump("Output I: ", ctx->I, DEFAULT_BLK_SZ); in _get_more_prng_bytes()`
D	sha256_generic.c	`45 static inline void LOAD_OP(int I, u32 W, const u8 input) in LOAD_OP() argument 47 W[I] = get_unaligned_be32((__u32 )input + I); in LOAD_OP() 50 static inline void BLEND_OP(int I, u32 W) in BLEND_OP() argument 52 W[I] = s1(W[I-2]) + W[I-7] + s0(W[I-15]) + W[I-16]; in BLEND_OP()`
/linux-4.1.27/drivers/media/tuners/
D	mt2060.c	`104 int I,J; in mt2060_spurcalc() local 107 for (I = 1; I < 10; I++) { in mt2060_spurcalc() 108 J = ((2Ilo1)/lo2+1)/2; in mt2060_spurcalc() 109 diff = I(int)lo1-J(int)lo2; in mt2060_spurcalc() 124 int I,J; in mt2060_spurcheck() local 125 I=0; in mt2060_spurcheck() 133 I=1000; in mt2060_spurcheck() 134 Sp1 = mt2060_spurcalc(lo1+I,lo2+I,if2); in mt2060_spurcheck() 135 Sp2 = mt2060_spurcalc(lo1-I,lo2-I,if2); in mt2060_spurcheck() 138 J=-J; I=-I; Spur=Sp2; in mt2060_spurcheck() [all …]`
/linux-4.1.27/Documentation/device-mapper/
D	dm-io.txt	4 Dm-io provides synchronous and asynchronous I/O services. There are three 5 types of I/O services available, and each type has a sync and an async 9 of the I/O. Each io_region indicates a block-device along with the starting 21 The first I/O service type takes a list of memory pages as the data buffer for 22 the I/O, along with an offset into the first page. 36 The second I/O service type takes an array of bio vectors as the data buffer 37 for the I/O. This service can be handy if the caller has a pre-assembled bio, 47 The third I/O service type takes a pointer to a vmalloc'd memory buffer as the 48 data buffer for the I/O. This service can be handy if the caller needs to do 49 I/O to a large region but doesn't want to allocate a large number of individual [all …]
D	cache-policies.txt	49 The sequential threshold indicates the number of contiguous I/Os 52 is the number of intervening non-contiguous I/Os that must be seen 57 Large, sequential I/Os are probably better left on the origin device 58 since spindles tend to have good sequential I/O bandwidth. The 59 io_tracker counts contiguous I/Os to try to spot when the I/O is in one 62 If sequential threshold is set to 0 the sequential I/O detection is 63 disabled and sequential I/O will no longer implicitly bypass the cache. 64 Setting the random threshold to 0 does _not_ disable the random I/O
D	dm-queue-length.txt	`5 which selects a path with the least number of in-flight I/Os. 9 <repeat_count>: The number of I/Os to dispatch using the selected 17 <in-flight>: The number of in-flight I/Os on the path. 23 dm-queue-length increments/decrements 'in-flight' when an I/O is`
D	dm-service-time.txt	`6 the incoming I/O. 9 of in-flight I/Os on a path with the performance value of the path. 16 <repeat_count>: The number of I/Os to dispatch using the selected 31 <in-flight-size>: The size of in-flight I/Os on the path. 39 dm-service-time adds the I/O size to 'in-flight-size' when the I/O is`
D	switch.txt	5 arbitrary mapping of fixed-size regions of I/O across a fixed set of 9 It maps I/O to underlying block devices efficiently when there is a large 27 stored on another member the I/O will be forwarded as required. This 37 robin algorithm to send I/O across all paths and let the storage array 50 Upper Tier - Determine which array member the I/O should be sent to. 61 a bitmap to look up the location of the I/O and choose the appropriate 62 lower tier device to route the I/O. By using a bitmap we are able to 74 The number of paths across which to distribute the I/O.
D	dm-flakey.txt	`30 unreliability, all I/O returns errors. 33 All write I/O is silently ignored. 34 Read I/O is handled correctly.`
D	statistics.txt	`4 Device Mapper supports the collection of I/O statistics on user-defined 13 The I/O statistics counters for each step-sized area of a region are 124 9. the number of I/Os currently in progress 125 10. the number of milliseconds spent doing I/Os 126 11. the weighted number of milliseconds spent doing I/Os`
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/engine/ce/fuc/
D	com.fuc	`146 iowr I[$r1 + 0x300] $r2 150 iowr I[$r1] $r2 156 iowr I[$r1] $r2 166 iord $r1 I[$r0 + 0x200] 178 iowr I[$r0 + 0x100] $r1 192 iord $r4 I[$r4 + 0] 201 iowrs I[$r15] $r5 220 iowrs I[$r15] $r14 245 iord $r3 I[$r2] 253 iowr I[$r2] $r3 [all …]`
/linux-4.1.27/Documentation/hwmon/
D	it87	7 Addresses scanned: from Super I/O config space (8 I/O ports) 11 Addresses scanned: from Super I/O config space (8 I/O ports) 15 Addresses scanned: from Super I/O config space (8 I/O ports) 19 Addresses scanned: from Super I/O config space (8 I/O ports) 23 Addresses scanned: from Super I/O config space (8 I/O ports) 27 Addresses scanned: from Super I/O config space (8 I/O ports) 31 Addresses scanned: from Super I/O config space (8 I/O ports) 35 Addresses scanned: from Super I/O config space (8 I/O ports) 39 Addresses scanned: from Super I/O config space (8 I/O ports) 43 Addresses scanned: from Super I/O config space (8 I/O ports) [all …]
D	w83627hf	7 Addresses scanned: ISA address retrieved from Super I/O registers 10 Addresses scanned: ISA address retrieved from Super I/O registers 13 Addresses scanned: ISA address retrieved from Super I/O registers 16 Addresses scanned: ISA address retrieved from Super I/O registers 19 Addresses scanned: ISA address retrieved from Super I/O registers 42 the Winbond W83627HF, W83627THF, W83697HF and W83637HF Super I/O chips. 47 Super I/O chip and a second i2c-only Winbond chip (often a W83782D), 51 If you really want i2c accesses for these Super I/O chips, 72 be used to force the base I/O address of the hardware monitoring block. 78 # Enter the Super I/O config space [all …]
D	f71882fg	7 Addresses scanned: none, address read from Super I/O config space 11 Addresses scanned: none, address read from Super I/O config space 15 Addresses scanned: none, address read from Super I/O config space 19 Addresses scanned: none, address read from Super I/O config space 23 Addresses scanned: none, address read from Super I/O config space 27 Addresses scanned: none, address read from Super I/O config space 31 Addresses scanned: none, address read from Super I/O config space 35 Addresses scanned: none, address read from Super I/O config space 39 Addresses scanned: none, address read from Super I/O config space 43 Addresses scanned: none, address read from Super I/O config space [all …]
D	w83627ehf	7 Addresses scanned: ISA address retrieved from Super I/O registers 11 Addresses scanned: ISA address retrieved from Super I/O registers 15 Addresses scanned: ISA address retrieved from Super I/O registers 19 Addresses scanned: ISA address retrieved from Super I/O registers 23 Addresses scanned: ISA address retrieved from Super I/O registers 27 Addresses scanned: ISA address retrieved from Super I/O registers 29 * Nuvoton NCT6775F/W83667HG-I 31 Addresses scanned: ISA address retrieved from Super I/O registers 35 Addresses scanned: ISA address retrieved from Super I/O registers 49 W83627DHG, W83627DHG-P, W83627UHG, W83667HG, W83667HG-B, W83667HG-I [all …]
D	smsc47m1	`7 Addresses scanned: none, address read from Super I/O config space 15 Addresses scanned: none, address read from Super I/O config space 19 Addresses scanned: none, address read from Super I/O config space 33 The Standard Microsystems Corporation (SMSC) 47M1xx Super I/O chips`
D	nct6775	13 Addresses scanned: ISA address retrieved from Super I/O registers 15 * Nuvoton NCT5572D/NCT6771F/NCT6772F/NCT6775F/W83677HG-I 17 Addresses scanned: ISA address retrieved from Super I/O registers 21 Addresses scanned: ISA address retrieved from Super I/O registers 25 Addresses scanned: ISA address retrieved from Super I/O registers 29 Addresses scanned: ISA address retrieved from Super I/O registers 33 Addresses scanned: ISA address retrieved from Super I/O registers 43 and compatible super I/O chips.
D	pc87427	`7 Addresses scanned: none, address read from Super I/O config space 19 The National Semiconductor Super I/O chip includes complete hardware 57 not. I couldn't find a way to figure out the external sensor data`
D	sch5627	`7 Addresses scanned: none, address read from Super I/O config space 16 SMSC SCH5627 Super I/O chips include complete hardware monitoring`
D	ds620	`26 PO is always low. If .pomode == 1, the thermostat is in PO_LOW mode. I.e., the 30 Likewise, with .pomode == 2, the thermostat is in PO_HIGH mode. I.e., the PO`
D	sch5636	`7 Addresses scanned: none, address read from Super I/O config space 15 SMSC SCH5636 Super I/O chips include an embedded microcontroller for`
D	f71805f	`7 Addresses scanned: none, address read from Super I/O config space 11 Addresses scanned: none, address read from Super I/O config space 15 Addresses scanned: none, address read from Super I/O config space 34 The Fintek F71805F/FG Super I/O chip includes complete hardware monitoring 41 The Fintek F71872F/FG Super I/O chip is almost the same, with two 45 The Fintek F71806F/FG Super-I/O chip is essentially the same as the`
D	w83781d	7 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports) 11 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports) 217 > What formulas do I use to program a new R-T table for a given Beta? 229 > How do I program them for diode inputs? I can't find any register 254 I reworded some parts and added personal comments. 269 very badly chosen IMHO), I don't know what DVC could stand for. Maybe 287 Remark: I noticed that on Intel boards sensor 2 is used for the CPU 401 I've been fiddling around with the (in)famous 0x59 register and 409 0x82 - slightly "on-ner" than off, but my fans do not get to move. I can 418 My mobo is an ASUS A7V266-E. This behavior is similar to what I got [all …]
/linux-4.1.27/drivers/input/joystick/iforce/
D	Kconfig	`2 # I-Force driver configuration 5 tristate "I-Force devices" 8 Say Y here if you have an I-Force joystick or steering wheel 16 bool "I-Force USB joysticks and wheels" 19 Say Y here if you have an I-Force joystick or steering wheel 23 bool "I-Force Serial joysticks and wheels" 26 Say Y here if you have an I-Force joystick or steering wheel`
/linux-4.1.27/Documentation/s390/
D	cds.txt	4 Device Driver I/O Support Routines 15 I/O access method. This gives relief to the device drivers as they don't 18 I/O (PIO), and other hardware features more. However, this implies that 19 either every single device driver needs to implement the hardware I/O 28 In order to build common device support for ESA/390 I/O interfaces, a 29 functional layer was introduced that provides generic I/O access methods to 32 The common device support layer comprises the I/O support routines defined 64 initiate an I/O request. 70 terminate the current I/O request processed on the device. 74 routine whenever an I/O interrupt is presented to the system. The do_IRQ() [all …]
D	CommonIO	`1 S/390 common I/O-Layer - command line parameters, procfs and debugfs entries 15 The given devices will be ignored by the common I/O-layer; no detection 30 operator). The '!' operator will cause the I/O-layer to _not_ ignore a device. 49 Lists the ranges of devices (by bus id) which are ignored by common I/O. 115 Various debug messages from the common I/O-layer. 118 Logs the calling of functions in the common I/O-layer and, if applicable,`
D	00-INDEX	`8 - s390 common device support (common I/O layer). 10 - common I/O layer command line parameters, procfs and debugfs entries`
/linux-4.1.27/Documentation/isdn/
D	syncPPP.FAQ	7 Q04: MPPP?? What's that and how can I use it ... 8 Q05: I tried MPPP but it doesn't work 9 Q06: can I use asynchronous PPP encapsulation with network devices 11 Q08: I wanna talk to several machines, which need different configs 12 Q09: Starting the ipppd, I get only error messages from i4l 13 Q10: I wanna use dynamic IP address assignment 14 Q11: I can't connect. How can I check where the problem is. 15 Q12: How can I reduce login delay? 20 what should I use? 47 Q02: when I start the ipppd .. I only get the [all …]
/linux-4.1.27/Documentation/video4linux/bttv/
D	Tuners	`20 C= I+DK 23 M= BG+I+DK 25 Q= BG+I+DK+LL 54 1246: PAL I 58 ME: BG DK I LL (Multi Europe) 59 MP: BG DK I (Multi PAL) 75 xx6x: PAL I 87 TAPC-I701 : PAL I (TAPC-I001 w/FM) (P,170/450) 91 TAPC-W701P: PAL I (TAPC-W001P w/FM) (L,170/450) 93 TAPC-Q704P: PAL D/K+I (L,170/450) [all …]`
D	README.WINVIEW	`7 infra-red remote control decoded on the board, I will add support for this 8 when I get time (it simple generates an interrupt for each key press, with 11 I don't yet have any application to test the radio support. The tuner 24 on their server are the full data-sheets, but don't ask how I found it. 26 To use the driver I use the following options, the tuner and pll settings might`
D	README.freeze	`34 I've seen reports that bttv 0.7.x crashes whereas 0.8.x works rock solid 36 0.7.x. I have no idea where exactly, it works stable for me and a lot of 50 althrought I'm not sure whenever this really fixes the problems or 71 VGA cards seems to cause trouble sometimes. I've also seen funny`
/linux-4.1.27/block/
D	Kconfig.iosched	`9 The no-op I/O scheduler is a minimal scheduler that does basic merging 16 tristate "Deadline I/O scheduler" 19 The deadline I/O scheduler is simple and compact. It will provide 25 tristate "CFQ I/O scheduler" 28 The CFQ I/O scheduler tries to distribute bandwidth equally 33 This is the default I/O scheduler. 43 prompt "Default I/O scheduler" 46 Select the I/O scheduler which will be used by default for all`
/linux-4.1.27/Documentation/filesystems/nfs/
D	nfs41-server.txt	39 I Implemented NFSv4.1 operations. 51 I \| BACKCHANNEL_CTL \| REQ \| \| Section 18.33 \| 52 I \| BIND_CONN_TO_SESSION \| REQ \| \| Section 18.34 \| 56 I \| CREATE_SESSION \| REQ \| \| Section 18.36 \| 61 I \| DESTROY_CLIENTID \| REQ \| \| Section 18.50 \| 62 I \| DESTROY_SESSION \| REQ \| \| Section 18.37 \| 63 I \| EXCHANGE_ID \| REQ \| \| Section 18.35 \| 64 I \| FREE_STATEID \| REQ \| \| Section 18.38 \| 66 I \| GETDEVICEINFO \| OPT \| pNFS (REQ) \| Section 18.40 \| 70 I \| LAYOUTCOMMIT \| OPT \| pNFS (REQ) \| Section 18.42 \| [all …]
/linux-4.1.27/arch/mips/ralink/
D	Platform	`5 cflags-$(CONFIG_RALINK) += -I$(srctree)/arch/mips/include/asm/mach-ralink 11 cflags-$(CONFIG_SOC_RT288X) += -I$(srctree)/arch/mips/include/asm/mach-ralink/rt288x 17 cflags-$(CONFIG_SOC_RT305X) += -I$(srctree)/arch/mips/include/asm/mach-ralink/rt305x 23 cflags-$(CONFIG_SOC_RT3883) += -I$(srctree)/arch/mips/include/asm/mach-ralink/rt3883 29 cflags-$(CONFIG_SOC_MT7620) += -I$(srctree)/arch/mips/include/asm/mach-ralink/mt7620`
/linux-4.1.27/Documentation/serial/
D	rocket.txt	26 The RocketPort ISA board requires I/O ports to be configured by the DIP 30 You pass the I/O port to the driver using the following module parameters: 32 board1 : I/O port for the first ISA board 33 board2 : I/O port for the second ISA board 34 board3 : I/O port for the third ISA board 35 board4 : I/O port for the fourth ISA board 87 You must assign and configure the I/O addresses used by the ISA Rocketport 92 SETTING THE I/O ADDRESS 96 a range of I/O addresses for it to use. The first RocketPort card 97 requires a 68-byte contiguous block of I/O addresses, starting at one [all …]
/linux-4.1.27/arch/x86/crypto/sha-mb/
D	sha1_x8_avx2.S	`328 I=0 341 vmovdqu T0, (I8)32(%rsp) 343 vmovdqu T1, (I8+1)32(%rsp) 345 vmovdqu T2, (I8+2)32(%rsp) 347 vmovdqu T3, (I8+3)32(%rsp) 349 vmovdqu T4, (I8+4)32(%rsp) 351 vmovdqu T5, (I8+5)32(%rsp) 353 vmovdqu T6, (I8+6)32(%rsp) 355 vmovdqu T7, (I8+7)32(%rsp) 357 I = (I+1) define [all …]`
D	sha1_mb_mgr_flush_avx2.S	`161 I = 0 define 163 offset = (_ldata + I * _LANE_DATA_size + _job_in_lane) 166 JNE_SKIP %I 167 offset = (_args + _data_ptr + 8I) 169 offset = (_lens + 4I) 171 LABEL skip_ %I 172 I = (I+1) define`
/linux-4.1.27/Documentation/video4linux/
D	CARDLIST.usbvision	18 17 -> Hauppauge WinTV USB (PAL I) [0573:4d02] 23 22 -> Hauppauge WinTV USB (PAL I FM) [0573:4d12] 27 26 -> Hauppauge WinTV USB Pro (PAL/SECAM B/G/I/D/K/L) [0573:4d2c] 30 29 -> Hauppauge WinTV USB Pro (PAL I) [0573:4d22] 33 32 -> Hauppauge WinTV USB Pro (PAL/SECAM BGDK/I/L) [0573:4d25] 34 33 -> Hauppauge WinTV USB Pro (PAL/SECAM BGDK/I/L) V2 [0573:4d26] 37 36 -> Hauppauge WinTV USB Pro (PAL I,D/K) [0573:4d29] 40 39 -> Hauppauge WinTV USB Pro (PAL I FM) [0573:4d32] 42 41 -> Hauppauge WinTV USB Pro (Temic PAL/SECAM B/G/I/D/K/L FM) [0573:4d35] 44 43 -> Hauppauge WinTV USB Pro (PAL/SECAM B/G/I/D/K/L FM) [0573:4d37] [all …]
D	radiotrack.txt	`13 vary... I make no guarantees, claims or warranties to the suitability or 21 I have a RadioTrack card from back when I ran an MS-Windows platform. After 22 converting to Linux, I found Gideon le Grange's command-line software for 25 value, I wanted to see if the tuner could be tuned beyond the usual FM radio 26 broadcast band, so I could pick up the audio carriers from North American 28 I did not get much success, but I learned about programming ioports under`
D	README.ir	`10 remote controls. I suggest to download my input layer tools 21 was very confusing and I decided to basically start over from scratch. 56 XFree86 likely can be configured to recognise the remote keys. Once I 64 I know next to nothing about that through.`
D	Zoran	9 2. How do I get this damn thing to work 10 3. What mainboard should I use (or why doesn't my card work) 145 The CCIR has defined different standards: A,B,D,E,F,G,D,H,I,K,K1,L,M,N,... 167 The CCIR - I uses the PAL colorsystem, and is used in Great Britain, Hong Kong, 187 But I did not defiantly find out what NTSC Comb is. 191 can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC N, NTSC 4.43 and SECAM 199 can handle: PAL B/G/D/H/I/N, PAL N, PAL M, NTSC M, NTSC 4.43 and SECAM 203 can handle: PAL B/D/G/H/I, NTSC M 207 can handle: PAL B/G/H/I, PAL N, PAL M, NTSC M, NTSC 44, PAL 60, SECAM,NTSC Comb 211 can handle: NTSC-M/N/44, PAL-M/N/B/G/H/I/D/K/L and SECAM [all …]
D	CARDLIST.ivtv	`13 13 -> I/O Data GV-MVP/RX [10fc:d01e,10fc:d038,10fc:d039] 14 14 -> I/O Data GV-MVP/RX2E [10fc:d025]`
/linux-4.1.27/Documentation/powerpc/
D	mpc52xx.txt	`33 is not supported, and I'm not sure anyone is interesting in working on it 34 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have 35 nothing to do with the MPC5200. I also included the 'MPC' for the same 37 - Of course, I inspired myself from the 2.4 port. If you think I forgot to 38 mention you/your company in the copyright of some code, I'll correct it`
/linux-4.1.27/arch/arm/mm/
D	proc-arm926.S	83 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 86 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 110 mcr p15, 0, r2, c1, c0, 0 @ Disable I cache 123 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 152 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 174 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 177 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 181 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 184 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 219 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry [all …]
D	proc-mohawk.S	75 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 77 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 105 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 129 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 152 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 155 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 191 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 215 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 331 mcr p15, 0, ip, c7, c5, 0 @ invalidate I cache 335 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs [all …]
D	proc-arm925.S	123 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 126 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 145 mcr p15, 0, r2, c1, c0, 0 @ Disable I cache 157 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 189 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 211 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 214 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 218 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 221 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 256 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry [all …]
D	proc-arm920.S	91 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 94 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 122 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 152 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 174 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 208 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 232 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 365 mcr p15, 0, ip, c7, c5, 0 @ invalidate I cache 368 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 402 mcr p15, 0, ip, c8, c7, 0 @ invalidate I+D TLBs [all …]
D	cache-v4wt.S	`51 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 73 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 94 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 125 1: mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 143 mcr p15, 0, r2, c7, c5, 0 @ invalidate I cache`
D	proc-arm922.S	93 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 96 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 124 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 154 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 176 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 210 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 234 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 369 mcr p15, 0, ip, c7, c5, 0 @ invalidate I cache 372 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 394 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 [all …]
D	proc-arm946.S	61 mcr p15, 0, ip, c7, c5, 0 @ flush I cache 87 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 118 mcrne p15, 0, ip, c7, c5, 0 @ flush I cache 142 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 145 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 149 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 152 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 188 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 213 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 332 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache [all …]
D	proc-arm1020e.S	99 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 102 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 132 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 166 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 195 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 230 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 402 mcr p15, 0, r1, c7, c5, 0 @ invalidate I cache 406 mcr p15, 0, r1, c8, c7, 0 @ invalidate I & D TLBs 429 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 432 mcr p15, 0, r0, c8, c7 @ invalidate I,D TLBs on v4
D	proc-arm1026.S	90 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 93 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 123 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 151 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 180 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 215 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 375 mcr p15, 0, r1, c7, c5, 0 @ invalidate I cache 379 mcr p15, 0, r1, c8, c7, 0 @ invalidate I & D TLBs 402 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 405 mcr p15, 0, r0, c8, c7 @ invalidate I,D TLBs on v4
D	proc-arm1022.S	90 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 93 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 123 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 156 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 185 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 221 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 386 mcr p15, 0, r1, c7, c5, 0 @ invalidate I cache 390 mcr p15, 0, r1, c8, c7, 0 @ invalidate I & D TLBs 413 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 416 mcr p15, 0, r0, c8, c7 @ invalidate I,D TLBs on v4
D	proc-xscale.S	149 mcr p15, 0, r1, c10, c4, 1 @ unlock I-TLB 150 mcr p15, 0, r1, c8, c5, 0 @ invalidate I-TLB 158 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches & BTB 162 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 193 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 217 mcrne p15, 0, ip, c7, c5, 0 @ Invalidate I cache & BTB 239 mcrne p15, 0, r0, c7, c5, 1 @ Invalidate I cache line 270 mcr p15, 0, r0, c7, c5, 0 @ Invalidate I cache & BTB 287 mcr p15, 0, r0, c7, c5, 1 @ Invalidate I cache entry 313 mcr p15, 0, r0, c7, c5, 0 @ Invalidate I cache & BTB [all …]
D	proc-feroceon.S	104 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 107 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 136 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 170 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 191 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 194 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I entry 230 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 255 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 269 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 488 mcreq p15, 0, ip, c7, c5, 0 @ invalidate I cache [all …]
D	cache-v6.S	`43 mcr p15, 0, r0, c7, c5, 0 @ invalidate entire I-cache 44 mcr p15, 0, r0, c7, c5, 0 @ invalidate entire I-cache 45 mcr p15, 0, r0, c7, c5, 0 @ invalidate entire I-cache 46 mcr p15, 0, r0, c7, c5, 0 @ invalidate entire I-cache 52 mcr p15, 0, r0, c7, c5, 0 @ invalidate I-cache 69 mcr p15, 0, r0, c7, c5, 0 @ I+BTB cache invalidate 146 mcr p15, 0, r0, c7, c5, 0 @ I+BTB cache invalidate`
D	proc-sa1100.S	`76 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 79 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 152 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 188 mcr p15, 0, ip, c8, c7, 0 @ flush I+D TLBs 189 mcr p15, 0, ip, c7, c7, 0 @ flush I&D cache 204 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 207 mcr p15, 0, r0, c8, c7 @ invalidate I,D TLBs on v4`
D	proc-arm1020.S	99 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 102 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 132 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 167 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 198 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 236 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 418 mcr p15, 0, r1, c7, c5, 0 @ invalidate I cache 422 mcr p15, 0, r1, c8, c7, 0 @ invalidate I & D TLBs 447 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 450 mcr p15, 0, r0, c8, c7 @ invalidate I,D TLBs on v4
D	proc-xsc3.S	121 mcr p15, 0, ip, c8, c7, 0 @ invalidate I and D TLBs 152 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 176 mcrne p15, 0, ip, c7, c5, 0 @ invalidate L1 I cache and BTB 199 mcrne p15, 0, r0, c7, c5, 1 @ invalidate L1 I line 232 mcr p15, 0, r0, c7, c5, 0 @ invalidate L1 I cache and BTB 253 mcr p15, 0, r0, c7, c5, 0 @ invalidate L1 I cache and BTB 365 mcr p15, 0, ip, c7, c5, 0 @ invalidate L1 I cache and BTB 370 mcr p15, 0, ip, c8, c7, 0 @ invalidate I and D TLBs 433 mcr p15, 0, ip, c7, c7, 0 @ invalidate I & D caches, BTB 436 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs [all …]
D	proc-sa110.S	`68 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 71 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 141 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 165 mcr p15, 0, r10, c7, c7 @ invalidate I,D caches on v4 168 mcr p15, 0, r10, c8, c7 @ invalidate I,D TLBs on v4`
D	proc-fa526.S	`63 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 66 mcr p15, 0, ip, c8, c7, 0 @ invalidate I & D TLBs 113 mcr p15, 0, ip, c7, c5, 0 @ invalidate I cache 142 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 145 mcr p15, 0, r0, c8, c7 @ invalidate I,D TLBs on v4`
D	cache-fa.S	`48 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 71 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 94 mcrne p15, 0, r0, c7, c5, 1 @ invalidate I line 131 mcr p15, 0, r0, c7, c5, 1 @ invalidate I entry 157 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache`
D	cache-v4wb.S	`61 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 80 mcr p15, 0, ip, c7, c5, 0 @ invalidate I cache 114 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 172 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache`
D	proc-arm940.S	`54 mcr p15, 0, ip, c7, c5, 0 @ flush I cache 80 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 123 mcrne p15, 0, ip, c7, c5, 0 @ invalidate I cache 171 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 279 mcr p15, 0, r0, c7, c5, 0 @ invalidate I cache 327 orr r0, r0, #0x00001000 @ I-cache`
D	tlb-v4wb.S	`41 mcrne p15, 0, r3, c8, c5, 0 @ invalidate I TLB 64 mcr p15, 0, r3, c8, c5, 0 @ invalidate I TLB`
D	tlb-v4wbi.S	`43 mcrne p15, 0, r0, c8, c5, 1 @ invalidate I TLB entry 55 1: mcr p15, 0, r0, c8, c5, 1 @ invalidate I TLB entry`
D	cache-v7.S	`77 ALT_SMP(mcr p15, 0, r0, c7, c1, 0) @ invalidate I-cache inner shareable 78 ALT_UP(mcr p15, 0, r0, c7, c5, 0) @ I+BTB cache invalidate 190 ALT_SMP(mcr p15, 0, r0, c7, c1, 0) @ invalidate I-cache inner shareable 191 ALT_UP(mcr p15, 0, r0, c7, c5, 0) @ I+BTB cache invalidate 208 ALT_SMP(mcr p15, 0, r0, c7, c1, 0) @ invalidate I-cache inner shareable 209 ALT_UP(mcr p15, 0, r0, c7, c5, 0) @ I+BTB cache invalidate 290 USER( mcr p15, 0, r12, c7, c5, 1 ) @ invalidate I line`
D	tlb-v6.S	`51 mcrne p15, 0, r0, c8, c5, 1 @ TLB invalidate I MVA (was 1) 79 mcr p15, 0, r0, c8, c5, 1 @ TLB invalidate I MVA`
/linux-4.1.27/Documentation/usb/
D	acm.txt	35 Many modems do, here is a list of those I know of: 45 I know of one ISDN TA that does work with the acm driver: 49 Some cell phones also connect via USB. I know the following phones work: 77 I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub 78 E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms 86 I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=acm 87 E: Ad=85(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms 89 E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=128ms 91 I: If#= 0 Alt= 0 #EPs= 1 Cls=02(comm.) Sub=02 Prot=01 Driver=acm 92 E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=128ms [all …]
D	rio.txt	17 Before I explain how to use this to access the Rio500 please be warned: 19 W A R N I N G: 27 I suggest when the batteries are low and you want to transfer stuff that you 28 replace it with a fresh one. In my case, what happened is I lost two 16kb 29 blocks (they are no longer usable to store information to it). But I don't 33 In an extreme case, I left my Rio playing overnight and the batteries wore 60 re-written and Pete Ikusz along with the rest will re-design it. I would 91 I/O ports at ....
D	mtouchusb.txt	`39 download, I persist in updating this driver since I would like to use the 40 touchscreen for embedded apps using QTEmbedded, DirectFB, etc. So I feel the 64 I am not a MicroTouch/3M employee, nor have I ever been. 3M does not support`
D	iuu_phoenix.txt	`13 occur and your system may freeze. As far I now, 14 I never had any problem with it, but I'm not a real 63 So I have added this option to permit him to see a lot of color ( each activity change the color 73 work. ( This will not change anything ).Later I will perhaps`
D	proc_usb_info.txt	86 I made it ASCII instead of binary on purpose, so that someone 102 I = Interface descriptor info. 231 I:* If#=dd Alt=dd #EPs=dd Cls=xx(sssss) Sub=xx Prot=xx Driver=ssss 259 \| \|__EndpointAddress(I=In,O=Out) 314 I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub 315 E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms 321 I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub 322 E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms 328 I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=mouse 329 E: Ad=81(I) Atr=03(Int.) MxPS= 3 Ivl= 10ms [all …]
D	wusb-cbaf	`84 echo I: started host $(basename $dev) >&2 91 echo I: stopped host $(basename $dev) >&2 116 echo I: CC set >&2`
/linux-4.1.27/drivers/pinctrl/sunxi/
D	pinctrl-sun4i-a10.c	`897 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 0), 900 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 1), 903 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 2), 906 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 3), 910 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 4), 914 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 5), 918 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 6), 922 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 7), 926 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 8), 930 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 9), [all …]`
D	pinctrl-sun7i-a20.c	`917 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 0), 921 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 1), 925 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 2), 929 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 3), 934 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 4), 938 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 5), 942 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 6), 946 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 7), 950 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 8), 954 SUNXI_PIN(SUNXI_PINCTRL_PIN(I, 9), [all …]`
/linux-4.1.27/Documentation/ABI/testing/
D	procfs-diskstats	`5 The /proc/diskstats file displays the I/O statistics 19 12 - I/Os currently in progress 20 13 - time spent doing I/Os (ms) 21 14 - weighted time spent doing I/Os (ms)`
D	sysfs-block	5 The /sys/block/<disk>/stat files displays the I/O 15 9 - I/Os currently in progress 16 10 - time spent doing I/Os (ms) 17 11 - weighted time spent doing I/Os (ms) 26 I/O statistics of partition <part>. The format is the 118 minimum I/O size which is the smallest request the 124 workloads where a high number of I/O operations is 131 Storage devices may report an optimal I/O size, which is 132 the device's preferred unit for sustained I/O. This is 137 throughput is desired. If no optimal I/O size is [all …]
D	sysfs-bus-css	`23 Note: This is an I/O-subchannel specific attribute. 31 channel subsystem when last queried by the common I/O 34 Note: This is an I/O-subchannel specific attribute.`
/linux-4.1.27/Documentation/networking/
D	eql.txt	26 terminal server. I do not know if other terminal servers support load- 27 balancing, but I do know that the PortMaster does it, and does it 31 and 14.4 Kbps connection. However, I am not sure that it really is 32 the PortMaster, or if it's Linux's TCP drivers. I'm told that Linux's 36 I suggest to ISPs out there that it would probably be fair to charge 46 Here I describe the general steps of getting a kernel up and working 95 So far, I have only used the eql device with the DSLIP SLIP connection 98 managers is up to you. Most other connection managers that I've seen 138 I haven't found a good reason to write it yet... other than for 225 I have not yet done any load-balancing testing for PPP devices, mainly [all …]
D	arcnet-hardware.txt	12 some cabling tips, and a listing of all jumper settings I can find. Please 26 types, as far as I'm aware, are not compatible and so you cannot wire a 27 100 Mbps card to a 2.5 Mbps card, and so on. From what I hear, my driver does 28 work with 100 Mbps cards, but I haven't been able to verify this myself, 29 since I only have the 2.5 Mbps variety. It is probably not going to saturate 67 level of encapsulation is defined by RFC1201, which I call "packet 95 also work fine, because ARCnet is a very stable network. I personally use 75 130 (Avery's note: oops, I didn't know that. Mine (TV cable) works 256 - the I/O address: this is the "port" your ARCnet card is on. Probed 260 a doc I got from Novell, MS Windows prefers values of 0x300 or more, [all …]
D	de4x5.txt	60 line 5594 to reflect the I/O address you're using, or assign these when 95 I've changed the timing routines to use the kernel timer and scheduling 105 The SMC9332 card has a non-compliant SROM which needs fixing - I have 109 I have removed the buffer copies needed for receive on Intels. I cannot 114 I have added SROM decoding routines to make this driver work with any 117 the dc2104x chips should run correctly with the basic driver. I'm in 125 I have added a temporary fix for interrupt problems when some SCSI cards 138 Finally, I think I have really fixed the module loading problem with 139 more than one DECchip based card. As a side effect, I don't mess with 150 duplex links except through autonegotiation. When I include the [all …]
D	arcnet.txt	12 Hmm, I think I'm allowed to call that a poem, even though it's only two 13 lines. Hey, I'm in Computer Science, not English. Give me a break. 15 The point is: I REALLY REALLY REALLY REALLY REALLY want to hear from you if 31 If you don't e-mail me about your success/failure soon, I may be forced to 34 (You know, it might be argued that I'm pushing this point a little too much. 52 #ifdefs! I've changed this file a bit, but kept it in the first person from 53 Avery, because I didn't want to completely rewrite it. 62 Where do I discuss these drivers? 141 sensible method of autoprobing for these cards. You must specify the I/O 169 4. ARCnet RIM I cards. [all …]
D	netdev-FAQ.txt	85 Q: How do I indicate which tree (net vs. net-next) my patch should be in? 97 Q: I sent a patch and I'm wondering what happened to it. How can I tell 107 Q: The above only says "Under Review". How can I find out more? 114 Q: How can I tell what patches are queued up for backporting to the 137 Q: I see a network patch and I think it should be backported to stable. 138 Should I request it via "stable@vger.kernel.org" like the references in 155 Q: I have created a network patch and I think it should be backported to 156 stable. Should I add a "Cc: stable@vger.kernel.org" like the references 187 Q: I am working in existing code that has the former comment style and not the 188 latter. Should I submit new code in the former style or the latter? [all …]
D	tlan.txt	`12 I. Supported Devices. 35 I am not sure if 100BaseTX daughterboards (for those cards which 36 support such things) will work. I haven't had any solid evidence 43 but I do not expect any problems. 67 to force 100Mbs operation. (I'm not sure what will happen 109 section I, above.`
D	6pack.txt	46 3. Where can I get the latest version of 6pack for LinuX? 60 with PC/FlexNet. Please do not ask me about the internals of this file as I 61 don't know anything about it. I used a textual description of the 6pack 124 Although the driver has been tested on various platforms, I still declare it 146 or more subsequent packets. I have been told that this is due to a problem 147 with the serial driver of 2.0.3x kernels. I don't know yet if the problem 148 still exists with 2.1.x kernels, as I have heard that the serial driver 154 occur when there is a bare AX.25 connection still running. I don't know if 161 and at least at the moment I won't be able to do it because I do not have 166 I haven't modified or removed them yet -- sorry! The code itself needs
D	README.sb1000	59 to redefine the value of READ_DATA_PORT to match the I/O address used 68 of "pnpdump" to a file and editing this file to set the correct I/O ports, 72 errors and fix as necessary. (As an aside, I use I/O ports 0x110 and 130 interface. It looks like I'm connected but I can't even ping any 143 2.) I get "unresolved symbol" error messages on executing `insmod sb1000.o'. 153 option in the lines that allocate the two I/O addresses for the SB1000 card. 154 This first popped up on RH 6.0. Delete "(CHECK)" for the SB1000 I/O addresses. 158 4.) I can't execute the /etc/ppp/ppp@gi-on file. 167 6.) I'm getting tons of firewall deny messages in the /var/kern.log, 199 still supplied with his driver .tar.gz archive. I and all other sb1000 users
D	netlink_mmap.txt	1 This file documents how to use memory mapped I/O with netlink. 8 Memory mapped netlink I/O can be used to increase throughput and decrease 14 Memory mapped netlink I/O used two circular ring buffers for RX and TX which 18 user-space memory without copying them as done with regular socket I/O, 29 In order to use memory mapped netlink I/O, user-space needs three main changes: 51 On kernel side, in order to make use of memory mapped I/O on receive, the 52 originating netlink subsystem needs to support memory mapped I/O, otherwise 55 Dumps of kernel databases automatically support memory mapped I/O. 62 Structured and definitions for using memory mapped I/O are contained in 185 not support memory mapped I/O. Appropriate action is
D	s2io.txt	`1 Release notes for Neterion's (Formerly S2io) Xframe I/II PCI-X 10GbE driver. 14 This Linux driver supports Neterion's Xframe I PCI-X 1.0 and 27 eth3: Neterion Xframe I 10GbE adapter (rev 3), Version 2.0.9.1, Intr type INTA 31 The above messages identify the adapter type(Xframe I/II), adapter revision, 40 a. Jumbo frames. Xframe I/II supports MTU up to 9600 bytes,`
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/
D	par_io.txt	`1 * Parallel I/O Ports 3 This node configures Parallel I/O ports for CPUs with QE support. 5 device that using parallel I/O ports, a child node should be created. 12 - num-ports : number of Parallel I/O ports 26 the new device trees. Instead, each Par I/O bank should be represented`
/linux-4.1.27/include/linux/mfd/
D	adp5520.h	`242 #define ADP5520_BL_CUR_mA(I) ((I * 127) / 30) argument 247 #define ADP5520_L2_COMP_CURR_uA(I) ((I * 255) / 1000) argument 252 #define ADP5520_L3_COMP_CURR_uA(I) ((I * 255) / 127) argument`
/linux-4.1.27/arch/mips/lantiq/
D	Platform	`6 cflags-$(CONFIG_LANTIQ) += -I$(srctree)/arch/mips/include/asm/mach-lantiq 8 cflags-$(CONFIG_SOC_TYPE_XWAY) += -I$(srctree)/arch/mips/include/asm/mach-lantiq/xway 9 cflags-$(CONFIG_SOC_FALCON) += -I$(srctree)/arch/mips/include/asm/mach-lantiq/falcon`
/linux-4.1.27/Documentation/zh_CN/
D	volatile-considered-harmful.txt	62 volatile的存储类型最初是为那些内存映射的I/O寄存器而定义。在内核里，寄存器访问也应 63 该被锁保护，但是人们也不希望编译器“优化”临界区内的寄存器访问。内核里I/O的内存访问 64 是通过访问函数完成的；不赞成通过指针对I/O内存的直接访问，并且不是在所有体系架构上 79 - 在一些体系架构的系统上，允许直接的I/0内存访问，那么前面提到的访问函数可以使用 91 - 由于某些I/0设备可能会修改连续一致的内存,所以有时,指向连续一致内存的数据结构
D	io_ordering.txt	`25 在某些平台上，所谓的内存映射I/O是弱顺序。在这些平台上，驱动开发者有责任 26 保证I/O内存映射地址的写操作按程序图意的顺序达到设备。通常读取一个“安全” 30 屏障操作，mb()，不过仅适用于I/O）。`
/linux-4.1.27/Documentation/
D	io_ordering.txt	`1 On some platforms, so-called memory-mapped I/O is weakly ordered. On such 2 platforms, driver writers are responsible for ensuring that I/O writes to 4 typically done by reading a 'safe' device or bridge register, causing the I/O 8 subsequent writes to I/O space arrived only after all prior writes (much like a 9 memory barrier op, mb(), only with respect to I/O). 45 Here, the reads from safe_register will cause the I/O chipset to flush any`
D	iostats.txt	1 I/O statistics fields 50 go to zero as I/Os complete; all others only increase (unless they 66 as only one I/O. This field lets you know how often this was done. 81 Field 9 -- # of I/Os currently in progress 84 Field 10 -- # of milliseconds spent doing I/Os 86 Field 11 -- weighted # of milliseconds spent doing I/Os 87 This field is incremented at each I/O start, I/O completion, I/O 88 merge, or read of these stats by the number of I/Os in progress 89 (field 9) times the number of milliseconds spent doing I/O since the 91 I/O completion time and the backlog that may be accumulating. [all …]
D	sysrq.txt	9 * How do I enable the magic SysRq key? 41 * How do I use the magic SysRq key? 50 On SPARC - You press 'ALT-STOP-<command key>', I believe. 60 let me know so I can add them to this section. 132 * Okay, so what can I use them for? 160 umount(u) is basically useful in the same ways as sync(s). I generally sync(s), 177 * Sometimes SysRq seems to get 'stuck' after using it, what can I do? 179 That happens to me, also. I've found that tapping shift, alt, and control 184 * I hit SysRq, but nothing seems to happen, what's wrong? 194 * I want to add SysRQ key events to a module, how does it work? [all …]
D	vgaarbiter.txt	`5 Graphic devices are accessed through ranges in I/O or memory space. While most 24 I. Details and Theory of Operation 25 I.1 vgaarb 26 I.2 libpciaccess 27 I.3 xf86VGAArbiter (X server implementation) 32 I. Details and Theory of Operation 35 I.1 vgaarb 101 I.2 libpciaccess 167 I.3 xf86VGAArbiter (X server implementation)`
D	bad_memory.txt	`8 There are three possibilities I know of: 38 some others. All had 0x1869xxxx in common, so I chose a pattern of`
D	oops-tracing.txt	52 NOTE: the message from Linus below applies to 2.4 kernel. I have preserved it 63 Actually, there are things you can do that make this easier. I have two 86 and do a replace of spaces to "\x" - that's what I do, as I'm too lazy 127 some small amount of concentration, you're right. Which is why I will 129 info etc looked up: it simply gets too hard to look it up (I have some 131 sometimes I have been able to look up those kinds of panics too, but 135 _Sometimes_ it happens that I just see the disassembled code sequence 136 from the panic, and I know immediately where it's coming from. That's when 137 I get worried that I've been doing this for too long ;-) 263 12: 'I' if the kernel is working around a severe bug in the platform
/linux-4.1.27/arch/mips/sibyte/
D	Platform	`13 -I$(srctree)/arch/mips/include/asm/mach-sibyte \ 17 -I$(srctree)/arch/mips/include/asm/mach-sibyte \ 21 -I$(srctree)/arch/mips/include/asm/mach-sibyte \ 25 -I$(srctree)/arch/mips/include/asm/mach-sibyte \`
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/engine/sec/fuc/
D	g98.fuc0s	`113 iowr I[$r2 + 0x300] $r1 117 iowr I[$r2] $r1 122 iowr I[$r2] $r1 136 iord $r1 I[$r0 + 0x200] 152 iord $r4 I[$r3] 163 iowr I[$r3] $r4 166 iowr I[$r3 + 0x200] $r4 172 iord $r4 I[$r3 + 0x100] 188 iowr I[$r8] $r7 195 iowr I[$r3 + 0x200] $r5 [all …]`
/linux-4.1.27/drivers/zorro/
D	zorro.ids	`38 4500 A2232 Prototype [Multi I/O] 39 4600 A2232 [Multi I/O] 88 ff00 GPIB/Dual IEEE-488/Twin-X [Multi I/O] 118 0800 Impact Series I [SCSI Host Adapter and RAM Expansion] 132 0100 Impact Series I (4K) [SCSI Host Adapter] 133 0200 Impact Series I (16K/2) [SCSI Host Adapter] 134 0300 Impact Series I (16K/2) [SCSI Host Adapter] 144 0b98 IO-Extender [Multi I/O] 192 1000 MultiFace I [Multi I/O] 208 0500 32Bit Parallel I/O Interface [all …]`
/linux-4.1.27/arch/ia64/kernel/
D	kprobes.c	`45 enum instruction_type {A, I, M, F, B, L, X, u}; enumerator 47 { M, I, I }, /* 00 / 48 { M, I, I }, / 01 / 49 { M, I, I }, / 02 / 50 { M, I, I }, / 03 / 55 { M, M, I }, / 08 / 56 { M, M, I }, / 09 / 57 { M, M, I }, / 0A / 58 { M, M, I }, / 0B / 59 { M, F, I }, / 0C */ [all …]`
/linux-4.1.27/Documentation/sysctl/
D	README	`4 'Why', I hear you ask, 'would anyone even _want_ documentation 23 The consequences are that I won't guarantee the correctness of 25 screwed up your system because of wrong documentation, I won't 26 feel sorry for you. I might even laugh at you... 29 only the sysctl options used in this file, I'd like to hear of 73 These are the subdirs I have on my system. There might be more 74 or other subdirs in another setup. If you see another dir, I'd`
/linux-4.1.27/drivers/net/wireless/ath/ath9k/
D	ar9003_paprd.c	430 int G_fxp, Y_intercept, order_x_by_y, M, I, L, sum_y_sqr, sum_y_quad; in create_pa_curve() local 551 I = (max_index > 15) ? 7 : max_index >> 1; in create_pa_curve() 552 L = max_index - I; in create_pa_curve() 564 if (y_est[i + I] == 0) in create_pa_curve() 568 x_est[i + I] - ((1 << scale_factor) * y_est[i + I] + in create_pa_curve() 572 (x_est_fxp1_nonlin * (1 << M) + y_est[i + I]) / y_est[i + in create_pa_curve() 573 I]; in create_pa_curve() 575 (x_tilde[i] * (1 << M) + y_est[i + I]) / y_est[i + I]; in create_pa_curve() 577 (x_tilde[i] * (1 << M) + y_est[i + I]) / y_est[i + I]; in create_pa_curve() 579 (y_est[i + I] * y_est[i + I] + in create_pa_curve() [all …]
/linux-4.1.27/Documentation/filesystems/
D	hpfs.txt	25 - there is a list of text extensions (I thing it's better to not convert 28 heuristic algorithm that I removed. I thing it's danger to let the 34 danger. I tried to write it so that it won't crash if check=normal on 85 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV" 94 chgrp symlinks but I don't know what is it good for. chmoding symlink results 99 extended attributes and partly in OS2SYS.INI. I don't want (and don't know how) 108 support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk. 109 Once I booted English OS/2 working in cp 850 and I created a file on my 852 110 partition. It marked file name codepage as 850 - good. But when I again booted 114 really what IBM developers wanted? But problems continued. When I created in [all …]
/linux-4.1.27/Documentation/scsi/
D	sym53c500_cs.txt	`11 the code fragments I shamelessly adapted for this work. Thanks also to 12 Christoph Hellwig for his patient tutelage while I stumbled about. 16 other products using this chip, but I've never laid eyes (much less hands) 20 version of this driver, and I guess it worked for those users. It worked`
D	in2000.txt	8 compiled for SMP. I've fixed that problem, and after 58 I _think_ it may have been a little too lax, causing an 66 about; I figure that people who are really into it will 82 through Intel assembly language, I made an error in the 90 testing and optimizing: I think there's a real improvement 106 a few people downloaded before I caught it - could have 114 jury is still out on speed - I hope it's improved some. 116 reselect. The driver defaults to what I'm calling 135 I believe that disabling disconnects (DIS_NEVER) will allow you 136 to choose a LEVEL2 value higher than 'L2_BASIC', but I haven't [all …]
D	NinjaSCSI.txt	`12 PC card: I-O data PCSC-F (NinjaSCSI-3) 13 I-O data CBSC-II in 16 bit mode (NinjaSCSI-32Bi) 14 SCSI device: I-O data CDPS-PX24 (CD-ROM drive) 39 kernel source, I recommend rebuilding your kernel; this eliminates 110 It works good when I using this driver right way. But I'm not guarantee`
D	dtc3x80.txt	`31 on-chip buffer needs CPU attention. I couldn't get this to work. So 34 scsi disconnect/reconnect, and this (mostly) works. However..... I 38 the transfer state. I have tested with: "dd bs=4k count=2k 41 nowhere, I give up. So.....This driver does NOT use interrupts, even`
D	FlashPoint.txt	48 intelligent I/O technologies that increase network management control, 49 enhance CPU utilization, optimize I/O performance, and ensure data security 96 In the middle of December, I asked to meet with BusLogic's senior 99 publicly about BusLogic's attitude toward the Linux community, and I felt 100 it was best that these issues be addressed directly. I sent an email 115 take quite a while for a usable driver to be written, especially since I'm 138 I was a beta test site for the BT-948/958, and versions 1.2.1 and 1.3.1 of 148 sure have come a long way since the last time I worked on firmware for an 149 embedded system. I am presently working on some performance testing and 154 directly via email, or have appeared in the Linux newsgroups in which I
D	advansys.txt	`87 specifying a 5th (ASC_NUM_IOPORT_PROBE + 1) I/O Port. The 88 first three hex digits of the pseudo I/O Port must be set to 163 This option can be used to either disable I/O port scanning or to limit 164 scanning to 1 - 4 I/O ports. Regardless of the option setting EISA and 169 1. Eliminate I/O port scanning: 173 2. Limit I/O port scanning to one I/O port: 175 3. Limit I/O port scanning to four I/O ports: 185 I/O Port may be added to specify the driver debug level. Refer to`
D	BusLogic.txt	58 Mylex has been an excellent company to work with and I highly recommend their 59 products to the Linux community. In November 1995, I was offered the 72 Linux community, and I am now working on a Linux driver for the DAC960 PCI RAID 139 device or logical unit, and can improve I/O performance substantially. In 141 performance, and scatter/gather I/O can support as many segments as can be 142 effectively utilized by the Linux I/O subsystem. Control over the use of 180 driver will interrogate the PCI configuration space and use the I/O port 181 addresses assigned by the system BIOS, rather than the ISA compatible I/O 182 port addresses. The ISA compatible I/O port address is then disabled by the 184 used to disable the ISA compatible I/O port entirely as it is not necessary. [all …]
D	scsi-changer.txt	`49 I implemented the driver as character device driver with a NetBSD-like 66 I test and use the driver myself with a 35 slot cdrom jukebox from 67 Grundig. I got some reports telling it works ok with tape autoloaders 73 I don't have any device lists, neither black-list nor white-list. Thus 162 I wrote this driver using the famous mailing-patches-around-the-world 172 for a old, second-hand (but full functional) cdrom jukebox which I use`
/linux-4.1.27/Documentation/mtd/
D	nand_ecc.txt	5 I felt there was room for optimisation. I bashed the code for a few hours 8 Still I was not too happy as I felt there was additional room for improvement. 10 Bad! I was hooked. 11 I decided to annotate my steps in this file. Perhaps it is useful to someone 22 This is done by means of a Hamming code. I'll try to explain it in 23 laymans terms (and apologies to all the pro's in the field in case I do 25 years ago, and I must admit it was not one of my favourites). 27 As I said before the ecc calculation is performed on sectors of 256 74 The story now becomes quite boring. I guess you get the idea. 93 I detected after writing this that ST application note AN1823 [all …]
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
D	trivial-devices.txt	15 adi,adt7461 +/-1C TDM Extended Temp Range I.C 16 adt7461 +/-1C TDM Extended Temp Range I.C 17 adi,adt7473 +/-1C TDM Extended Temp Range I.C 18 adi,adt7475 +/-1C TDM Extended Temp Range I.C 19 adi,adt7476 +/-1C TDM Extended Temp Range I.C 20 adi,adt7490 +/-1C TDM Extended Temp Range I.C 48 dallas,ds3232 Extremely Accurate I²C RTC with Integrated Crystal and SRAM 49 dallas,ds4510 CPU Supervisor with Nonvolatile Memory and Programmable I/O 68 maxim,max6625 9-Bit/12-Bit Temperature Sensors with I²C-Compatible Serial Interface 77 nxp,pca9557 8-bit I2C-bus and SMBus I/O port with reset
/linux-4.1.27/scripts/coccinelle/misc/
D	doubleinit.cocci	`17 identifier I, s, fld; 22 struct I s =@p0 { ..., .fld@p = E, ...}; 25 identifier I, s, r.fld; 30 struct I s =@p0 { ..., .fld@p = E, ...};`
/linux-4.1.27/Documentation/ABI/removed/
D	video1394	`6 controller, which were used for isochronous I/O. It was added as an 7 alternative to raw1394's isochronous I/O functionality which had 10 asynchronous I/O for device discovery and configuration.`
/linux-4.1.27/scripts/coccinelle/iterators/
D	itnull.cocci	`22 iterator I; 27 I(x,...) { <... 65 iterator I; 70 *I@p1(x,...)`
/linux-4.1.27/drivers/gpu/drm/nouveau/
D	Kbuild	`2 ccflags-y += -I$(src)/include 3 ccflags-y += -I$(src)/include/nvkm 4 ccflags-y += -I$(src)/nvkm 5 ccflags-y += -I$(src)`
/linux-4.1.27/Documentation/input/
D	cs461x.txt	`13 driver as a backend. I've tested this driver with CS4610, 4-axis and 14 4-button joystick; I mean the jstest utility. Also I've tried to 20 screen in VJOYD); I have no documentation on my chip; and the existing 33 comments about them; but I've found the joystick can be initialized`
D	iforce-protocol.txt	2 This document describes what I managed to discover about the protocol used to 3 specify force effects to I-Force 2.0 devices. None of this information comes 10 I shall not be held responsible for any damage or harm caused if you try to 11 send data to your I-Force device based on what you read in this document. 28 First, I describe effects that are sent by the device to the computer 228 The amount of RAM may vary, I encountered values from 200 to 1000 bytes. Below 241 joystick/wheel). I used ComPortSpy from fCoder (alpha version!) 246 few seconds latency. Personally, I restart it every time I play an effect. 258 I-Force is trademark of Immersion Corp.
D	cd32.txt	`1 I have written a small patch that let's me use my Amiga CD32 2 joypad connected to the parallel port. Thought I'd share it with you so`
D	xpad.txt	45 and the zero-setting is not correct for the triggers (I don't know if that 46 is some limitation of jstest, since the input device setup should be fine. I 53 I tested the controller with quake3, and configuration and 54 in game functionality were OK. However, I find it rather difficult to 73 I've tested this with Stepmania, and it works quite well. 176 I have to thank ITO Takayuki for the detailed info on his site 197 I: If#= 0 Alt= 0 #EPs= 2 Cls=58(unk. ) Sub=42 Prot=00 Driver=(none) 198 E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl= 10ms 208 I: If#= 0 Alt= 0 #EPs= 2 Cls=58(unk. ) Sub=42 Prot=00 Driver=xpad 209 E: Ad=82(I) Atr=03(Int.) MxPS= 32 Ivl=4ms
D	amijoy.txt	`166 This register controls a 4 bit bi-direction I/O port 173 \| 14 \| DATRY \| I/O data Paula pin 33 \| 175 \| 12 \| DATRX \| I/O data Paula pin 32 \| 177 \| 10 \| DATLY \| I/O data Paula pin 36 \| 179 \| 08 \| DATLX \| I/O data Paula pin 35 \|`
D	ntrig.txt	`77 short lived touches. As such, I assume that the longer the continuous stream 84 I've kept that decision simple. 89 function of size, I just use it as a binary threshold. A sufficiently large 101 been far less problematic or relatively rare and I've left the defaults 104 I don't know what the optimal values are for these filters. If the defaults 106 values more comfortable, I would appreciate feedback.`
/linux-4.1.27/Documentation/sound/oss/
D	SoundPro	26 parameters for ad1848. Please let me know if it happens to you, so I can 36 recording. I don't know if this works, b/c I haven't tested it. Anyway, if 40 There is also a PCI SoundPro chip. I have not seen this chip, so I have 41 no idea if the driver will work with it. I suspect it won't. 70 another device for an I/O port or interrupt. Checking the contents of 76 to the ad1848 parameters, email me the syslog results and I'll do 80 loading with kmod, the kernel module loader, here is the section I
D	Introduction	137 easier to configure and from what I have read, they use 147 I use the following via a shell script to load my SoundBlaster: 163 When using sound as a module, I typically put these commands 210 For example, I use the following to remove my Soundblaster (rmmod 211 in the reverse order in which I loaded the modules): 218 When using sound as a module, I typically put these commands 233 (for example, I make a /lib/modules/<kernel>/misc/tmp 245 can be a configuration nightmare. I have heard reports of 3-4 246 sound cards (typically I only use 2). You can sometimes use 249 On my machine I have two sound cards (cs4232 and Soundblaster Vibra [all …]
D	AudioExcelDSP16	`19 I you own a Gallant's audio card based on SC-6600, activate the SC-6600 support. 26 set up I/O addresses, IRQ lines and DMA channels. Some parameters are 33 io I/O base address (0x220 or 0x240) 38 mss_base I/O base address for activate MSS mode (default SBPRO) 40 mpu_base I/O base address for activate MPU-401 mode 70 I'm working on the III version of the card: if someone have useful`
D	btaudio	`5 people start bugging me about this with questions, looks like I 6 should write up some documentation for this beast. That way I 7 don't have to answer that much mails I hope. Yes, I'm lazy... 71 With my Hauppauge I get noisy sound on the second input (mapped to line2`
D	ESS1868	`20 For configuring the sound card's I/O addresses, IRQ and DMA, here is a 39 In this setup, the main card I/O is 0x0220, FM synthesizer is 0x0388, and 43 the sound modules with the proper I/O information. Here is my setup:`
D	Opti	8 By the time of writing this I do not know which official 26 I highly recommend that you build a modularized sound driver. 58 This was tested with isapnptools-1.11 but I recommend that you use 64 The driver has one limitation with respect to I/O port resources: 86 To set the I/O and IRQ of the MPU. 122 I use two DMA channels (only one is required) to enable full duplex. 172 requested I get stereo-16 bit samples instead. Playback of 174 to all C931 based cards. I do not know how to identify cards that
/linux-4.1.27/Documentation/fb/
D	matroxfb.txt	101 Switching to another console and back fixes it. I hope that it is SVGALib's 102 problem and not mine, but I'm not sure. 133 novga - disables VGA I/O ports. It is default if BIOS did not enable device. 136 vga - preserve state of VGA I/O ports. It is default. Driver does not 137 enable VGA I/O if BIOS did not it (it is not safe to enable it in 209 Millennium I or II, because of these devices have hardware 293 but I'm not sure. 302 66 MHz on Millennium I 304 Because I have no access to other devices, I do not know specific 310 But Matrox says on product sheet that VCO limit is 50-250 MHz, so I believe [all …]
D	metronomefb.txt	`26 udev/hotplug setup. I have only tested with a single waveform file which was 27 originally labeled 23P01201_60_WT0107_MTC. I do not know what it stands for. 30 I neither have access to nor know exactly what the waveform does in terms of`
/linux-4.1.27/Documentation/devicetree/bindings/pci/
D	nvidia,tegra20-pcie.txt	37 - The remaining entries setup the mapping for the standard I/O, memory and 40 - 0x81000000: I/O memory region 70 - vdd-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V. 83 - vddio-pex-ctl-supply: Power supply for PCIe control I/O partition. Must 85 - hvdd-pex-supply: High-voltage supply for PCIe I/O and PCIe output clocks. 90 - vdd-pexa-supply: Power supply for digital PCIe I/O. Must supply 1.05 V. 93 - vdd-pexb-supply: Power supply for digital PCIe I/O. Must supply 1.05 V. 98 - dvddio-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V. 101 - hvdd-pex-supply: High-voltage supply for PCIe I/O and PCIe output clocks. 105 - vddio-pex-ctl-supply: Power supply for PCIe control I/O partition. Must [all …]
D	versatile.txt	`17 - ranges: ranges for the PCI memory and I/O regions 35 ranges = <0x01000000 0 0x00000000 0x43000000 0 0x00010000 /* downstream I/O */`
D	brcm,iproc-pcie.txt	`5 - reg: base address and length of the PCIe controller I/O register space 14 - ranges: ranges for the PCI memory and I/O regions`
D	samsung,exynos5440-pcie.txt	`29 0x81000000 0 0 0x40001000 0 0x00010000 /* downstream I/O / 49 0x81000000 0 0 0x60001000 0 0x00010000 / downstream I/O */`
/linux-4.1.27/arch/mips/txx9/
D	Platform	`5 -I$(srctree)/arch/mips/include/asm/mach-tx39xx 7 -I$(srctree)/arch/mips/include/asm/mach-tx49xx`
/linux-4.1.27/Documentation/arm/nwfpe/
D	NOTES	`1 There seems to be a problem with exp(double) and our emulator. I haven't 5 I also found one oddity in the emulator. I don't think it is serious but 11 I was looking at some code, that calculated a double result, stored it in f4`
D	README	`8 emits as the first target. I have attempted to be as optimal as 11 I have attempted to make the emulator as portable as possible. One of 13 kernels have no leading underscores, a.out compiled kernels do. I 17 Another choice I made was in the file structure. I have attempted to`
/linux-4.1.27/drivers/lguest/
D	README	`3 Lguest is an adventure, with you, the reader, as Hero. I can't think of many 8 know, all true Heroes are driven by a Noble Goal. Thus I offer a Beer (or 9 equivalent) to anyone I meet who has completed this documentation. 17 I) Preparation`
/linux-4.1.27/drivers/power/
D	apm_power.c	`123 union power_supply_propval I; in do_calculate_time() local 131 if (MPSY_PROP(CURRENT_AVG, &I)) { in do_calculate_time() 133 if (MPSY_PROP(CURRENT_NOW, &I)) in do_calculate_time() 137 if (!I.intval) in do_calculate_time() 189 return ((cur.intval - full.intval) * 60L) / I.intval; in do_calculate_time() 191 return -((cur.intval - empty.intval) * 60L) / I.intval; in do_calculate_time()`
/linux-4.1.27/Documentation/RCU/
D	rcu.txt	`47 o If I am running on a uniprocessor kernel, which can only do one 48 thing at a time, why should I wait for a grace period? 52 o How can I see where RCU is currently used in the Linux kernel? 62 o What guidelines should I follow when writing code that uses RCU? 72 o I hear that RCU is patented? What is with that? 81 o I hear that RCU needs work in order to support realtime kernels? 89 o Where can I find more information on RCU?`
/linux-4.1.27/drivers/uio/
D	Kconfig	`2 tristate "Userspace I/O drivers" 28 tristate "Userspace I/O platform driver with generic IRQ handling" 30 Platform driver for Userspace I/O devices, including generic 44 Platform driver for Userspace I/O devices, including generic 65 This device differs from other UIO devices since it uses I/O 66 ports instead of memory mapped I/O. In order to make it 78 Userspace I/O interface for the Sercos III PCI card from 149 Userspace I/O interface for the Humusoft MF624 PCI card.`
/linux-4.1.27/Documentation/trace/
D	coresight.txt	`39 \| #######<-->: I : \| #######<-->: I : : I : @@@<-\| \|\|\|\|\|\|\|\|\|\|\|\| 68 \|------>&& ETB &&<......II I ======= 69 \| ! &&&&&&&&& II I . 70 \| ! I I . 71 \| ! I REP I<.......... 72 \| ! I I 73 \| !!>&&&&&&&&& II I *Source: ARM ltd. 74 \|------>& TPIU &<......II I DAP = Debug Access Port`
/linux-4.1.27/arch/mips/netlogic/
D	Platform	`4 cflags-$(CONFIG_NLM_COMMON) += -I$(srctree)/arch/mips/include/asm/mach-netlogic 5 cflags-$(CONFIG_NLM_COMMON) += -I$(srctree)/arch/mips/include/asm/netlogic`
/linux-4.1.27/drivers/staging/media/bcm2048/
D	TODO	`13 actually read() from the device I am not sure whether the RDS 22 radio-si4713/si4713-i2c.c as a good example. But I would wait with that 23 until the rest of the driver is cleaned up. Then I have a better idea of`
/linux-4.1.27/drivers/iio/
D	Kconfig	`2 # Industrial I/O subsystem configuration 6 tristate "Industrial I/O support" 9 The industrial I/O subsystem provides a unified framework for 30 tristate "Industrial I/O buffering based on kfifo"`
/linux-4.1.27/arch/x86/kvm/
D	emulate.c	3747 #define I(_f, _e) { .flags = (_f), .u.execute = (_e) } macro 3758 #define I2bv(_f, _e) I((_f) \| ByteOp, _e), I(_f, _e) 3769 I(SrcNone \| Priv \| EmulateOnUD, em_hypercall), 3808 I(DstMem \| SrcNone \| Mov \| Stack \| IncSP, em_pop), N, N, N, N, N, N, N, 3842 I(SrcMem \| NearBranch, em_call_near_abs), 3843 I(SrcMemFAddr \| ImplicitOps \| Stack, em_call_far), 3844 I(SrcMem \| NearBranch, em_jmp_abs), 3845 I(SrcMemFAddr \| ImplicitOps, em_jmp_far), 3846 I(SrcMem \| Stack, em_push), D(Undefined), 3883 N, I(DstMem64 \| Lock \| PageTable, em_cmpxchg8b), N, N, N, N, N, N, [all …]
/linux-4.1.27/drivers/staging/xgifb/
D	TODO	`1 This drivers still needs a lot of work. I can list all cleanups to do but it's 2 going to be long. So, I'm writing "cleanups" and not the list.`
/linux-4.1.27/arch/arm/nwfpe/
D	ChangeLog	`44 * I discovered several bugs. First and worst is that the kernel 58 * Second I noticed resetFPA11 was not always being called for a 62 this to be zero. Not so. I found that the kernel recycles task 64 I couldn't even find anything that guarantees it is zeroed when 66 I now initialize the entire FPE state in the thread structure to 69 alloc_task_struct() may not be necessary, but I left it in for`
/linux-4.1.27/Documentation/i2c/busses/
D	i2c-nforce2	`37 I/O ports at c000 [size=32] 47 SMBus 2.0 adapter in the AMD-8111 south bridge. However, I could only get 48 the driver to work with direct I/O access, which is different to the EC`
D	i2c-parport-light	`6 on the parport driver, and uses direct I/O access instead. This might be 17 * base: base I/O address`
D	i2c-sis96x	`41 I suspect that this driver could be made to work for the following SiS 52 * The driver does not support SMBus block reads/writes; I may add them if a 62 - ditto, plus an important datasheet... almost the one I really wanted`
/linux-4.1.27/arch/arc/kernel/
D	head.S	`26 ; Disable I-cache/D-cache if kernel so configured 28 breq r5, 0, 1f ; I$ doesn't exist`
/linux-4.1.27/Documentation/vm/
D	zswap.txt	`6 for potentially reduced swap I/O. This trade-off can also result in a 18 * Overcommitted guests that share a common I/O resource can 19 dramatically reduce their swap I/O pressure, avoiding heavy handed I/O 21 impact to the guest workload and guests sharing the I/O subsystem`
D	active_mm.txt	`6 Cc'd to linux-kernel, because I don't write explanations all that often, 7 and when I do I feel better about more people reading them. 13 > discussed on the mailing lists---I just returned from vacation and 76 Anyway, I put a pre-patch-2.3.13-1 on ftp.kernel.org just a moment ago,`
/linux-4.1.27/Documentation/hid/
D	uhid.txt	1 UHID - User-space I/O driver support for HID subsystem 9 device connected to the user-space controlled bus. The UHID API defines the I/O 21 If a new device is detected by your HID I/O Driver and you want to register this 42 I/O with readv()/writev(). 52 event. If you receive the UHID_OPEN event, you should start I/O. If the last 58 You may decide to ignore UHID_OPEN/UHID_CLOSE, though. I/O is allowed even 90 This creates the internal HID device. No I/O is possible until you send this 92 contains information about your device. You can start I/O now. 95 This destroys the internal HID device. No further I/O will be accepted. There 109 field to 0 if no error occurred or to EIO if an I/O error occurred. [all …]
D	hid-transport.txt	1 HID I/O Transport Drivers 7 Bluetooth, I2C and user-space I/O drivers. 12 The HID subsystem is designed as a bus. Any I/O subsystem may provide HID 24 \| I/O Driver \| \| I/O Driver \| 45 I/O: USB, I2C, Bluetooth-l2cap 55 I/O drivers normally provide hotplug detection or device enumeration APIs to the 88 driver must provide two bi-directional I/O channels to each HID device. These 247 However, once ->open() is called, transport drivers must be ready for I/O. 254 Transport drivers can put devices asleep and terminate any I/O of all 301 Transport drivers are responsible of reading data from I/O devices. They must [all …]
/linux-4.1.27/drivers/net/ethernet/alteon/
D	Kconfig	`36 bool "Omit support for old Tigon I based AceNICs" 40 out support for the older Tigon I based cards which are no longer 43 app. 100KB. If you are not sure whether your card is a Tigon I or a`
/linux-4.1.27/fs/squashfs/
D	Kconfig	74 bool "Use multiple decompressors for parallel I/O" 77 poor performance on parallel I/O workloads when using multiple CPU 80 If you have a parallel I/O workload and your system has enough memory, 81 using this option may improve overall I/O performance. 88 bool "Use percpu multiple decompressors for parallel I/O" 91 poor performance on parallel I/O workloads when using multiple CPU 178 the optimal I/O size is 4K (even though the devices can support 181 Using a 4K device block size may also improve overall I/O
/linux-4.1.27/arch/mips/alchemy/
D	Platform	`12 cflags-$(CONFIG_MIPS_DB1XXX) += -I$(srctree)/arch/mips/include/asm/mach-db1x00 38 cflags-$(CONFIG_MIPS_ALCHEMY) += -I$(srctree)/arch/mips/include/asm/mach-au1x00`
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
D	gpio-pcf857x.txt	`1 * PCF857x-compatible I/O expanders 3 The PCF857x-compatible chips have "quasi-bidirectional" I/O lines that can be 45 The I/O expander can detect input state changes, and thus optionally act as 60 Example: PCF8575 I/O expander node`
/linux-4.1.27/drivers/gpu/drm/msm/
D	NOTES	`9 (I don't have a completely clear picture on which display controller 19 display controller blocks. And I for sure don't want to have to deal 70 (ie. like DT super-node.. but I don't have any snapdragon hw yet that 73 Note that so far I've not been able to get any docs on the hw, and it 76 names (I had to invent a few, since no sufficient hint was given in`
/linux-4.1.27/Documentation/virtual/kvm/devices/
D	s390_flic.txt	`4 FLIC handles floating (non per-cpu) interrupts, i.e. I/O, service and some 53 Register an I/O adapter interrupt source. Takes a kvm_s390_io_adapter 64 id contains the unique id for the adapter, isc the I/O interruption subclass 70 Modifies attributes of an existing I/O adapter interrupt source. Takes`
/linux-4.1.27/Documentation/power/
D	swsusp.txt	123 Q: Maybe I'm missing something, but why don't the regular I/O paths work? 125 A: We do use the regular I/O paths. However we cannot restore the data 138 between 0-640KB. That way, I'd have to make sure that 0-640KB is free 180 Q: I do not understand why you have such strong objections to idea of 184 it's useless for suspend-to-disk. (And I do not see how you could use 185 it for suspend-to-ram, I hope you do not want that). 206 complicated code. (And I have not yet introduce details like system 308 Q: Can I suspend to a swap file? 335 little as possible modules loaded helps a lot. I also prefer people to 349 Q: How do I make suspend more verbose? [all …]
/linux-4.1.27/Documentation/PCI/
D	pci-error-recovery.txt	18 halting all I/O to it. The goal of a disconnection is to avoid system 34 It also gives the drivers a chance to defer incoming I/O as 41 of reset it desires, the choices being a simple re-enabling of I/O 46 After a reset and/or a re-enabling of I/O, all drivers are 88 pci_channel_io_normal, /* I/O channel is in normal state / 89 pci_channel_io_frozen, / I/O to channel is blocked */ 118 is isolated, in that all I/O is blocked: all reads return 0xffffffff, 129 already have "noticed" the error because of a failing I/O, but this 174 >>> attempts I/O at this point, or not. I/O's will fail, returning 176 >>> EEH_MAX_FAILS I/O's are attempted to a frozen adapter, EEH [all …]
D	pci-iov-howto.txt	`1 PCI Express I/O Virtualization Howto 13 Single Root I/O Virtualization (SR-IOV) is a PCI Express Extended 28 2.1 How can I enable SR-IOV capability 46 2.2 How can I use the Virtual Functions`
/linux-4.1.27/sound/oss/
D	Kconfig	70 Memory-mapped I/O base address for the MultiSound Classic and 74 hex "MSND Classic I/O 210, 220, 230, 240, 250, 260, 290, 3E0" 78 I/O port address for the MultiSound Classic and related cards. 133 Memory-mapped I/O base address for the primary synthesizer on 137 hex "MSND Pinnacle I/O 210, 220, 230, 240, 250, 260, 290, 3E0" 141 Memory-mapped I/O base address for the primary synthesizer on 145 bool "MSND Pinnacle has S/PDIF I/O" 184 hex "MSND Pinnacle MPU I/O (e.g. 330)" 188 Memory-mapped I/O base address for the Kurzweil daughterboard 200 hex "MSND Pinnacle IDE I/O 0 (e.g. 170)" [all …]
/linux-4.1.27/drivers/staging/media/mn88473/
D	TODO	`14 checkpatch.pl tests. I don't want waste my time to review this kind of 15 trivial stuff. Do not add missing register I/O error checks. Those are`
/linux-4.1.27/drivers/staging/media/mn88472/
D	TODO	`14 checkpatch.pl tests. I don't want waste my time to review this kind of 15 trivial stuff. Do not add missing register I/O error checks. Those are`
/linux-4.1.27/drivers/parisc/
D	README.dino	`6 equipped with third-party or customer-installed PCI I/O expansion 9 when data is transmitted through PCI I/O expansion cards on the`
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
D	guts.txt	`3 The global utilities block controls power management, I/O device 5 I/O signal configuration, alternate function selection for multiplexed`
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
D	mmc.txt	`37 - mmc-ddr-1_8v: eMMC high-speed DDR mode(1.8V I/O) is supported 38 - mmc-ddr-1_2v: eMMC high-speed DDR mode(1.2V I/O) is supported 39 - mmc-hs200-1_8v: eMMC HS200 mode(1.8V I/O) is supported 40 - mmc-hs200-1_2v: eMMC HS200 mode(1.2V I/O) is supported 41 - mmc-hs400-1_8v: eMMC HS400 mode(1.8V I/O) is supported 42 - mmc-hs400-1_2v: eMMC HS400 mode(1.2V I/O) is supported`
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
D	macros.fuc	`185 / iord reg I[reg + 0x000] 189 / iord reg I[reg + 0x000] 196 / iowr I[$r0 + 0x000] reg / 201 / iowr I[$r0 + 0x000] reg / 209 / iowrs I[$r0 + 0x000] reg / 214 / iowrs I[$r0 + 0x000] reg /`
/linux-4.1.27/Documentation/laptops/
D	disk-shock-protection.txt	`24 a shock protection facility. The idea is to stop all I/O operations on 43 of the respective drive off the platter and block all I/O operations 62 /dev/sda and stop all I/O operations for five seconds: 82 been issued to a device successfully, all I/O operations on the 92 actually result in stopping I/O to a whole bunch of devices. However, 104 I/O operations on that drive (and the reset itself) will be delayed 132 protection on different systems. Unfortunately, I only know of a`
/linux-4.1.27/drivers/scsi/pcmcia/
D	Kconfig	`47 I-O DATA CDPS-PX24's card (PCSC-F) 54 [I-O DATA (OEM) (version string: "IO DATA","CBSC16 ","1")] 55 I-O DATA CBSC-II`
/linux-4.1.27/Documentation/sound/alsa/
D	CMIPCI.txt	40 [ Well.. I once got the output with correct volume (i.e. same with the 42 on and "double DAC" mode. Actually I could hear separate 4 channels 44 It's a very pity that I didn't save the register dump at that 104 Digital I/O 108 price (yes, that's the reason I bought the card :) 213 You need to set the module option "mpu_port" to a valid I/O port address 214 to enable MIDI support. Valid I/O ports are 0x300, 0x310, 0x320 and 234 I don't know why.. 244 If the auto-detection fails, try to pass the exact I/O address.
/linux-4.1.27/arch/unicore32/mm/
D	Kconfig	`13 bool "Disable I-Cache (I-bit)"`
/linux-4.1.27/include/math-emu/
D	op-1.h	`30 #define _FP_FRAC_SET_1(X,I) (X##_f = I) argument 35 #define _FP_FRAC_ADDI_1(X,I) (X##_f += I) argument`
/linux-4.1.27/scripts/
D	Kbuild.include	`197 # Prefix -I with $(srctree) if it is not an absolute path. 198 # skip if -I has no parameter 199 addtree = $(if $(patsubst -I%,%,$(1)), \ 200 $(if $(filter-out -I/%,$(1)),$(patsubst -I%,-I$(srctree)/%,$(1))) $(1)) 202 # Find all -I options and call addtree 203 flags = $(foreach o,$($(1)),$(if $(filter -I%,$(o)),$(call addtree,$(o)),$(o)))`
/linux-4.1.27/fs/befs/
D	ChangeLog	29 * Fixed up some places where I assumed that a long int could hold 34 This is bad, since 2.4.9 is still the current RedHat kernel. I added 59 they work. I had forgotten all about them. (inode.c, symlink.c) [WD] 126 in directories. A cleaner solution will come after I've thought about it 197 * Removed all the Read-Write stuff. I'll redo it when it is time to add 217 I've done some serious testing on it now (on my box anyhow), and it 219 correct (see TODO list). But it isn't 1.0 yet. I think 0.4 gives me some 225 * Fixed date format in this file. Was I smoking crack? 281 I have no intention of supporting it, and it was very ugly. 282 Flow control with #ifdef (ugh). Maybe I'll redo it once [all …]
/linux-4.1.27/arch/mips/sgi-ip22/
D	Platform	`11 cflags-$(CONFIG_SGI_IP22) += -I$(srctree)/arch/mips/include/asm/mach-ip22 33 cflags-$(CONFIG_SGI_IP28) += -mr10k-cache-barrier=store -I$(srctree)/arch/mips/include/asm/mach-ip28`
/linux-4.1.27/drivers/net/fddi/
D	Kconfig	`36 This instructs the driver to use EISA or PCI memory-mapped I/O 37 (MMIO) as appropriate instead of programmed I/O ports (PIO). 40 adapters. TURBOchannel does not have the concept of I/O ports,`
/linux-4.1.27/arch/x86/purgatory/
D	sha256.c	`38 static inline void LOAD_OP(int I, u32 W, const u8 input) in LOAD_OP() argument 40 W[I] = __be32_to_cpu(((__be32 )(input))[I]); in LOAD_OP() 43 static inline void BLEND_OP(int I, u32 W) in BLEND_OP() argument 45 W[I] = s1(W[I-2]) + W[I-7] + s0(W[I-15]) + W[I-16]; in BLEND_OP()`
/linux-4.1.27/arch/arm/boot/compressed/
D	head.S	623 mcr p15, 0, r0, c2, c0, 1 @ I-cache on 627 mcr p15, 0, r0, c5, c0, 1 @ I-access permission 632 mcr p15, 0, r0, c7, c5, 0 @ flush(inval) I-Cache 635 @ ...I .... ..D. WC.M 642 mcr p15, 0, r0, c7, c5, 0 @ flush(inval) I-Cache 743 mcr p15, 0, r0, c8, c7, 0 @ flush I,D TLBs 745 orr r0, r0, #0x5000 @ I-cache enable, RR cache replacement 750 mcr p15, 0, r0, c8, c7, 0 @ flush I,D TLBs 764 mcrne p15, 0, r0, c8, c7, 0 @ flush I,D TLBs 768 orr r0, r0, #0x5000 @ I-cache enable, RR cache replacement [all …]
/linux-4.1.27/arch/arm/common/
D	vlock.S	`91 eor r0, r1, r2 @ zero if I won, else nonzero 96 mov r0, #1 @ nonzero indicates that I lost`

12 3 4 5

Project(s)

Full Search
Definition
Symbol
File Path
History
Type