/linux/drivers/net/wireless/ath/ath9k/ |
A D | dynack.c | 126 struct ath_node *an; in ath_dynack_compute_ackto() local 130 if (an->ackto > to) in ath_dynack_compute_ackto() 131 to = an->ackto; in ath_dynack_compute_ackto() 151 struct ath_node *an; in ath_dynack_compute_to() local 177 an->ackto = ath_dynack_ewma(an->ackto, in ath_dynack_compute_to() 181 an->ackto, ackto); in ath_dynack_compute_to() 234 struct ath_node *an; in ath_dynack_sample_tx_ts() local 237 an->ackto = -1; in ath_dynack_sample_tx_ts() 329 an->ackto = da->ackto; in ath_dynack_node_init() 348 list_del(&an->list); in ath_dynack_node_deinit() [all …]
|
A 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() 39 if (!an->sta->ht_cap.ht_supported) { in read_file_node_aggr() 46 an->maxampdu); in read_file_node_aggr() 48 an->mpdudensity); in read_file_node_aggr() 56 tid = ath_node_to_tid(an, tidno); in read_file_node_aggr() 100 struct ath_node *an; in ath_debug_rate_stats() local 112 rstats = &an->rx_rate_stats; in ath_debug_rate_stats() 172 struct ath_softc *sc = an->sc; in read_file_node_recv() 175 struct ieee80211_sta *sta = an->sta; in read_file_node_recv() [all …]
|
/linux/Documentation/devicetree/bindings/fsi/ |
A D | fsi.txt | 7 busses, which are then exposed by the device tree. For example, an FSI engine 19 /* top-level of FSI bus topology, bound to an FSI master driver and 20 * exposes an FSI bus */ 40 not be described; this binding only provides an optional facility for 47 value. It's likely that an implementation-specific compatible value will 109 Here's an example that illustrates: 110 - an FSI master 111 - connected to an FSI slave 112 - that contains an engine that is an I2C master 113 - connected to an I2C EEPROM [all …]
|
/linux/Documentation/driver-api/usb/ |
A D | anchors.rst | 8 a driver to cease all IO to an interface. To do so, a 18 There's no API to allocate an anchor. It is simply declared 31 An association of URBs to an anchor is made by an explicit 33 an URB is finished by (successful) completion. Thus disassociation 35 all URBs associated with an anchor. 44 This function kills all URBs associated with an anchor. The URBs 52 This function unlinks all URBs associated with an anchor. The URBs 62 All URBs of an anchor are unanchored en masse. 67 This function waits for all URBs associated with an anchor to finish 74 Returns true if no URBs are associated with an anchor. Locking [all …]
|
/linux/tools/bpf/bpftool/Documentation/ |
A D | bpftool-cgroup.rst | 87 **sock_create** opening of an inet socket (since 4.10); 90 **bind4** call to bind(2) for an inet4 socket (since 4.17); 91 **bind6** call to bind(2) for an inet6 socket (since 4.17); 92 **post_bind4** return from bind(2) for an inet4 socket (since 4.17); 94 **connect4** call to connect(2) for an inet4 socket (since 4.17); 95 **connect6** call to connect(2) for an inet6 socket (since 4.17); 96 **sendmsg4** call to sendto(2), sendmsg(2), sendmmsg(2) for an 98 **sendmsg6** call to sendto(2), sendmsg(2), sendmmsg(2) for an 101 an unconnected udp4 socket (since 5.2); 103 an unconnected udp6 socket (since 5.2); [all …]
|
/linux/drivers/pinctrl/intel/ |
A D | Kconfig | 23 Cherryview/Braswell pinctrl driver provides an interface that 36 provides an interface that allows configuring of PCH pins and 46 Merrifield Family-Level Interface Shim (FLIS) driver provides an 63 This pinctrl driver provides an interface that allows configuring 71 Broxton pinctrl driver provides an interface that allows 79 This pinctrl driver provides an interface that allows configuring 87 This pinctrl driver provides an interface that allows configuring 95 This pinctrl driver provides an interface that allows configuring 103 This pinctrl driver provides an interface that allows configuring 111 This pinctrl driver provides an interface that allows configuring [all …]
|
/linux/arch/m68k/ifpsp060/ |
A 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. 76 | does an "rte". 95 | does an "rte". 114 | does an "rte". 133 | does an "rte". 152 | does an "rte". 171 | does an "rte". 183 | This is the exit point for the 060FPSP when an enabled bsun exception 189 | bit in the FPSR, and does an "rte". The instruction that caused the [all …]
|
/linux/Documentation/networking/ |
A D | ila.rst | 34 A number that identifies an addressable node in the network 40 provide the topological location of an addressed node. ILA 44 A mapping of an ILA identifier to a locator (or to a 50 four bits) and an identifier (lower sixty-four bits). 57 bits) and an identifier (low order sixty-four bits). ILA 58 addresses are never visible to an application. 74 can be an ILA router, ILA forwarding cache, or ILA host. 83 to an ILA overlay. 115 When an address is translated by ILA, an encapsulated transport checksum 184 adjustment value are not present so an identifier is considered an [all …]
|
/linux/Documentation/ABI/testing/ |
A D | sysfs-class-fc | 5 This interface allows an admin to set an FC application 8 an application or logical entity such as a virtual 21 If an appid_store is done for a cgroup id that already 22 has an appid set, the new value will override the 25 If an admin wants to remove an FC application identifier 26 from a cgroup, an appid_store should be done with the
|
/linux/Documentation/i2c/ |
A D | fault-codes.rst | 9 A "Fault" is not always an "Error" 47 Also returned when trying to invoke an I2C operation in an 73 performing an I/O operation. Use a more specific fault 91 an I2C device was temporarily not responding, usually it 98 Returned by an adapter when asked to perform an operation 101 For example, this would be returned when an adapter that 107 Similarly, if an I2C adapter can't execute all legal I2C 111 that if an adapter supports I2C it supports all of I2C.) 116 case is when the length of an SMBus block data response 120 Returned when a transfer was requested using an adapter [all …]
|
/linux/drivers/gpu/drm/sun4i/ |
A D | Kconfig | 13 Choose this option if you have an Allwinner SoC with a 23 Choose this option if you have an Allwinner SoC with an HDMI 32 Choose this option if you have an Allwinner SoC with an HDMI 39 Choose this option if you have an Allwinner SoC with the 52 Choose this option if you want have an Allwinner SoC with 61 Choose this option if you have an Allwinner SoC with the 69 Choose this option if you have an Allwinner SoC with the
|
/linux/Documentation/core-api/ |
A D | assoc_array.rst | 91 1. Apply an edit script:: 100 2. Cancel an edit script:: 132 2. Get a chunk of an object's index key:: 156 5. Free an object:: 170 1. Initialise an associative array:: 177 2. Insert/replace an object in an associative array:: 197 an out-of-memory error. 202 3. Delete an object from an associative array:: 233 an out-of-memory error. 307 2. Find an object in an associative array:: [all …]
|
/linux/Documentation/powerpc/ |
A D | pmu-ebb.rst | 20 Throughout this document we will refer to an "EBB event" or "EBB events". This 39 and attach an EBB event to the process, which will then cause EBBs to be 44 user process. This means once an EBB event is scheduled on the PMU, no non-EBB 57 section below titled "Enabling an EBB event" for more information. 60 Creating an EBB event 63 To request that an event is counted using EBB, the event code should have bit 87 Enabling an EBB event 90 Once an EBB event has been successfully opened, it must be enabled with the 106 Reading an EBB event 109 It is possible to read() from an EBB event. However the results are [all …]
|
/linux/Documentation/staging/ |
A D | rpmsg.rst | 22 its own instance of RTOS in an AMP configuration. 86 Returns 0 on success and an appropriate error value on failure. 96 its length (in bytes), and an explicit destination address. 109 Returns 0 on success and an appropriate error value on failure. 133 Returns 0 on success and an appropriate error value on failure. 149 Returns 0 on success and an appropriate error value on failure. 160 its length (in bytes), and an explicit destination address. 170 Returns 0 on success and an appropriate error value on failure. 191 Returns 0 on success and an appropriate error value on failure. 245 a pointer to an rpmsg_driver struct, which contains the driver's [all …]
|
/linux/Documentation/filesystems/ |
A D | autofs-mount-control.rst | 17 are things such as setting an autofs mount catatonic, setting the 19 certain types of autofs triggered mounts can end up covering an autofs 74 For example, an indirect mount map entry could also be:: 121 implement an isolated operation it was decided to re-implement the 231 an error of -EBADF, -ENOTTY or -EINVAL (not an autofs descriptor) is 250 implementation. It requires an initialized struct autofs_dev_ioctl as an 305 The call requires an initialized struct autofs_dev_ioctl with the 320 The call requires an initialized struct autofs_dev_ioctl with the 327 Set the expire timeout for mounts within an autofs mount point. 354 Issue an expire request to the kernel for an autofs mount. Typically [all …]
|
/linux/Documentation/ABI/stable/ |
A 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. 82 These attributes are only created if the root directory of an 83 IEEE 1394 node or the unit directory of an IEEE 1394 unit 87 Hexadecimal string representation of an u24. 93 Hexadecimal string representation of an u24. 99 Hexadecimal string representation of an u24. 103 Hexadecimal string representation of an u24. 110 Hexadecimal string representation of an u24. [all …]
|
/linux/Documentation/misc-devices/ |
A D | ibmvmc.rst | 23 The Virtual Management Channel (VMC) is a logical device which provides an 26 to provide an alternative to systems that use a Hardware Management 30 on an appliance server named the Hardware Management Console (HMC), 31 packaged as an external tower or rack-mounted personal computer. In a 46 traditionally require an HMC can be implemented in the management 107 This section provides an example for the management application 145 After the basic VMC channel has been initialized, an HMC session level 148 (32 bytes of data) for this session. If the VMC device is in an invalid 152 RDMA of the HMC ID to the hypervisor, and then sends an Interface Open 156 connection. Finally, the hypervisor sends an Interface Open Response [all …]
|
/linux/Documentation/filesystems/caching/ |
A D | backend-api.rst | 295 These methods are used to pin an object into the cache. Once pinned an 300 * Check coherency state of an object [mandatory]:: 325 with an object update operation. 377 highest byte it's willing to store for an object. 387 * Reserve cache space for an object's data [optional]:: 529 * Note occurrence of an I/O error in a cache:: 590 * Perform coherency check on an object:: 622 * Indicate the destruction of an object:: 632 * Indicate negative lookup on an object:: 647 * Indicate an object has been obtained:: [all …]
|
/linux/drivers/eisa/ |
A D | Kconfig | 14 developed as an open alternative to the IBM MicroChannel bus. 21 Say Y here if you are building a kernel for an EISA-based machine. 31 Bus (VLB) card that identify itself as an EISA card (such as 47 # Using EISA_VIRTUAL_ROOT on something other than an Alpha or 48 # an X86 may lead to crashes... 56 (no PCI slots). The Alpha Jensen is an example of such 71 you are building an installation floppy or kernel for an
|
/linux/Documentation/userspace-api/accelerators/ |
A D | ocxl.rst | 5 OpenCAPI is an interface between processors and accelerators. It aims 9 It allows an accelerator (which could be an FPGA, ASICs, ...) to access 83 OpenCAPI includes the possibility for an AFU to send an interrupt to a 88 The driver allows a process to allocate an interrupt and obtain its 128 Based on the AFU definition found in the config space, an AFU may 144 Allocate an AFU interrupt and return an identifier. 152 Associate an event fd to an AFU interrupt so that the user process 153 can be notified when the AFU sends an interrupt.
|
/linux/Documentation/devicetree/bindings/power/reset/ |
A D | gpio-poweroff.txt | 7 state. Otherwise its configured as an input. 9 When the power-off handler is called, the gpio is configured as an 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 power-off handler is called. If this optional 28 property is not specified, the GPIO is initialized as an output in its
|
/linux/Documentation/devicetree/bindings/net/ |
A D | marvell-orion-mdio.txt | 4 MV78xx0, Armada 370, Armada XP, Armada 7k and Armada 8k have an 5 identical unit that provides an interface with the MDIO bus. 7 provides an interface with the xMDIO bus. This driver handles 12 - reg: address and length of the MDIO registers. When an interrupt is 25 Example at the SoC level without an interrupt property: 34 Example with an interrupt property:
|
/linux/drivers/gpu/drm/bridge/analogix/ |
A D | Kconfig | 9 ANX6345 is an ultra-low power Full-HD DisplayPort/eDP 11 ANX6345 transforms the LVTTL RGB output of an 20 ANX78XX is an ultra-low power Full-HD SlimPort transmitter 22 the HDMI output of an application processor to MyDP 35 ANX7625 is an ultra-low power 4K mobile HD transmitter
|
/linux/Documentation/driver-api/nfc/ |
A D | nfc-hci.rst | 12 enables easy writing of HCI-based NFC drivers. The HCI layer runs as an NFC Core 13 backend, implementing an abstract nfc device and translating NFC Core API 19 HCI registers as an nfc device with NFC Core. Requests coming from userspace are 37 The Session initialization is an HCI standard which must unfortunately 102 - target_from_gate() is an optional entrypoint to return the nfc protocols 142 layers such as an llc to store the frame for re-emission, this 223 Workflow executing an HCI command (using shdlc) 226 Executing an HCI command can easily be performed synchronously using the 266 Workflow receiving an HCI event or command 273 NFC_HCI_EVT_TARGET_DISCOVERED event from PN544 requires to issue an [all …]
|
/linux/Documentation/hid/ |
A D | hidraw.rst | 59 the device has an INTERRUPT OUT endpoint, the report will be sent on that 133 Send an Input Report 136 In most cases, setting an input HID report on a device is meaningless and has 142 Get an Input Report 144 This ioctl will request an input report from the device using the control 148 an input report of a device, before an application listens for normal reports via 153 Send an Output Report 158 the initial states of an output report of a device, before an application sends 163 Get an Output Report 165 This ioctl will request an output report from the device using the control [all …]
|