/linux-4.1.27/drivers/net/wireless/ath/ath9k/ |
D | debug_sta.c | 26 struct ath_node *an = file->private_data; in read_file_node_aggr() local 27 struct ath_softc *sc = an->sc; in read_file_node_aggr() 40 if (!an->sta->ht_cap.ht_supported) { in read_file_node_aggr() 47 an->maxampdu); in read_file_node_aggr() 49 an->mpdudensity); in read_file_node_aggr() 54 for (acno = 0, ac = &an->ac[acno]; in read_file_node_aggr() 69 for (tidno = 0, tid = &an->tid[tidno]; in read_file_node_aggr() 114 struct ath_node *an; in ath_debug_rate_stats() local 125 an = (struct ath_node *) sta->drv_priv; in ath_debug_rate_stats() 126 rstats = &an->rx_rate_stats; in ath_debug_rate_stats() [all …]
|
D | dynack.c | 85 struct ath_node *an; in ath_dynack_compute_ackto() local 90 list_for_each_entry(an, &da->nodes, list) in ath_dynack_compute_ackto() 91 if (an->ackto > to) in ath_dynack_compute_ackto() 92 to = an->ackto; in ath_dynack_compute_ackto() 118 struct ath_node *an; in ath_dynack_compute_to() local 143 an = (struct ath_node *)sta->drv_priv; in ath_dynack_compute_to() 144 an->ackto = ath_dynack_ewma(an->ackto, in ath_dynack_compute_to() 147 "%pM to %u\n", dst, an->ackto); in ath_dynack_compute_to() 280 void ath_dynack_node_init(struct ath_hw *ah, struct ath_node *an) in ath_dynack_node_init() argument 286 an->ackto = ackto; in ath_dynack_node_init() [all …]
|
D | dynack.h | 84 void ath_dynack_node_init(struct ath_hw *ah, struct ath_node *an); 85 void ath_dynack_node_deinit(struct ath_hw *ah, struct ath_node *an); 93 struct ath_node *an) {} in ath_dynack_node_init() argument 95 struct ath_node *an) {} in ath_dynack_node_deinit() argument
|
D | main.c | 348 struct ath_node *an; in ath_node_attach() local 349 an = (struct ath_node *)sta->drv_priv; in ath_node_attach() 351 an->sc = sc; in ath_node_attach() 352 an->sta = sta; in ath_node_attach() 353 an->vif = vif; in ath_node_attach() 354 memset(&an->key_idx, 0, sizeof(an->key_idx)); in ath_node_attach() 356 ath_tx_node_init(sc, an); in ath_node_attach() 358 ath_dynack_node_init(sc->sc_ah, an); in ath_node_attach() 363 struct ath_node *an = (struct ath_node *)sta->drv_priv; in ath_node_detach() local 364 ath_tx_node_cleanup(sc, an); in ath_node_detach() [all …]
|
D | xmit.c | 111 struct ath_vif *avp = (struct ath_vif *) tid->an->vif->drv_priv; in ath_tx_queue_tid() 142 if (!tid->an->sta) in ath_send_bar() 145 ieee80211_send_bar(tid->an->vif, tid->an->sta->addr, tid->tidno, in ath_send_bar() 181 ath_get_skb_tid(struct ath_softc *sc, struct ath_node *an, struct sk_buff *skb) in ath_get_skb_tid() argument 184 return ATH_AN_2_TID(an, tidno); in ath_get_skb_tid() 442 struct ath_node *an = NULL; in ath_tx_complete_aggr() local 494 an = (struct ath_node *)sta->drv_priv; in ath_tx_complete_aggr() 495 tid = ath_get_skb_tid(sc, an, skb); in ath_tx_complete_aggr() 560 if (txok || !an->sleeping) in ath_tx_complete_aggr() 639 if (an->sleeping) in ath_tx_complete_aggr() [all …]
|
/linux-4.1.27/Documentation/usb/ |
D | anchors.txt | 5 a driver to cease all IO to an interface. To do so, a 15 There's no API to allocate an anchor. It is simply declared 28 An association of URBs to an anchor is made by an explicit 30 an URB is finished by (successful) completion. Thus disassociation 32 all URBs associated with an anchor. 41 This function kills all URBs associated with an anchor. The URBs 48 This function unlinks all URBs associated with an anchor. The URBs 58 All URBs of an anchor are unanchored en masse. 63 This function waits for all URBs associated with an anchor to finish 70 Returns true if no URBs are associated with an anchor. Locking [all …]
|
D | callbacks.txt | 56 an interface. A driver's bond to an interface is exclusive. 64 Accept or decline an interface. If you accept the device return 0, 69 usb_set_intfdata(), to associate a data structure with an interface, so 80 This callback is a signal to break any connection with an interface. 99 contains the interface passed as an argument. Cease IO, wait for all 121 No callbacks other than probe will be invoked for an interface 124 Probe will never be called for an interface bound to a driver. 128 Once your driver is bound to an interface, disconnect can be
|
D | URB.txt | 13 1.1. Basic concept or 'What is an URB?' 21 - Execution of an URB is inherently an asynchronous operation, i.e. the 33 data to an endpoint while your driver handles completion of another. 40 Some of the fields in an URB are: 79 endpoint descriptor in an interface that it's claimed. 82 1.3. How to get an URB? 94 To free an URB, use 98 You may free an urb that you've submitted, but which hasn't yet been 120 1.5. How to submit an URB? 148 1.6. How to cancel an already running URB? [all …]
|
D | bulk-streams.txt | 18 an out-of-band mechanism on another endpoint) that data is ready for that stream 34 pass an array of usb_host_endpoints that need to be setup with similar stream 38 The return value is an error condition (if one of the endpoints doesn't support 60 To queue an URB for a specific stream, set the urb->stream_id value. If the 61 endpoint does not support streams, an error will be returned.
|
/linux-4.1.27/Documentation/DocBook/ |
D | .writing-an-alsa-driver.xml.cmd | 1 …riting-an-alsa-driver.xml := SRCTREE=./ ./scripts/docproc doc Documentation/DocBook/writing-an-als… 2 Documentation/DocBook/writing-an-alsa-driver.xml: Documentation/DocBook/writing-an-alsa-driver.tmpl
|
/linux-4.1.27/arch/m68k/ifpsp060/ |
D | fskeleton.S | 9 |THE SOFTWARE is provided on an "AS IS" basis and without warranty. 61 | simply execute an "rte" as with the sample code below. 70 | This is the exit point for the 060FPSP when an enabled overflow exception 72 | for enabled overflow conditions. The exception stack frame is an overflow 76 | does an "rte". 89 | This is the exit point for the 060FPSP when an enabled underflow exception 91 | for enabled underflow conditions. The exception stack frame is an underflow 95 | does an "rte". 107 | This is the exit point for the 060FPSP when an enabled operand error exception 109 | for enabled operand error exceptions. The exception stack frame is an operand error [all …]
|
D | fplsp.doc | 9 THE SOFTWARE is provided on an "AS IS" basis and without warranty. 50 then converting the resulting binary output image into an 67 The file fplsp.sa contains an "Entry-Point" section and a 82 As an example, the "fsin" library instruction can be passed an 109 entry. If an exception should be reported, then the package forces 113 executes an FMUL of a zero and an infinity to force the OPERR
|
/linux-4.1.27/Documentation/i2c/ |
D | fault-codes | 5 A "Fault" is not always an "Error" 14 result for an operation ... it doesn't indicate that anything is wrong 43 Also returned when trying to invoke an I2C operation in an 48 Returned by SMBus logic when an invalid Packet Error Code byte 63 This rather vague error means an invalid parameter has been 69 performing an I/O operation. Use a more specific fault 86 of a transfer didn't get an ACK. While it might just mean 87 an I2C device was temporarily not responding, usually it 94 Returned by an adapter when asked to perform an operation 97 For example, this would be returned when an adapter that [all …]
|
D | slave-interface | 6 Linux can also be an I2C slave in case I2C controllers have slave support. 49 The bus driver sends an event to the backend using the following function: 54 types described hereafter. 'val' holds an u8 value for the data byte to be 56 provided even if val is not used for an event, i.e. don't use NULL here. 'ret' 87 is zero, the bus driver should ack this byte. If 'ret' is an errno, then the byte 123 Check the i2c-slave-eeprom driver as an example. 140 Check the i2c-rcar driver as an example. 155 byte when it reads from us. We could make this an optional event if the need 157 to send STOP after that and we have an event for that. Also, keep in mind not 165 bytes came up. Such an extension might be possible, usefulness is unclear at [all …]
|
D | instantiating-devices | 17 devices which live on this bus. This is done with an array of struct 94 This method is appropriate when a larger device uses an I2C bus for 96 tuner, a video decoder, an audio decoder, etc. usually connected to the 97 main chip by the means of an I2C bus. You won't know the number of the I2C 120 A variant of this is when you don't know for sure if an I2C device is 121 present or not (for example for an optional feature which is not present 158 Method 3: Probe an I2C bus for certain devices 161 Sometimes you do not have enough information about an I2C device, not even 165 it is next to impossible to build an exhaustive list of the hardware 172 drivers are loaded, and if any is found, an I2C device will be [all …]
|
D | functionality | 6 is implemented when it is given the option to attach to an adapter: 7 the client needs some way to check whether an adapter has the needed 88 of an I2C adapter. 94 Before a client tries to attach to an adapter, or even do tests to check 95 whether one of the devices it supports is present on an adapter, it should 128 If you try to access an adapter from a userspace program, you will have
|
/linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
D | gpio-poweroff.txt | 7 state. Otherwise its configured as an input. 9 When the pm_power_off is called, the gpio is configured as an output, 11 condition. This will also cause an inactive->active edge condition, so 13 the GPIO is set to inactive, thus causing an active->inactive edge, 26 - input : Initially configure the GPIO line as an input. Only reconfigure 27 it to an output when the pm_power_off function is called. If this optional 28 property is not specified, the GPIO is initialized as an output in its
|
D | gpio-restart.txt | 11 priority order. The gpio is configured as an output, and driven active, 12 triggering a level triggered reset condition. This will also cause an 15 inactive, thus causing an active->inactive edge, triggering negative edge 30 specified, the GPIO is initialized as an output in its inactive state.
|
/linux-4.1.27/Documentation/powerpc/ |
D | pmu-ebb.txt | 19 Throughout this document we will refer to an "EBB event" or "EBB events". This 38 and attach an EBB event to the process, which will then cause EBBs to be 43 user process. This means once an EBB event is scheduled on the PMU, no non-EBB 54 If an EBB event and a regular event are both pinned, then whichever is enabled 56 section below titled "Enabling an EBB event" for more information. 59 Creating an EBB event 62 To request that an event is counted using EBB, the event code should have bit 86 Enabling an EBB event 89 Once an EBB event has been successfully opened, it must be enabled with the 93 However, due to the design of the perf_events API, enabling an event does not [all …]
|
/linux-4.1.27/Documentation/ |
D | assoc_array.txt | 28 This associative array implementation is an object container with the following 37 permits an object to be located in multiple arrays simultaneously. 42 (4) Index keys must be unique. Inserting an object with the same key as one 70 pack leaf object pointers into spare space in the node rather than making an 71 extra branch until as such time an object needs to be added to a full node. 91 The insertion and deletion functions produce an 'edit script' that can later be 99 after an RCU grace period has passed - thus allowing access functions to 108 (1) Apply an edit script. 117 (2) Cancel an edit script. 149 (2) Get a chunk of an object's index key. [all …]
|
D | IRQ.txt | 1 What is an IRQ? 3 An IRQ is an interrupt request from a device. 6 sharing an IRQ. 9 interrupt source. Typically this is an index into the global irq_desc 13 An IRQ number is an enumeration of the possible interrupt sources on a
|
D | rpmsg.txt | 17 its own instance of RTOS in an AMP configuration. 76 Returns 0 on success and an appropriate error value on failure. 82 its length (in bytes), and an explicit destination address. 93 Returns 0 on success and an appropriate error value on failure. 111 Returns 0 on success and an appropriate error value on failure. 123 Returns 0 on success and an appropriate error value on failure. 129 its length (in bytes), and an explicit destination address. 137 Returns 0 on success and an appropriate error value on failure. 152 Returns 0 on success and an appropriate error value on failure. 157 - every rpmsg address in the system is bound to an rx callback (so when [all …]
|
D | io-mapping.txt | 1 The io_mapping functions in linux/io-mapping.h provide an abstraction for 2 efficiently mapping small regions of an I/O device to the CPU. The initial 28 creation function yields undefined results. Using an offset 29 which is not page aligned yields an undefined result. The 66 mechanisms and so provides only an abstraction layer and no new 75 kmap_atomic_pfn to map the specified page in an atomic fashion; 77 provides an efficient mapping for this usage. 81 performs an IPI to inform all processors about the new mapping. This results
|
D | IRQ-domain.txt | 40 An interrupt controller driver creates and registers an irq_domain by 44 provide the allocator function with an irq_domain_ops structure. 54 When an interrupt is received, irq_find_mapping() function should 75 hwirq number. When a hwirq is mapped, an irq_desc is allocated for 90 IRQs. When an hwirq is mapped, an irq_desc is allocated and the 129 controller to manage IRQ allocations and it requires an irq_desc to be 138 will use a legacy domain only if an IRQ range is supplied by the 140 of this call are such that if an IRQ range is specified then 145 A typical use case for simple domains is where an irqchip provider 156 involved in delivering an interrupt from the device to the target CPU. [all …]
|
D | flexible-arrays.txt | 16 piecing together an array from smaller parts; the flexible array library 19 A flexible array holds an arbitrary (within limits) number of fixed-sized 20 objects, accessed via an integer index. Sparse arrays are handled 26 locking at all; if concurrent access to an array is possible, then the 47 This macro will result in a definition of an array with the given name; the 73 flex_array_put() call on an element in that range is guaranteed not to 83 Note that it is possible to get back a valid pointer for an element which 98 flex_array_clear() will return -EINVAL instead. Note that clearing an 100 allocated size of an array, call: 109 It is possible to remove all elements of an array with a call to:
|
D | irqflags-tracing.txt | 6 that it gives interested subsystems an opportunity to be notified of 13 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these 19 state changes. But an architecture can be irq-flags-tracing enabled in a 44 in general there is no risk from having an incomplete irq-flags-tracing 45 implementation in an architecture: lockdep will detect that and will
|
D | smsc_ece1099.txt | 14 Interrupts can be generated by an edge detection on a GPIO 15 pin or an edge detection on one of the bus interface pins. 22 of an interrupt, it should first read the Group Interrupt Status Register 26 are active interrupts. Software clears an interrupt by writing a 1 to the 54 clock, BC_CLK, and the Companion device is the source for an
|
D | unaligned-memory-access.txt | 10 The definition of an unaligned access 14 from an address that is not evenly divisible by N (i.e. addr % N != 0). 16 reading 4 bytes of data from address 0x10005 would be an unaligned memory 46 The effects of performing an unaligned memory access vary from architecture 84 Let us assume that an instance of the above structure resides in memory 86 not be unreasonable to expect that accessing field2 would cause an unaligned 102 will never cause an unaligned access, because all memory addresses are evenly 140 that can cause an unaligned memory access. The following function taken 141 from include/linux/etherdevice.h is an optimized routine to compare two 163 Think about what would happen if addr1 was an odd address such as 0x10003. [all …]
|
D | hwspinlock.txt | 21 remote M3 and/or C64x+ slave processors (by an IPC subsystem called Syslink). 38 - dynamically assign an hwspinlock and return its address, or NULL 39 in case an unused hwspinlock isn't available. Users of this 52 - free a previously-assigned hwspinlock; returns 0 on success, or an 65 Returns 0 when successful and an appropriate error code otherwise (most 76 Returns 0 when successful and an appropriate error code otherwise (most 89 Returns 0 when successful and an appropriate error code otherwise (most 100 Returns 0 on success and an appropriate error code otherwise (most 110 Returns 0 on success and an appropriate error code otherwise (most 121 Returns 0 on success and an appropriate error code otherwise (most [all …]
|
D | IRQ-affinity.txt | 10 allowed to turn off all CPUs, and if an IRQ controller does not support 18 Here is an example of restricting IRQ44 (eth1) to CPU0-3 then restricting 19 it to CPU4-7 (this is an 8-CPU SMP box): 58 Here is an example of limiting that same irq (44) to cpus 1024 to 1031:
|
D | remoteproc.txt | 12 is running its own instance of RTOS in an AMP configuration. 35 Returns 0 on success, and an appropriate error value otherwise. 43 In case @rproc is still being used by an additional user(s), then 92 After creating an rproc handle using this function, and when ready, 101 - Free an rproc handle that was allocated by rproc_alloc. 112 Returns 0 on success and an appropriate error code otherwise. 113 Note: this function initiates an asynchronous firmware loading 160 The ->start() handler takes an rproc handle and should then power on the 164 On success, 0 should be returned, and on failure, an appropriate error code. 166 The ->stop() handler takes an rproc handle and powers the device down. [all …]
|
D | md.txt | 63 For this reason, md will normally refuse to start such an array. This 69 filesystem on it. In order to support this booting from such an 98 It is 'assembled' by associating each of these devices with an 108 When an array is assembled, it is first initialized with the 121 Once started, new devices can be added. They should have an 125 Devices that have failed or are not yet active can be detached from an 167 will be empty. If an array is being resized this will contain 171 be set while assembling an array. 174 in an e.g. raid5, the array size must first be reduced by 183 of 2. This can only be set while assembling an array [all …]
|
D | rbtree.txt | 26 The high-resolution timer code uses an rbtree to organize outstanding 59 Data nodes in an rbtree tree are structures containing a struct rb_node member: 70 At the root of each rbtree is an rb_root structure, which is initialized to be 75 Searching for a value in an rbtree 103 Inserting data into an rbtree 140 Removing or replacing existing data in an rbtree 143 To remove an existing node from a tree, call: 156 To replace an existing node in a tree with a new one with the same key, call: 164 Iterating through the elements stored in an rbtree (in sort order) 167 Four functions are provided for iterating through an rbtree's contents in [all …]
|
D | eisa.txt | 12 drivers to the new infrastructure is not an easy task (mostly because 29 an I/O region on x86, to the rather more complex, like the hppa 31 running on an "new" platform. 45 root of an EISA bus. The eisa_root_device structure holds a reference 85 id_table : an array of NULL terminated EISA id strings, 86 followed by an empty string. Each string can 173 Force the probing code to probe EISA slots even when it cannot find an 180 Converting an EISA driver to the new API mostly involves *deleting*
|
D | kmemleak.txt | 27 To trigger an intermediate memory scan: 62 these actions are stored in an early log buffer. The size of this buffer 101 avoid this, kmemleak can also store the number of values pointing to an 130 disabled by the user or due to an fatal error, internal kmemleak objects 150 kmemleak_not_leak - mark an object as not a leak 151 kmemleak_ignore - do not scan or report an object as leak 154 kmemleak_erase - erase an old value in a pointer variable 177 the minimum age of an object to be reported as a memory leak. 189 address inside a block's address range. This may lead to an increased 198 The tool can report false positives. These are cases where an allocated
|
/linux-4.1.27/Documentation/ABI/stable/ |
D | sysfs-bus-firewire | 12 Binary attribute; an array of host-endian u32. 17 Hexadecimal string representation of an u64. 30 Summary of all units present in an IEEE 1394 node. 81 These attributes are only created if the root directory of an 82 IEEE 1394 node or the unit directory of an IEEE 1394 unit 86 Hexadecimal string representation of an u24. 92 Hexadecimal string representation of an u24. 98 Hexadecimal string representation of an u24. 102 Hexadecimal string representation of an u24. 109 Hexadecimal string representation of an u24. [all …]
|
D | sysfs-class-udc | 6 Indicates if an OTG A-Host supports HNP at an alternate port. 14 Indicates if an OTG A-Host supports HNP at this port. 22 Indicates if an OTG A-Host enabled HNP support. 38 Indicates that this port is the default Host on an OTG session
|
/linux-4.1.27/Documentation/filesystems/ |
D | autofs4-mount-control.txt | 15 are things such as setting an autofs mount catatonic, setting the 17 certain types of autofs triggered mounts can end up covering an autofs 36 module source you will see a third type called an offset, which is just 58 For the above indirect map an autofs file system is mounted on /test and 63 The way that direct mounts are handled is by making an autofs mount on 72 For example, an indirect mount map entry could also be: 90 One of the issues with version 4 of autofs was that, when mounting an 105 The current autofs implementation uses an ioctl file descriptor opened 119 implement an isolated operation it was decided to re-implement the 126 autofs maps. They are recorded at mount request time and an operation [all …]
|
D | affs.txt | 47 of the original permissions. Directories will get an x 53 The file system will return an error when filename exceeds 67 quiet The file system will not return an error for disallowed 79 symbolic links on an AFFS partition. Default = "/". 82 volume=name When symbolic links with an absolute path are created 83 on an AFFS partition, name will be prepended as the 162 have an Amiga harddisk connected to your PC, it will overwrite 164 the Rigid Disk Block. Sheer luck has it that this is an unused 192 do care about the case. Example (with /wb being an affs mounted fs): 200 in an ugly way (but the real AFFS doesn't do much better). This [all …]
|
D | automount-support.txt | 25 (b) Copy the nameidata provided as an argument and substitute the dentry 33 should also be given the location of an expiration list (see further 90 mount is made on an expirable mount, the new vfsmount will not be on the 94 and the copies of those that are on an expiration list will be added to the 102 As an alternative, it is possible for userspace to request expiry of any 108 umount() or its parent mountpoint, an EBUSY error will be returned and the 111 If the mountpoint was not already marked for expiry at that time, an EAGAIN
|
D | qnx6.txt | 41 So basically the snapshot functionality is realized by an atomic final 53 Level 1 adds an additional indirect addressing level where each indirect 55 Level 2 adds an additional indirect addressing block level (so, already up 76 Each object in the filesystem is represented by an inode. (index node) 78 the data held in the object and all of the metadata about an object except 80 The metadata about an object includes the permissions, owner, group, flags, 87 For more than 16 blocks an indirect addressing in form of another tree is 96 A directory is a filesystem object and has an inode just like a file. 98 name with an inode number. 116 Hard links got an inode, a directory entry, but a specific mode bit set,
|
D | exofs.txt | 5 exofs is a file system that uses an OSD and exports the API of a normal Linux 21 To use this file system, you need to have an object store to run it on. You 32 You need an external Kernel source tree or kernel headers from your 44 open-osd/top-level-Makefile for an example. 58 As an example, this will create the file system on: 83 do-exofs start - an example of how to perform the above steps. 84 do-exofs stop - an example of how to unmount the file system. 85 do-exofs format - an example of how to format and mkfs a new exofs. 100 login into an OSD target. 108 Hex by pre-pending an 0x to the number. [all …]
|
D | inotify.txt | 15 A: Watches are associated with an open inotify device, not an open file. 21 Q: What is the design decision behind using an-fd-per-instance as opposed to 22 an fd-per-watch? 28 A watch consumes less memory than an open file, separating the number 31 fd and no twiddling with fd limits. Initializing an inotify instance two
|
D | dlmfs.txt | 49 that an OCFS2 file system be in place so that it can automatically 67 request for an already acquired lock will not generate another DLM 79 maximum currently supported LVB length is 64 bytes (though that is an 93 an error has occurred, unless it has been instructed to do a trylock 94 operation. If the lock succeeds, you'll get an fd. 123 Once written, an LVB will be visible to other nodes who obtain Read
|
D | spufs.txt | 55 data in the address space of the SPU. The possible operations on an 74 operations on an open mbox file are: 88 operations on an open ibox file are: 111 operations on an open wbox file are: write(2) If a count smaller than 135 operations on an open *box_stat file are: 152 Internal registers of the SPU. The representation is an ASCII string 156 npc requires an SPU context save and is therefore very inefficient. 173 The possible operations on an open npc, decr, decr_status, 211 The two signal notification channels of an SPU. These are read-write 213 triggers an interrupt on the SPU. The value written to the signal [all …]
|
D | overlayfs.txt | 18 cases an object accessed in the union will be indistinguishable 22 While directories will report an st_dev from the overlay-filesystem, 23 all non-directory objects will report an st_dev from the lower or 32 An overlay filesystem combines two filesystems - an 'upper' filesystem 38 It would be more correct to refer to an upper and lower 'directory 70 The "workdir" needs to be an empty directory on the same filesystem 88 filesystem, an overlay filesystem needs to record in the upper filesystem 98 to "y". Where the upper filesystem contains an opaque directory, any 121 - remember an offset, and close the directory 158 overlay filesystem (though an operation on the name of the file such as [all …]
|
/linux-4.1.27/drivers/eisa/ |
D | Kconfig | 10 Bus (VLB) card that identify itself as an EISA card (such as 26 # Using EISA_VIRTUAL_ROOT on something other than an Alpha or 27 # an X86 may lead to crashes... 35 (no PCI slots). The Alpha Jensen is an example of such 50 you are building an installation floppy or kernel for an
|
/linux-4.1.27/Documentation/filesystems/caching/ |
D | backend-api.txt | 5 The FS-Cache system provides an API by which actual caches can be supplied to 84 In either case, this may not be an appropriate context in which to access the 171 An operation can be made exclusive upon an object by setting the 173 an operation needs more processing time, it should be enqueued again. 197 The to_do field is an empty list available for the cache backend to use as 228 This isn't strictly an operation, but should be pointed at a string naming 251 This method is used to look up an object, given that the object is already 278 This method is called to increment the reference count on an object. It 288 These methods are used to exclusively lock an object. It must be possible 297 These methods are used to pin an object into the cache. Once pinned an [all …]
|
D | object.txt | 25 FS-Cache maintains an in-kernel representation of each object that a netfs is 36 represented by multiple objects - an index may exist in more than one cache - 97 machine. The state for an object is kept in the fscache_object struct, in 101 Each state has an action associated with it that is invoked when the machine 105 representations are hierarchical, and it is expected that an object must 122 Then when an event is raised (by calling fscache_raise_event()), if the event 165 the cache, it is expected that it will not be possible to look an object 192 Create an object on disk, using the parent as a starting point. This 201 operations the netfs has queued for an object. If creation failed, the 232 And there are terminal states in which an object cleans itself up, deallocates [all …]
|
D | netfs-api.txt | 5 There's an API by which a network filesystem can make use of the FS-Cache 92 a particular key - for instance to mirror the removal of an AFS volume. 96 restraints as possible on how an index is structured and where it is placed in 106 cache. Any such objects created within an index will be created in the 107 first cache only. The cache in which an index is created can be 121 To define an object, a structure of the following type should be filled out: 166 This defines an index, which is a special FS-Cache type. 170 This defines an ordinary data file. 174 This defines an extraordinary object such as an XATTR. 179 (3) A function to select the cache in which to store an index [optional]. [all …]
|
D | operations.txt | 24 FS-Cache has an asynchronous operations handling facility that it uses for its 40 An operation is recorded in an fscache_operation struct: 52 Someone wanting to issue an operation should allocate something with this 79 may decide it wants to handle an operation itself without deferring it to 83 the backing filesystem in CacheFiles. Although readpages() does an 97 will be given to keventd to process. Such an operation is not permitted 110 will be given to the slow work facility to process. Such an operation is 162 The operation manager will defer operations on an object that is still 163 undergoing lookup or creation. The operation will also be deferred if an 179 (4) The operation holds an effective lock upon the object, preventing other
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/qe/ |
D | pincfg.txt | 12 1 = The pin is an output 13 2 = The pin is an input 18 0 = The pin is actively driven as an output 19 1 = The pin is an open-drain driver. As an output, the pin is
|
/linux-4.1.27/Documentation/devicetree/bindings/gpu/ |
D | nvidia,tegra20-host1x.txt | 9 - #size-cells: The number of cells used to represent the size of an address 14 - resets: Must contain an entry for each entry in reset-names. 30 - resets: Must contain an entry for each entry in reset-names. 43 - resets: Must contain an entry for each entry in reset-names. 56 - resets: Must contain an entry for each entry in reset-names. 69 - resets: Must contain an entry for each entry in reset-names. 82 - resets: Must contain an entry for each entry in reset-names. 92 - clocks: Must contain an entry for each entry in clock-names. 99 - resets: Must contain an entry for each entry in reset-names. 111 - clocks: Must contain an entry for each entry in clock-names. [all …]
|
D | nvidia,gk20a.txt | 11 - interrupts: Must contain an entry for each entry in interrupt-names. 17 - clocks: Must contain an entry for each entry in clock-names. 22 - resets: Must contain an entry for each entry in reset-names.
|
/linux-4.1.27/Documentation/devicetree/bindings/i2c/ |
D | i2c-mux-gpio.txt | 3 This binding describes an I2C bus multiplexer that uses GPIOs to 32 For each i2c child node, an I2C child bus will be created. They will 35 Whenever an access is made to a device on a child bus, the value set 39 If an idle state is defined, using the idle-state (optional) property, 40 whenever an access is not being made to a device on a child bus, the 43 If an idle state is not defined, the most recently used value will be
|
D | i2c-mux-pinctrl.txt | 3 This binding describes an I2C bus multiplexer that uses pin multiplexing to 35 For each named state defined in the pinctrl-names property, an I2C child bus 47 Whenever an access is made to a device on a child bus, the relevant pinctrl 50 If an idle state is defined, whenever an access is not being made to a device 53 If an idle state is not defined, the most recently used pinctrl state will be
|
/linux-4.1.27/Documentation/nfc/ |
D | nfc-hci.txt | 10 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core 11 backend, implementing an abstract nfc device and translating NFC Core API 17 HCI registers as an nfc device with NFC Core. Requests coming from userspace are 34 The Session initialization is an HCI standard which must unfortunately 88 - hci_ready() is an optional entry point that is called right after the hci 92 - start_poll() is an optional entrypoint that shall set the hardware in polling 99 - target_from_gate() is an optional entrypoint to return the nfc protocols 101 - complete_target_discovered() is an optional entry point to let the driver 111 - check_presence() is an optional entry point that will be called regularly 112 by the core to check that an activated tag is still in the field. If this is [all …]
|
D | nfc-pn544.txt | 7 The PN544 is an integrated transmission module for contactless 24 HCI messages consist of an eight bit header and the message body. The 25 header contains the message length. Maximum size for an HCI message is
|
/linux-4.1.27/Documentation/networking/ |
D | ppp_generic.txt | 8 The generic PPP driver in linux-2.4 provides an implementation of the 56 * ioctl() provides an interface which can be used by a user-space 58 procedure will be called when a user-space program does an ioctl 59 system call on an instance of /dev/ppp which is bound to the 86 (e.g. an ioctl) to transmit this back to user-space, as user-space 87 will need it to attach an instance of /dev/ppp to this channel. 101 communications medium and prepare it to do PPP. For example, with an 123 The channel must provide an instance of a ppp_channel struct to 255 this way an effect similar to Solaris' clone open is obtained, 256 allowing us to control an arbitrary number of PPP interfaces and [all …]
|
D | rxrpc.txt | 56 (1) Part of an RxRPC facility for both kernel and userspace applications by 84 The Andrew File System (AFS) is an example of an application that uses this and 104 a port number. AF_RXRPC permits multiple services to share an endpoint. 203 (*) If an ICMP error is received, all calls affected by that error will be 204 aborted with an appropriate network error passed through recvmsg(). 209 (*) A socket is made into a server socket by binding an address with a 220 socket. This may be overridden by supplying an alternate address to the 223 (*) If connect() is called on an unbound client, a random local port will 248 (*) A call may be aborted by adding an abort control message to the control 249 data. Issuing an abort terminates the kernel's use of that call's tag. [all …]
|
D | operstates.txt | 4 Linux distinguishes between administrative and operational state of an 9 However, an interface is not usable just because the admin enabled it 11 a site's networking policy and configuration, an 802.1X authentication 13 shows the ability of an interface to transmit this user data. 56 Interfaces stacked on an interface that is IF_OPER_DOWN show this 61 Interface is L1 up, but waiting for an external event, f.e. for a 129 RFC2863 operational state of an interface. Setting IFLA_LINKMODE to 1 130 via RTM_SETLINK instructs the kernel that an interface should go to
|
D | nfc.txt | 5 NFC device drivers development and to create an unified userspace interface. 20 responsible for providing an interface to control operations and low-level 82 * NFC_EVENT_DEVICE_ADDED - reports an NFC device addition 83 * NFC_EVENT_DEVICE_REMOVED - reports an NFC device removal 113 To establish a connection with one target, the user must create an 119 Internally, 'connect' will result in an activate_target call to the driver.
|
D | dm9000.txt | 90 device, whether or not an external PHY is attached to the device and 91 the availability of an external configuration EEPROM. 109 The chip is connected to an external PHY. 113 This can be used to signify that the board does not have an 146 When using an external PHY, the driver currently has to poll the MII 147 link status as there is no method for getting an interrupt on link change.
|
/linux-4.1.27/drivers/input/joystick/iforce/ |
D | Kconfig | 8 Say Y here if you have an I-Force joystick or steering wheel 19 Say Y here if you have an I-Force joystick or steering wheel 26 Say Y here if you have an I-Force joystick or steering wheel 29 You will need an additional utility called inputattach, see
|
/linux-4.1.27/net/atm/ |
D | Kconfig | 13 In order to participate in an ATM network, your Linux box needs an 34 Normally, an "ICMP host unreachable" message is sent if a neighbour 44 LAN Emulation emulates services of existing LANs across an ATM 46 LANE client can also act as an proxy client bridging packets between 63 This device will act like an ethernet from the kernels point of view, 71 This is an experimental mechanism for users who need to terminate a
|
/linux-4.1.27/Documentation/arm/ |
D | swp_emulation | 8 instructions, triggering an undefined instruction exception when executed. 9 Trapped instructions are emulated using an LDREX/STREX or LDREXB/STREXB 10 sequence. If a memory access fault (an abort) occurs, a segmentation fault is 22 NOTE: when accessing uncached shared regions, LDREX/STREX rely on an external
|
D | IXP4xx | 15 routing, firewalling, etc. The IXP46x family is an updated version which 17 integration such as an on-chip I2C controller. 23 Intel also made the IXCP1100 CPU for sometime which is an IXP4xx 60 Simple one page summary of building a gateway using an IXP425 and Linux 112 Finally, there is an IDE port hanging off the expansion bus. 131 This is basically an IXDP425 with an IXP465 and 32M of flash instead 139 adapter with an E100 card. So to NFS root you need to use either
|
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/ |
D | ti,omap4-wugen-mpu | 3 All TI OMAP4/5 (and their derivatives) an interrupt controller that 12 - interrupt-controller : Identifies the node as an interrupt controller. 13 - #interrupt-cells : Specifies the number of cells needed to encode an 22 - Only SPIs can use the WUGEN as an interrupt parent. SGIs and PPIs
|
D | brcm,bcm7120-l2-intc.txt | 7 Such an interrupt controller has the following hardware design: 12 directly output an interrupt signal towards the interrupt controller parent, 13 or if they will output an interrupt signal at this 2nd level interrupt 20 - not all bits within the interrupt controller actually map to an interrupt 56 - interrupt-controller: identifies the node as an interrupt controller 57 - #interrupt-cells: specifies the number of cells needed to encode an interrupt
|
D | marvell,orion-intc.txt | 8 - interrupt-controller: identifies the node as an interrupt controller 9 - #interrupt-cells: number of cells to encode an interrupt source, shall be 1 32 - interrupt-controller: identifies the node as an interrupt controller 33 - #interrupt-cells: number of cells to encode an interrupt source, shall be 1
|
D | opencores,or1k-pic.txt | 10 "opencores,or1k-pic" is also provided as an alias to "opencores,or1200-pic", 13 - interrupt-controller : Identifies the node as an interrupt controller 14 - #interrupt-cells : Specifies the number of cells needed to encode an
|
D | brcm,bcm7038-l1-intc.txt | 11 - Most onchip peripherals are wired directly to an L1 input 28 - interrupt-controller: identifies the node as an interrupt controller 29 - #interrupt-cells: specifies the number of cells needed to encode an interrupt 36 If multiple reg ranges and interrupt-parent entries are present on an SMP
|
D | atmel,aic.txt | 6 - interrupt-controller: Identifies the node as an interrupt controller. 7 - interrupt-parent: For single AIC system, it is an empty property. 36 * An interrupt generating device that is wired to an AIC.
|
D | allwinner,sun4i-ic.txt | 7 - interrupt-controller : Identifies the node as an interrupt controller 8 - #interrupt-cells : Specifies the number of cells needed to encode an
|
D | nvidia,tegra-ictlr.txt | 19 - interrupt-controller : Identifies the node as an interrupt controller. 20 - #interrupt-cells : Specifies the number of cells needed to encode an 29 - Only SPIs can use the ictlr as an interrupt parent. SGIs and PPIs
|
D | digicolor-ic.txt | 8 - interrupt-controller : Identifies the node as an interrupt controller 9 - #interrupt-cells : Specifies the number of cells needed to encode an
|
/linux-4.1.27/Documentation/devicetree/bindings/net/ |
D | brcm,systemport.txt | 16 - systemport,num-tier2-arb: number of tier 2 arbiters, an integer 17 - systemport,num-tier1-arb: number of tier 1 arbiters, an integer 18 - systemport,num-txq: number of HW transmit queues, an integer 19 - systemport,num-rxq: number of HW receive queues, an integer
|
D | via-velocity.txt | 9 - no-eeprom : PCI network cards use an external EEPROM to store data. Embedded 10 devices quite often set this data in uboot and do not provide an eeprom.
|
/linux-4.1.27/Documentation/hwmon/ |
D | adt7411 | 18 The ADT7411 can use an I2C/SMBus compatible 2-wire interface or an 20 converter which measures 1 temperature, vdd and 8 input voltages. It has an 21 internal temperature sensor, but an external one can also be connected (one
|
D | adm9240 | 42 be read out via an I2C-compatible serial System Management Bus, and values 82 Two fan tacho inputs are provided, the ADM9240 gates an internal 22.5kHz 83 clock via a divider to an 8-bit counter. Fan speed (rpm) is calculated by: 119 An analog output provides a 0 to 1.25 volt signal intended for an external 136 The reading is an unsigned 8-bit value, nominal voltage measurement is 151 Datasheet has an example of an external temperature sensor driving 152 this pin. On an Intel SE440BX-2 the Chassis Intrusion header is 155 The ADM9240 provides an internal open drain on this line, and may output 156 a 20 ms active low pulse to reset an external Chassis Intrusion latch.
|
D | ads7828 | 23 The ads7828 driver accepts an optional ads7828_platform_data structure (defined 30 set to true if it operates with an external reference, false for default 34 if using an external reference, set this to the reference voltage in mV, 52 The chip also has the facility to use an external voltage reference. This
|
D | sch5636 | 15 SMSC SCH5636 Super I/O chips include an embedded microcontroller for 29 The Fujitsu Theseus hwmon solution also contains an integrated watchdog. 32 An application note describing the Theseus' registers, as well as an
|
D | ina2xx | 40 The INA219 is a high-side current shunt and power monitor with an I2C 44 The INA220 is a high or low side current shunt and power monitor with an I2C 47 The INA226 is a current shunt and power monitor with an I2C interface. 51 with an I2C interface. The chips monitor both a shunt voltage drop and
|
D | lm63 | 33 The LM63 is basically an LM86 with fan speed monitoring and control 49 store the value in an 8-bit register and have a selectable clock divider 54 Note that the pin used for fan monitoring is shared with an alert out 72 The LM64 is effectively an LM63 with GPIO lines. The driver does not 75 The LM96163 is an enhanced version of LM63 with improved temperature accuracy
|
D | lm83 | 32 list and an unconfirmed list follow. If you can confirm or infirm the 33 fact that any of these motherboards do actually have an LM83, please 55 secondary chips coupled with another chip such as an IT8705F or similar 61 chip such as the LM83. The only case where using an LM83 would make 63 because you want an additional temperature sensor for each additional
|
/linux-4.1.27/Documentation/devicetree/bindings/pci/ |
D | ralink,rt3883-pci.txt | 12 - #address-cells: specifies the number of cells needed to encode an 16 of an address. The value must be 1. 35 - interrupt-controller: identifies the node as an interrupt controller 37 - #address-cells: specifies the number of cells needed to encode an 41 - #interrupt-cells: specifies the number of cells needed to encode an 55 - #address-cells: specifies the number of cells needed to encode an 59 of an address. The value must be 2. 61 - #interrupt-cells: specifies the number of cells needed to encode an
|
D | xilinx-pcie.txt | 6 - #interrupt-cells: specifies the number of cells needed to encode an 26 - interrupt-controller: identifies the node as an interrupt controller 27 - #address-cells: specifies the number of cells needed to encode an 29 - #interrupt-cells: specifies the number of cells needed to encode an 35 functionality. The driver will create an IRQ domain for this map, decode
|
/linux-4.1.27/Documentation/ia64/ |
D | serial.txt | 11 - Firmware on some machines (mostly from HP) provides an HCDP 25 With an HCDP, device names changed depending on EFI configuration 26 and "console=" arguments. Without an HCDP, device names didn't 29 For example, an HP rx1600 with a single built-in serial port 30 (described in the ACPI namespace) plus an MP[2] (a PCI device) has 62 - Without an HCDP, Linux defaults to a VGA console unless you 77 2.6.10 and later kernels have an "early uart" driver that works 79 this if the user supplies an argument like "console=uart,io,0x3f8", 81 firmware supplies an HCDP. 100 - You're connected to an HP MP port[2] but have a non-MP UART [all …]
|
D | README | 16 Compiling and running this kernel requires an IA-64 compliant GCC 17 compiler. And various software packages also compiled with an 29 the original README for details BUT make sure you have an IA-64
|
/linux-4.1.27/Documentation/cgroups/ |
D | net_prio.txt | 4 The Network priority cgroup provides an interface to allow an administrator to 8 Nominally, an application would set the priority of its traffic via the 13 decision rather than an application defined one. 15 This cgroup allows an administrator to assign a process to a group which defines 29 value that the kernel uses as an internal representation of this cgroup.
|
/linux-4.1.27/Documentation/RCU/ |
D | UP.txt | 11 an idea this is. 16 Suppose that an RCU-based algorithm scans a linked list containing 38 Suppose that an RCU-based algorithm again scans a linked list containing 90 immediately on an UP system. It is also safe for synchronize_rcu() 101 Because the calling function is scanning an RCU-protected linked 102 list, and is therefore within an RCU read-side critical section. 103 Therefore, the called function has been invoked within an RCU 109 Any lock that is acquired within an RCU callback must be 110 acquired elsewhere using an _irq variant of the spinlock 111 primitive. For example, if "mylock" is acquired by an [all …]
|
D | lockdep-splat.txt | 4 family to access an RCU-protected pointer without the proper protection. 5 When such misuse is detected, an lockdep-RCU splat is emitted. 7 The usual cause of a lockdep-RCU slat is someone accessing an 14 So let's look at an example RCU lockdep splat from 3.0-rc5, one that 72 take the struct request_queue "q" from cfq_exit_queue() as an argument, 79 code was invoked either from within an RCU read-side critical section 84 On the other hand, perhaps we really do need an RCU read-side critical 98 With this change, the rcu_dereference() is always within an RCU
|
D | rcubarrier.txt | 14 carefully, leaving an old version of the data structure in place until all 19 How can an RCU writer possibly determine when all readers are finished, 22 pre-existing readers have completed. An updater wishing to delete an 23 element p from a linked list might do the following, while holding an 31 primitive must be used instead. This primitive takes a pointer to an 34 structure. Code to delete an element p from the linked list from IRQ 53 But what if p_callback is defined in an unloadable module? 169 module is an exception to this rule, and therefore needs to set this 200 queues. His implementation queues an RCU callback on each of the per-CPU 230 to post an RCU callback, as follows: [all …]
|
/linux-4.1.27/Documentation/gpio/ |
D | consumer.txt | 26 With the descriptor-based interface, GPIOs are identified with an opaque, 36 device that displays digits), an additional index argument can be specified: 51 Both functions return either a valid GPIO descriptor, or an error code checkable 54 other error codes are used for cases where a GPIO has been assigned but an error 56 errors and an absence of GPIO for optional GPIO parameters. For the common 76 This function returns a struct gpio_descs which contains an array of 122 For an array of GPIOs this function can be used: 128 from an array acquired with gpiod_get_array(). 175 Use the following calls to access GPIOs from an atomic context: 181 of an output pin, the value returned should be what's seen on the pin. That [all …]
|
/linux-4.1.27/net/nfc/nci/ |
D | Kconfig | 7 an NFC Controller (NFCC) and a Device Host (DH). 19 an NFC Controller (NFCC) and a Device Host (DH). 21 Say yes if you use an NCI driver that requires SPI link layer.
|
/linux-4.1.27/drivers/net/ethernet/freescale/fs_enet/ |
D | Kconfig | 12 bool "Chip has an SCC usable for ethernet" 17 bool "Chip has an FCC usable for ethernet" 22 bool "Chip has an FEC usable for ethernet"
|
/linux-4.1.27/Documentation/misc-devices/mei/ |
D | mei-client-bus.txt | 16 Existing device drivers can even potentially be re-used by adding an MEI CL bus layer to 23 A driver implementation for an MEI Client is very similar to existing bus 24 based device drivers. The driver registers itself as an MEI CL bus driver through 51 an Rx event) they can register an event handler through the 53 will trigger an event handler call and the driver implementation is supposed 118 an ME bus event handler which is as close as it can get to registering a
|
/linux-4.1.27/Documentation/devicetree/bindings/arm/omap/ |
D | mpu.txt | 18 - For an OMAP5 SMP system: 25 - For an OMAP4 SMP system: 33 - For an OMAP3 monocore system:
|
/linux-4.1.27/drivers/scsi/arm/ |
D | Kconfig | 9 This enables support for the Acorn SCSI card (aka30). If you have an 40 was either sold on its own or with an integral SCSI controller. 49 This enables support for the Cumana SCSI II card. If you have an 56 This enables support for the EESOX SCSI card. If you have an Acorn 74 This enables support for the Cumana SCSI I card. If you have an 82 This enables support for the Oak SCSI card. If you have an Acorn
|
/linux-4.1.27/Documentation/devicetree/bindings/ |
D | open-pic.txt | 4 representation of an Open PIC compliant interrupt controller. This binding is 20 as an Open PIC. No property value shall be defined. 22 - #interrupt-cells: Specifies the number of cells needed to encode an 25 - #address-cells: Specifies the number of cells needed to encode an 58 // This is an interrupt controller node. 81 * An interrupt generating device that is wired to an Open PIC.
|
D | graph.txt | 8 devices that work together to form a logical compound device, following an 31 Each port node contains an 'endpoint' subnode for each remote device port 33 remote device, an 'endpoint' child node must be provided for each link. 66 All 'port' nodes can be grouped under an optional 'ports' node, which 128 - remote-endpoint: phandle to an 'endpoint' subnode of a remote device node.
|
/linux-4.1.27/Documentation/early-userspace/ |
D | README | 24 two ways to add an early userspace image: specify an existing cpio 38 The kernel build process can also build an early userspace image from 41 built by an unprivileged user. 60 initramfs image will be an aggregate of all of them. In this way a user 65 early userspace image can be built by an unprivileged user. 71 gen_initramfs_list.sh. If a directory is specified as an argument then 74 specified as an argument to scripts/gen_initramfs_list.sh then the 100 - nfsmount, a program that can mount an NFS filesystem. 134 b) some device and filesystem drivers built as modules and stored in an 143 initrd format, an cpio archive. It must be called "/init". This binary [all …]
|
/linux-4.1.27/Documentation/devicetree/bindings/media/ |
D | si4713.txt | 3 The Silicon Labs Si4713 is an FM radio transmitter with receive power scan 4 supporting 76-108 MHz. It includes an RDS encoder and has both, a stereo-analog 6 DSP-mode format. It is programmable through an I2C interface.
|
D | video-interfaces.txt | 7 controlled over an I2C, SPI or UART bus, and SoC internal IP blocks, including 34 bus, an 'endpoint' child node must be provided for each of them. If more than 73 - remote-endpoint: phandle to an 'endpoint' subnode of a remote device node. 93 - data-lanes: an array of physical data lane indexes. Position of an entry 94 determines the logical lane number, while the value of an entry indicates 98 - clock-lanes: an array of physical clock lane indexes. Position of an entry 99 determines the logical lane number, while the value of an entry indicates 109 - lane-polarities: an array of polarities of the lanes starting from the clock 186 vsync-active = <0>; /* Who came up with an
|
D | exynos-fimc-lite.txt | 15 Each FIMC device should have an alias in the aliases node, in the form of 16 fimc-lite<n>, where <n> is an integer specifying the IP block instance.
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-bus-rpmsg | 20 and remote ("destination") rpmsg address. When an entity 27 of this channel. If it contains 0xffffffff, then an address 38 and remote ("destination") rpmsg address. When an entity 45 of this channel. If it contains 0xffffffff, then an address 64 A channel is first created when an entity, whether local 66 called an rpmsg server).
|
D | sysfs-class-extcon | 27 object. If the extcon object has an optional callback 37 If the extcon object has an optional callback "show_state" 52 In order to update the state of an extcon device, enter a hex 63 multiple cable states of an extcon device simultaneously. 70 "x" (integer between 0 and 31) of an extcon device. 77 state of cable "x" (integer between 0 and 31) of an extcon
|
D | sysfs-firmware-acpi | 5 The BGRT is an ACPI 5.0 feature that allows the OS 43 The value of the above attribute is an integer number: 1 (set) 78 to a Linux device driver registered on an ACPI device, 131 has been called and claimed an interrupt. 134 has been called and NOT claimed an interrupt. 150 error - an interrupt that can't be accounted for above. 153 doesn't have an event handler. 165 None of these counters has an effect on the function 195 * and it triggers an ACPI fixed event when the enable bit is set again
|
D | sysfs-class-net | 7 1: enumerated by the kernel, possibly in an unpredictable way 39 Format is a string, e.g: 00:11:22:33:44:55 for an Ethernet MAC 48 string, e.g: ff:ff:ff:ff:ff:ff for an Ethernet broadcast MAC 70 Indicates the device unique identifier. Format is an hexadecimal 117 Indicates/stores an interface alias name as a string. This can 126 decimal number. This attribute is used for mapping an interface 127 identifier to an interface name. It is used throughout the 205 an integer representing the link speed in Mbits/sec. 216 as an integer value. Value depend on the type of interface,
|
D | sysfs-bus-iio-trigger-sysfs | 6 driver. Writing this file with any value triggers an event 8 into an in kernel buffer. This approach can be valuable during
|
D | sysfs-kernel-iommu_groups | 6 directories, each representing an IOMMU group. The 8 for the group, which is an integer value. Within each
|
D | sysfs-driver-ppi | 25 This attribute shows the request for an operation to be 27 the OS to the pre-OS environment. The request should be an 54 This attribute shows whether it is allowed to request an 65 This attribute shows whether it is allowed to request an
|
D | sysfs-class-rc | 33 Write fails with EINVAL if an invalid protocol combination or 46 an error. 61 an error. 79 Write fails with EINVAL if an invalid protocol combination or 95 Otherwise the write will fail with an error. 110 Otherwise the write will fail with an error.
|
D | sysfs-devices-lpss_ltr | 14 The /sys/devices/.../lpss_ltr/ltr_mode attribute contains an 28 represented as an 8-digit hexadecimal number. 40 as an 8-digit hexadecimal number.
|
/linux-4.1.27/Documentation/xtensa/ |
D | atomctl.txt | 5 1. With and without an Coherent Cache Controller which 15 On the FPGA Cards we typically simulate an Intelligent Memory controller 16 which can implement RCW transactions. For FPGA cards with an External 21 For systems without an coherent cache controller, non-MX, we always
|
/linux-4.1.27/arch/m68k/fpsp040/ |
D | gen_except.S | 10 | Any routine which may report an exceptions must load 95 | Frame is an unimp frame possible resulting from an fmove <ea>,fp0 96 | that caused an exception 167 | The typical work to be done to the unimp frame to report an 219 | ;it is an unsupp or unimp exc 239 | An fmoveout that results in an overflow is reported this way. 241 | An fmoveout that results in an underflow is reported this way. 250 | x is an extended denorm can report an underflow exception. 260 | The caller was from an unsupported data type trap. Test if the 324 | instruction in an emulation routine caused the exception [all …]
|
/linux-4.1.27/Documentation/power/ |
D | swsusp-dmcrypt.txt | 11 You did read Documentation/initrd.txt and know how an initrd works. 12 You know how to create or how to modify an initrd. 17 an initrd that does your current crypto setup already. 22 the key(s) from an external device like a pcmcia flash disk 23 or an usb stick prior to resume. So you need an initrd, that sets 51 you create an initrd that reads the required dm-crypt setup 52 from a pcmcia flash disk card. The card is formatted with an ext2 62 /dev/hda1 contains an unencrypted mini system that sets up all
|
D | opp.txt | 17 1.1 What is an Operating Performance Point (OPP)? 20 In an operational system executing varied use cases, not all modules in the SoC 30 As an example: 31 Let us consider an MPU device which supports the following: 56 list is expected to be an optimally small number typically around 5 per device. 73 be used for dev_pm_opp_enable/disable functions to make an opp available as required. 140 dev_pm_opp_find_freq_exact - Search for an OPP based on an *exact* frequency and 141 availability. This function is especially useful to enable an OPP which 160 dev_pm_opp_find_freq_floor - Search for an available OPP which is *at most* the 170 dev_pm_opp_find_freq_ceil - Search for an available OPP which is *at least* the [all …]
|
/linux-4.1.27/Documentation/PCI/ |
D | pcieaer-howto.txt | 69 When a PCI-E AER error is captured, an error message will be outputted to 71 Otherwise, it is printed as an error. So users could choose different 74 Below shows an example: 110 When AER is enabled, a PCI Express device will automatically send an 112 an error. The Root Port, upon receiving an error reporting message, 118 Error Command Register, the Root Port generates an interrupt if an 177 If an error message indicates a non-fatal error, performing link reset 182 If Upstream port A captures an AER error, the hierarchy consists of 189 If an error message indicates a fatal error, kernel will broadcast 195 component has an aer driver. If it has, kernel uses the reset_link [all …]
|
/linux-4.1.27/drivers/staging/nvec/ |
D | README | 3 This is an implementation of the NVEC protocol used to communicate with an 4 embedded controller (EC) via I2C bus. The EC is an I2C master while the host
|
/linux-4.1.27/Documentation/devicetree/ |
D | overlay-notes.txt | 16 in an active device should have it created while if the device node is either 19 Lets take an example where we have a foo board with the following base tree 92 1. Call of_overlay_create() to create and apply an overlay. The return value 96 created via the call to of_overlay_create(). Removal of an overlay that 106 The DTS of an overlay should have the following format: 119 node-a { /* add to an existing, or create a node-a */
|
D | usage-model.txt | 15 is a description of hardware that is readable by an operating system 20 nodes may have an arbitrary number of named properties encapsulating 43 program (like to an operating system). An operating system used the 117 with the exact name of the machine, followed by an optional list of 183 of an initrd image. 195 properties define the address and size of an initrd blob. Note that 198 optionally contain an arbitrary number of additional properties for 253 About now is a good time to lay out an example. Here is part of the 325 devices, but the codec@1a is an i2c device, and the sound node 343 example, each i2c_client is a child of an i2c_master. Each spi_device [all …]
|
/linux-4.1.27/Documentation/device-mapper/ |
D | dm-io.txt | 5 types of I/O services available, and each type has a sync and an async 8 The user must set up an io_region structure to describe the desired location 19 to multiple regions are specified by an array of io_region structures. 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 64 In the case of an write-I/O to multiple regions, this bitset allows dm-io to
|
D | thin-provisioning.txt | 12 Another significant feature is support for an arbitrary depth of 17 with depth. Fragmentation may still be an issue, however, in some 67 data device. If you do not have an existing metadata device you can 94 Using an existing pool device 115 Resuming a device with a new table itself triggers an event so the 153 To create a new thinly- provisioned volume you must send a message to an 158 Here '0' is an identifier for the volume, a 24-bit number. It's up 173 i) Creating an internal snapshot. 188 ii) Using an internal snapshot. 205 You can use an external _read only_ device as an origin for a [all …]
|
/linux-4.1.27/arch/mips/netlogic/ |
D | Kconfig | 9 Add an FDT blob for XLP EVP boards into the kernel. 19 Add an FDT blob for XLP VP boards into the kernel. 29 Add an FDT blob for XLP FVP board into the kernel. 39 Add an FDT blob for XLP GVP board into the kernel. 48 Add an FDT blob for XLP RVP board into the kernel.
|
/linux-4.1.27/Documentation/rapidio/ |
D | rapidio.txt | 28 Each of these components is represented in the subsystem by an associated data 39 host device ID that is valid when a master port is configured as an enumerating 59 switch is defined by an internal routing table. A switch is presented in the 101 an enumeration and/or discovery routine may be called automatically or 120 several methods to initiate an enumeration and/or discovery process: 140 endpoints have been successfully booted, an enumeration process shall be 141 started first by issuing a user-space command, after an enumeration is 145 user space. After an enumeration/discovery module is loaded, a network scan 147 Similar to the option (b) above, an enumerator has to be started first. 150 initialization routine. In this case an enumerating module shall be loaded [all …]
|
/linux-4.1.27/Documentation/arm/nwfpe/ |
D | NOTES | 8 often uses an stfe instruction to save f4 on the stack upon entry to a 9 function, and an ldfe instruction to restore it before returning. 13 f4 had been converted to an extended value in the emulator. 16 converted to extended, then stored. If an lfm/sfm combination had been used,
|
/linux-4.1.27/Documentation/parisc/ |
D | debugging | 9 rest of the kernel. To translate an absolute address to a virtual 17 an HPMC instead of a kernel oops. To debug an HPMC, try to find 34 was interrupted - so if you get an interruption between the instruction
|
/linux-4.1.27/Documentation/i2c/busses/ |
D | i2c-piix4 | 38 The PIIX4 (properly known as the 82371AB) is an Intel chip with a lot of 46 Do 'lspci -v' and see whether it contains an entry like this: 54 find such an entry, you have a PIIX4 SMBus controller. 69 The PIIX4E is just an new version of the PIIX4; it is supported as well. 70 The PIIX/PIIX3 does not implement an SMBus or I2C bus, so you can't use 79 an "Auxiliary SMBus Host Controller". 102 This driver will refuse to load on IBM systems with an Intel PIIX4 SMBus. 103 Some of these machines have an RFID EEPROM (24RF08) connected to the SMBus,
|
/linux-4.1.27/Documentation/hid/ |
D | uhid.txt | 5 hid-transport.txt for an introduction into HID transport drivers. This document 12 There is an example user-space application in ./samples/uhid/uhid-example.c 47 The first thing you should do is sending an UHID_CREATE2 event. This will 48 register the device. UHID will respond with an UHID_START event. You can now 53 user closes the HID device, you will receive an UHID_CLOSE event. This may be 54 followed by an UHID_OPEN event again and so on. There is no need to perform 56 UHID_OPEN events without an UHID_CLOSE event. The HID subsystem performs 62 an HID_INPUT2 event with your raw data payload. If the kernel wants to send data 63 on the interrupt channel to the device, you will read an UHID_OUTPUT event. 73 If your device disconnects, you should send an UHID_DESTROY event. This will [all …]
|
D | hid-sensor.txt | 35 The report is indicating "sensor page (0x20)" contains an accelerometer-3D (0x73). 47 for different sensors. For example an accelerometer can send X,Y and Z data, whereas 48 an ambient light sensor can send illumination data. 56 report descriptors and identifies all the sensors present. It adds an MFD device 59 HID-SENSOR-200073 is registered for an Accelerometer 3D driver. 61 function will be called. So an accelerometer processing driver can register 62 with this name and will be probed if there is an accelerometer-3D detected. 70 The processing driver will use an interface provided by the core driver to parse 91 Registers callbacks for an usage id. The callback functions are not allowed 98 Removes callbacks for an usage id. [all …]
|
/linux-4.1.27/scripts/coccinelle/misc/ |
D | bugon.cocci | 3 //# This makes an effort to find cases where BUG() follows an if 4 //# condition on an expression and replaces the if condition and BUG()
|
D | ifcol.cocci | 1 /// Find confusingly indented code in or after an if. An if branch should 2 /// be indented. The code following an if should not be indented. 3 /// Sometimes, code after an if that is indented is actually intended to be
|
/linux-4.1.27/fs/affs/ |
D | Kconfig | 7 if you want to be able to read and write files from and to an Amiga 9 read with this driver due to an incompatibility of the floppy 10 controller used in an Amiga and the standard floppy controller in
|
/linux-4.1.27/Documentation/acpi/ |
D | method-customizing.txt | 10 1. override an existing method which may not work correctly, 25 1. override an existing method 30 d) package the new file (psr.asl) to an ACPI table format. 31 Here is an example of a customized \_SB._AC._PSR method, 53 This is easier than overriding an existing method. 60 For an overrided method, in order to undo your changes, please
|
/linux-4.1.27/Documentation/blockdev/ |
D | ramdisk.txt | 16 is required for initrd, an initial filesystem used if you need to load modules 26 to support an unlimited number of RAM disks (at your own risk). Just change 32 for /dev/ram0, etc. If used, modern kernels use /dev/ram0 for an initrd. 35 allowing one to squeeze more programs onto an average installation or 68 as follows. The low 11 bits (0 -> 10) specify an offset (in 1 k blocks) of up 84 starts at an offset of 0 kB from the beginning of the floppy. 94 Putting that together gives 2^15 + 2^14 + 0 = 49152 for an rdev word. 111 construct it on. This can be the RAM disk device itself, or an 112 unused disk partition (such as an unmounted swap partition). For this 144 f) Put the RAM disk image onto the floppy, after the kernel. Use an offset
|
/linux-4.1.27/Documentation/devicetree/bindings/arm/mrvl/ |
D | intc.txt | 15 - interrupt-controller : Identifies the node as an interrupt controller. 16 - #interrupt-cells : Specifies the number of cells needed to encode an 46 - #interrupt-cells: Specifies the number of cells needed to encode an 48 - interrupt-controller : Declare this node to be an interrupt controller.
|
/linux-4.1.27/Documentation/w1/masters/ |
D | omap-hdq | 10 http://focus.ti.com/lit/an/slua408a/slua408a.pdf 26 create an initialization pulse to the slave.However, the slave can be reset by 27 using an initialization pulse (also referred to as a break pulse).The slave 35 be used to calculate the CRC and pass back an appropriate slave ID to the W1
|
/linux-4.1.27/arch/x86/math-emu/ |
D | README | 2 | wm-FPU-emu an FPU emulator for 80386 and 80486SX microprocessors. | 25 wm-FPU-emu is an FPU emulator for Linux. It is derived from wm-emu387 77 even for arguments approaching 2^63. This is far superior to an 111 be different from that obtained with an 80486. This occurs when the 126 and Unnormals. None of these will be generated by an 80486 or by the 128 detail from the way an 80486 does. 141 an 80486DX. 154 an 80486DX. A 80486DX will allow some floating point instructions to 229 than that of an Intel 80486 FPU. 232 match those of an 80486 FPU. They are the best possible; the error for [all …]
|
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
D | S3C2413.txt | 7 The S3C2413 is an extended version of the S3C2412, with an camera
|
D | Suspend.txt | 56 Note, the original method of adding an late_initcall() is wrong, 59 The following is an example of code used for testing wakeup from 60 an falling edge on IRQ_EINT0: 120 and the size of memory. For an 64Mbyte RAM area on an 200MHz
|
/linux-4.1.27/Documentation/devicetree/bindings/spi/ |
D | nvidia,tegra114-spi.txt | 11 - resets : Must contain an entry for each entry in reset-names. 15 - dmas : Must contain an entry for each entry in clock-names. 20 - clocks : Must contain an entry for each entry in clock-names.
|
/linux-4.1.27/Documentation/devicetree/bindings/ata/ |
D | tegra-sata.txt | 11 - clocks : Must contain an entry for each entry in clock-names. 18 - resets : Must contain an entry for each entry in reset-names. 24 - phys : Must contain an entry for each entry in phy-names.
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
D | msi-pic.txt | 16 register for platforms that have such an alias, if using MSIIR1, the second 34 no splitting an individual MSI register or the associated PIC interrupt). 35 MPIC v4.3 does not support this property because the 32 interrupts of an 43 has created an alternate mapping for the MSIR block. See below for an 88 Normally, PCI devices have access to all of CCSR via an ATMU mapping. The 92 In a virtualized environment, the hypervisor may need to create an IOMMU
|
/linux-4.1.27/drivers/gpu/drm/atmel-hlcdc/ |
D | Kconfig | 10 Choose this option if you have an ATMEL SoC with an HLCDC display
|
/linux-4.1.27/arch/frv/kernel/ |
D | break.S | 92 # determine whether we have stepped through into an exception 252 # step through an internal exception from kernel mode 259 # step through an external interrupt from kernel mode 305 # we single-stepped into an interrupt handler whilst interrupts were merely virtually disabled 336 # we also want to single step anyway, but after fixing up so that we get an event on the 363 # step through an internal exception from uspace mode 370 # step through an external interrupt from kernel mode 409 # step through an ITLB-miss handler from user mode 439 # to get a BREAK fault not an access violation should the return be to userspace
|
/linux-4.1.27/Documentation/filesystems/nfs/ |
D | knfsd-stats.txt | 50 (e.g. an NFS or UDP socket or an NFS/RDMA endpoint). 61 Counts how many times an NFS transport is enqueued to wait for 62 an nfsd thread to service it, i.e. no nfsd thread was considered 83 Counts how many times an idle nfsd thread is woken to try to 84 receive some data from an NFS transport. 92 Counts how many times the sunrpc server layer chose not to wake an 122 Counts how many times an nfsd thread triggered an idle timeout, 146 deferred because the transport is currently being used by an nfsd
|
D | rpc-cache.txt | 26 - allowing an EXPIRED time on cache items, and removing 41 as an element, usually the first. 55 This is called when the last reference to an item is 77 Format a request to be send to user-space for an item 105 if the data is valid, and may initiate an up-call to get fresh data. 106 cache_check will return -ENOENT in the entry is negative or if an up 107 call is needed but not possible, -EAGAIN if an upcall is pending, 123 saves any user of an item from worrying about content changing while 143 - an expiry time 145 with the intention that an item in the cache with the give key [all …]
|
/linux-4.1.27/Documentation/input/ |
D | ff.txt | 38 There is an utility called fftest that will allow you to test the driver. 103 some operations (removing an effect, controlling the playback). 113 3.3 Removing an effect from the device 122 Control of playing is done with write(). Below is an example: 141 /* Stop an effect */ 168 and I think it should be an effect, which computation depends on the game 183 3.7 Dynamic update of an effect 189 the direction of an effect cannot be updated with iforce devices. In this 197 Every time the status of an effect is changed, an event is sent. The values
|
D | xpad.txt | 23 - if using an unknown device (one not listed below), what you set in the 27 If you set dpad_to_buttons to N and you are using an unknown device 78 If you have an unknown xbox controller, it should work just fine with 81 HOWEVER if you have an unknown dance pad not listed below, it will not 84 PLEASE, if you have an unknown controller, email Dom <binary1230@yahoo.com> with 106 Using this driver with an Original Xbox controller requires an 121 original one. You can buy an extension cable and cut that instead. That way, 131 /proc/bus/usb/devices. There should be an entry like the one at the end [4]. 152 If you have an unrecognized controller please see 0.3 - Unknown Controllers
|
/linux-4.1.27/arch/ |
D | Kconfig | 26 between events at an user specified time interval. 111 This symbol should be selected by an architecture if 64 bit 127 This symbol should be selected by an architecture if it can 227 This symbol should be selected by an architecure if it supports 262 System hardware can generate an NMI using the perf event 326 For best performance, an arch should use seccomp_phase1 and 333 As an additional optimization, an arch may provide seccomp_data 383 have an 8-byte or larger character array on the stack. 388 On an x86 "defconfig" build, this feature adds canary checks to 399 - local variable's address used as part of the right hand side of an [all …]
|
/linux-4.1.27/arch/arm64/ |
D | Kconfig | 229 but contains an NVIDIA Denver CPU complex in place of 296 This option adds an alternative code sequence to work around ARM 297 erratum 826319 on Cortex-A53 parts up to r0p2 with an AMBA 4 ACE or 298 AXI master interface and an L2 cache. 300 If a Cortex-A53 uses an AMBA AXI4 ACE interface to other processors 309 the kernel if an affected CPU is detected. 317 This option adds an alternative code sequence to work around ARM 318 erratum 827319 on Cortex-A53 parts up to r0p2 with an AMBA 5 CHI 319 master interface and an L2 cache. 330 the kernel if an affected CPU is detected. [all …]
|
/linux-4.1.27/Documentation/devicetree/bindings/media/i2c/ |
D | nokia,smia.txt | 3 SMIA (Standard Mobile Imaging Architecture) is an image sensor standard 4 defined jointly by Nokia and ST. SMIA++, defined by Nokia, is an extension 15 - reg: I2C address (0x10, or an alternative address)
|
/linux-4.1.27/Documentation/devicetree/bindings/sound/ |
D | qcom,lpass-cpu.txt | 8 - clocks : Must contain an entry for each entry in clock-names. 13 - interrupts : Must contain an entry for each entry in 21 - reg : Must contain an address for each entry in reg-names.
|
D | fsl,ssi.txt | 16 field that represents an encoding of the sense and 50 - codec-handle: Phandle to a 'codec' node that defines an audio 52 a child of an I2C or other control node. 55 where an incompatible codec is connected to this SSI, e.g. 70 from an on-board dedicated oscillator. 74 On SOCs that have an SSI, specific DMA channels are hard-wired for playback
|
D | nvidia,tegra30-ahub.txt | 11 - Tegra114 requires an additional entry, for the APBIF2 register block. 13 - clocks : Must contain an entry for each entry in clock-names. 18 - resets : Must contain an entry for each entry in reset-names. 47 - dmas : Must contain an entry for each entry in clock-names.
|
/linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
D | twl-familly.txt | 6 These chips are connected to an i2c bus. 15 - interrupts : This i2c device has an IRQ line connected to the main SoC 17 it is considered as an interrupt controller cascaded to the SoC one.
|
/linux-4.1.27/Documentation/devicetree/bindings/metag/ |
D | meta-intc.txt | 15 as an interrupt controller. No property value shall be defined. 17 - #interrupt-cells: Specifies the number of cells needed to encode an 20 - #address-cells: Specifies the number of cells needed to encode an 47 // This is an interrupt controller node.
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
D | cpm.txt | 3 NOTE: This is an interim binding, and will likely change slightly, 28 is associated with. If absent, an unused BRG 30 device uses an external clock rather than a BRG. 54 purposes. The data node may have an arbitrary number of reg resources,
|
/linux-4.1.27/Documentation/driver-model/ |
D | design-patterns.txt | 40 This will create an instance of struct foo in memory every time probe() is 45 For example, if the driver is registering an interrupt handler, you would 69 Continuing on the above example we add an offloaded work: 102 The design pattern is the same for an hrtimer or something similar that will 111 Notice that the contained member must not be a pointer, but an actual member
|
/linux-4.1.27/drivers/staging/iio/Documentation/ |
D | device.txt | 3 This is not intended to provide a comprehensive guide to writing an 45 is used to read if an on sensor event detector is enabled. 47 Enable / disable an on sensor event detector. 54 a threshold above which an interrupt occurs. Note that the 63 to which this device is attached sends an event.
|
/linux-4.1.27/Documentation/s390/ |
D | zfcpdump.txt | 8 dump tool is loaded. There exists an SCLP hardware interface to obtain the saved 19 which exports memory and registers of the crashed Linux in an s390 42 The user space application of zfcpdump can reside in an intitramfs or an 46 The s390-tools package version 1.24.0 and above builds an external zfcpdump
|
/linux-4.1.27/drivers/net/ethernet/8390/ |
D | Kconfig | 25 Say Y here if you intend to attach an Asix AX88190-based PCMCIA 48 Select this if your platform comes with an external 93CX6 eeprom. 65 If you have an Acorn system with one of these network cards, you 74 Ethernet cards using an NS8390 chipset or its equivalent, say Y 83 This driver is for Ethernet devices using an NS8390-compatible 144 Say Y here if you intend to attach an NE2000 compatible PCMCIA 172 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible, 198 This driver is for Zorro Ethernet cards using an NS8390-compatible
|
/linux-4.1.27/drivers/staging/olpc_dcon/ |
D | Kconfig | 13 completely powered off while still retaining an image on the display. 24 have an XO-1 (or if you're unsure what model you have), you should 34 have an XO-1.5 (or if you're unsure what model you have), you
|
/linux-4.1.27/Documentation/block/ |
D | stat.txt | 38 These values increment when an I/O request completes. 43 These values increment when an I/O request is merged with an 60 example, if 60 read requests wait for an average of 30 ms, the read_ticks 82 number of requests waiting (see "read ticks" above for an example).
|
D | writeback_cache_control.txt | 13 a data integrity operation like fsync, sync or an unmount. 28 set on an otherwise empty bio structure, which causes only an explicit cache 78 of an empty REQ_FLUSH request followed by the actual write by the block 86 layer turns it into an empty REQ_FLUSH request after the actual write.
|
/linux-4.1.27/drivers/media/firewire/ |
D | Kconfig | 8 These devices don't have an MPEG decoder built in, 9 so you need an external software decoder to watch TV.
|
/linux-4.1.27/drivers/mtd/onenand/ |
D | Kconfig | 15 This adds an extra check when data is written to the flash. The 30 Support for a OneNAND flash device connected to an OMAP2/OMAP3 CPU 37 Support for a OneNAND flash device connected to an Samsung SOC. 57 The 2X Program is an extension of Program Operation.
|
/linux-4.1.27/Documentation/devicetree/bindings/rtc/ |
D | isil,isl12057.txt | 4 consisting of a compatible field, an address and possibly an interrupt 7 Nonetheless, it also supports an option boolean property 26 independently of the availability of an IRQ line connected to the
|
/linux-4.1.27/Documentation/watchdog/ |
D | pcwd-watchdog.txt | 8 the WDT card does, only it doesn't require an IRQ to run. Furthermore, 22 I suggest putting a "watchdog -d" before the beginning of an fsck, and 23 a "watchdog -e -t 1" immediately after the end of an fsck. (Remember 24 to run the program with an "&" to run it in the background!)
|
/linux-4.1.27/drivers/nfc/ |
D | Kconfig | 45 This adds support to use an mei bus nfc device. Select this if you 46 will use an HCI NFC driver for an NFC chip connected behind an
|
/linux-4.1.27/Documentation/devicetree/bindings/cris/ |
D | interrupts.txt | 9 - interrupt-controller : Identifies the node as an interrupt controller 10 - #interrupt-cells : Specifies the number of cells needed to encode an
|
/linux-4.1.27/Documentation/devicetree/bindings/thermal/ |
D | tegra-soctherm.txt | 6 notifications. It is also used to manage emergency shutdown in an 16 - clocks : Must contain an entry for each entry in clock-names. 21 - resets : Must contain an entry for each entry in reset-names.
|
/linux-4.1.27/drivers/usb/usbip/ |
D | usbip_protocol.txt | 9 client opens a TCP/IP connection towards the server, and sends an OP_REQ_DEVLIST 28 sends an OP_REQ_IMPORT packet. The server replies with OP_REP_IMPORT. If the 31 send two types of packets: the USBIP_CMD_SUBMIT to submit an URB, and 236 USBIP_CMD_SUBMIT: Submit an URB 240 0 | 4 | 0x00000001 | command: Submit an URB 257 | | | transmit an ISO frame, ignored if URB_ISO_ASAP 284 USBIP_RET_SUBMIT: Reply for submitting an URB 304 0x1C | 4 | | start_frame: for an ISO frame the actually 317 USBIP_CMD_UNLINK: Unlink an URB
|
/linux-4.1.27/Documentation/scsi/ |
D | scsi_mid_low_api.txt | 17 In some cases the SCSI transport is an external bus that already has 35 The SCSI mid level isolates an LLD from other layers such as the SCSI 60 Traditionally an LLD for the SCSI subsystem has been at least two files in 100 "struct scsi_host_template", an instance of which is passed to 103 struct scsi_host_template. Defining an instance of struct 111 All functions defined within an LLD and all data defined at file scope 112 should be static. For example the slave_alloc() function in an LLD 124 In this model an LLD controls when SCSI hosts are introduced and removed 127 will respond to a sysfs probe() callback that indicates an HBA has been 137 aware of an LLD when that LLD registers its first HBA. [all …]
|
/linux-4.1.27/drivers/sn/ |
D | Kconfig | 17 If you have an SGI Altix with an IOC3-based
|
/linux-4.1.27/Documentation/kbuild/ |
D | modules.txt | 3 This document describes how to build an out-of-tree kernel module. 13 === 3. Creating a Kbuild File for an External Module 44 in building out-of-tree (or "external") modules. The author of an 70 The command to build an external module is: 74 The kbuild system knows that an external module is being built 98 Informs kbuild that an external module is being built. 105 When building an external module, only a subset of the "make" 146 === 3. Creating a Kbuild File for an External Module 159 When the module is built from multiple sources, an additional line is 265 allows an older version of kbuild, which only knows of [all …]
|
/linux-4.1.27/drivers/pci/ |
D | Kconfig | 15 generate an interrupt using an inbound Memory Write on its 100 behind an IOMMU to recover from page faults. 111 use of this feature an IOMMU is required which also supports PASIDs. 112 Select this option if you have such an IOMMU and want to compile the
|
/linux-4.1.27/Documentation/isdn/ |
D | README | 60 A low-level-driver can register itself through an interface (which is 224 an incoming call happened (RING) and 289 When an incoming call is detected, the driver looks first for a network 290 interface and then for an opened tty which: 308 For an outgoing call, the inactive physical lines are searched. 315 If an incoming call matches one network interface, it gets connected to it. 352 an AT&W0 is performed on any ISDN-tty. If the file already exists, 356 d) For networking, continue: Create an interface: 394 isdn0". However, after an idle time of no traffic as configured for 413 Now you are ready! A ping to the set address should now result in an [all …]
|
/linux-4.1.27/arch/arm/lib/ |
D | ecard.S | 20 @ Purpose: call an expansion card loader to read bytes. 33 @ Purpose: call an expansion card loader to reset the card
|
/linux-4.1.27/Documentation/devicetree/bindings/media/xilinx/ |
D | video.txt | 8 Each video IP core is represented by an AMBA bus child node in the device 12 The whole pipeline is represented by an AMBA bus child node in the device 20 - xlnx,video-format: This property represents a video format transmitted on an
|
/linux-4.1.27/Documentation/devicetree/bindings/phy/ |
D | phy-bindings.txt | 29 That node describes an IP block (PHY provider) that implements 2 different PHYs. 30 In order to differentiate between these 2 PHYs, an additional specifier should be 69 device defined previously. Note that the phy handle has an additional specifier
|
/linux-4.1.27/drivers/staging/ozwpan/ |
D | README | 3 This driver is a USB HCD driver that does not have an associated a physical 6 on the network using an ethertype (0x892e) regestered to Ozmo Device Inc. 13 loading using an ioctl call. See the ozappif.h file and the ioctls
|
/linux-4.1.27/drivers/media/platform/s5p-tv/ |
D | Kconfig | 29 as module. It is an auxiliary driver, that exposes a V4L2 47 as module. It is an I2C driver, that exposes a V4L2 57 as module. It is an I2C driver, that exposes a V4L2 67 as module. It is an auxiliary driver, that exposes a V4L2
|
/linux-4.1.27/arch/mips/dec/ |
D | int-handler.S | 162 # irq_nr < 0: it is an address 211 # irq_nr < 0: it is an address 291 move a1,t0 # cheats way of printing an arg! 295 move a1,t0 # cheats way of printing an arg!
|
/linux-4.1.27/arch/powerpc/platforms/embedded6xx/ |
D | Kconfig | 29 with an 8241 CPU in it. 47 Select PPC_HOLLY if configuring for an IBM 750GX/CL Eval 58 an SBS board). 96 USB Gecko adapter as an udbg console.
|
/linux-4.1.27/Documentation/scheduler/ |
D | sched-arch.txt | 11 the context switch. See arch/ia64/include/asm/switch_to.h for an example. 38 need_resched, it prevents losing an interrupt). 49 need an interrupt to wake them up when need_resched goes high. 55 an interrupt sleep, it needs to be cleared then a memory
|
/linux-4.1.27/Documentation/devicetree/bindings/iio/ |
D | iio-bindings.txt | 7 outputs to IIO inputs. Similar to the gpio specifiers, an IIO 8 specifier is an array of one or more cells identifying the IIO 9 output on a device. The length of an IIO specifier is defined by the 17 #io-channel-cells: Number of cells in an IIO specifier; Typically 0 for nodes
|
/linux-4.1.27/Documentation/x86/x86_64/ |
D | kernel-stacks | 35 (IST). There can be up to 7 IST entries per CPU. The IST code is an 39 An IST is selected by a non-zero value in the IST field of an 40 interrupt-gate descriptor. When an interrupt occurs and the hardware 50 nested. For example, a debug interrupt can safely be interrupted by an 54 stack size allocated to an IST assumes no nesting for the same code. 73 in many cases to still output an oops.
|
/linux-4.1.27/drivers/input/mouse/ |
D | Kconfig | 46 Say Y here if you have an ALPS PS/2 touchpad connected to 96 Say Y here if you have an IBM Trackpoint PS/2 mouse connected 105 Say Y here if you have an Elantech PS/2 touchpad connected 127 Say Y here if you have an eGalax TouchKit PS/2 touchscreen 136 Say Y here if you have an OLPC XO-1 laptop (with built-in 138 touchpad an HGPK. 160 load in the presence of an in-kernel vmmouse driver. 182 Say Y here if you want to use an Apple USB Touchpad. 203 Say Y here if you have an Apple USB BCM5974 Multitouch 268 Say Y here if you have an InPort, Microsoft or ATI XL busmouse. [all …]
|
/linux-4.1.27/drivers/staging/i2o/ |
D | README.ioctl | 50 Returns 0 if no errors occur, and -1 otherwise. If an error occurs, 76 This function returns 0 if no errors occur. If an error occurs, -1 105 This function returns 0 if no errors occur. If an error occurs, -1 140 ops->resbuf if no errors occur. If an error occurs, -1 is returned 224 This function returns 0 no errors occur. If an error occurs, -1 266 This function returns 0 if no errors occur. If an error occurs, -1 303 This function returns 0 if no errors occur. If an error occurs, -1 320 This function posts an ExecConfigValidate message to the controller 327 This function returns 0 if no erro occur. If an error occurs, -1 is 351 This function posts an UtilConfigDialog message to the device identified [all …]
|
/linux-4.1.27/Documentation/timers/ |
D | timers-howto.txt | 16 code in an atomic context?" This should be followed closely by "Does 63 for usleep *may* not be worth it. Such an evaluation 87 worst case, fire an interrupt for your upper bound. 90 that you will not trigger an interrupt; this should 91 be balanced with what is an acceptable upper bound on
|
/linux-4.1.27/Documentation/sound/alsa/soc/ |
D | overview.txt | 15 Headphone/Mic insertion, Headphone/Mic detection after an insertion 17 machine specific code to re-route audio, enable amps, etc., after such an 52 To achieve all this, ASoC basically splits an embedded audio system into 66 decribes and binds the other component drivers together to form an ALSA 68 machine level audio events (e.g. turning on an amp at start of playback).
|
/linux-4.1.27/Documentation/devicetree/bindings/timer/ |
D | brcm,bcm2835-system-timer.txt | 4 single 64-bit free running counter. Each channel has an output compare 6 free running counter values, and generates an interrupt.
|
/linux-4.1.27/Documentation/video4linux/bttv/ |
D | README.WINVIEW | 6 GPIO lines in order to give some volume control. They have also stuck an 8 when I get time (it simple generates an interrupt for each key press, with 18 use this driver, send an email insult to them, and tell them you won't
|
/linux-4.1.27/net/x25/ |
D | Kconfig | 25 One connects to an X.25 network either with a dedicated network card 27 X.25 over a standard telephone line using an ordinary modem (say Y 28 to "X.25 async driver" below) or over Ethernet using an ordinary
|
/linux-4.1.27/Documentation/devicetree/bindings/mtd/ |
D | partition.txt | 3 Partitions can be represented by sub-nodes of an mtd device. This can be used 5 used for what purposes, but which don't use an on-flash partition table such 60 /* an 8 GiB partition */
|
/linux-4.1.27/arch/blackfin/ |
D | Kconfig.debug | 10 When a program crashes due to an exception, or the kernel detects 11 an internal error, the kernel can print a not so brief message 33 will happen immediately when an error condition occurs. This comes 55 If an exception is caused while executing code within the exception 67 - The EXCAUSE field is updated with an unrecoverable event 100 Enabling this option will take up an extra entry in CPLB table. 110 can be handy when an application dies - we print out the execution 164 into a software buffer, for dumping when there is an issue. This 165 has a great impact on performance, (an interrupt every 16 change of 191 space when in reality an application is buggy.
|
/linux-4.1.27/drivers/s390/char/ |
D | Kconfig | 16 Include support for using an IBM 3270 terminal as a Linux tty. 23 Include support for fullscreen applications on an IBM 3270 terminal. 30 Include support for using an IBM 3270 terminal as a Linux system 45 Include support for using an IBM 3215 line-mode terminal as a 63 Include support for using an IBM HWC line-mode terminal as the Linux 71 Include support for an IBM SCLP VT220-compatible terminal. 78 Include support for using an IBM SCLP VT220-compatible terminal as a
|
/linux-4.1.27/drivers/zorro/ |
D | Kconfig | 12 take up kernel memory. Anyway, if you are building an installation 13 floppy or kernel for an embedded system where kernel image size
|