| /kernel/linux/linux-5.10/drivers/net/wireless/ath/ath9k/ |
| D | dynack.c | 127 struct ath_node *an; in ath_dynack_compute_ackto() local
130 list_for_each_entry(an, &da->nodes, list) in ath_dynack_compute_ackto()
131 if (an->ackto > to) in ath_dynack_compute_ackto()
132 to = an->ackto; in ath_dynack_compute_ackto()
152 struct ath_node *an; in ath_dynack_compute_to() local
177 an = (struct ath_node *)sta->drv_priv; in ath_dynack_compute_to()
178 an->ackto = ath_dynack_ewma(an->ackto, in ath_dynack_compute_to()
182 an->ackto, ackto); in ath_dynack_compute_to()
235 struct ath_node *an; in ath_dynack_sample_tx_ts() local
237 an = (struct ath_node *)sta->drv_priv; in ath_dynack_sample_tx_ts()
[all …]
|
| 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
111 an = (struct ath_node *) sta->drv_priv; in ath_debug_rate_stats()
112 rstats = &an->rx_rate_stats; in ath_debug_rate_stats()
171 struct ath_node *an = file->private_data; in read_file_node_recv() local
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 7 busses, which are then exposed by the device tree. For example, an FSI engine
8 that is an I2C master - the I2C bus can be described by the device tree under
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
70 for an address identifier. Since these are not a range, no size cells are
71 required. For an example, a slave on link 1, with ID 2, could be represented
79 Each slave provides an address-space, under which the engines are accessible.
109 Here's an example that illustrates:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| 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 …]
|
| /kernel/linux/linux-5.10/tools/bpf/bpftool/Documentation/ |
| D | bpftool-cgroup.rst | 86 **sock_create** opening of an inet socket (since 4.10);
89 **bind4** call to bind(2) for an inet4 socket (since 4.17);
90 **bind6** call to bind(2) for an inet6 socket (since 4.17);
91 **post_bind4** return from bind(2) for an inet4 socket (since 4.17);
92 **post_bind6** return from bind(2) for an inet6 socket (since 4.17);
93 **connect4** call to connect(2) for an inet4 socket (since 4.17);
94 **connect6** call to connect(2) for an inet6 socket (since 4.17);
95 **sendmsg4** call to sendto(2), sendmsg(2), sendmmsg(2) for an
97 **sendmsg6** call to sendto(2), sendmsg(2), sendmmsg(2) for an
100 an unconnected udp4 socket (since 5.2);
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/drivers/pinctrl/intel/ |
| 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 Broxton pinctrl driver provides an interface that allows
71 This pinctrl driver provides an interface that allows configuring
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 …]
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | ila.rst | 12 differentiates between location and identity of a network node. Part of an
18 ILA can be thought of as means to implement an overlay network without
21 the network, an ILA translated packet appears to be no different than any
22 other IPv6 packet. For instance, if the transport protocol is TCP then an
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.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/i2c/ |
| D | fault-codes.rst | 9 A "Fault" is not always an "Error"
18 result for an operation ... it doesn't indicate that anything is wrong
47 Also returned when trying to invoke an I2C operation in an
52 Returned by SMBus logic when an invalid Packet Error Code byte
67 This rather vague error means an invalid parameter has been
73 performing an I/O operation. Use a more specific fault
90 of a transfer didn't get an ACK. While it might just mean
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
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/sun4i/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | assoc_array.rst | 8 This associative array implementation is an object container with the following
19 permits an object to be located in multiple arrays simultaneously.
24 4. Index keys must be unique. Inserting an object with the same key as one
52 pack leaf object pointers into spare space in the node rather than making an
53 extra branch until as such time an object needs to be added to a full node.
74 The insertion and deletion functions produce an 'edit script' that can later be
82 after an RCU grace period has passed - thus allowing access functions to
91 1. Apply an edit script::
100 2. Cancel an edit script::
132 2. Get a chunk of an object's index key::
[all …]
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| 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
55 If an EBB event and a regular event are both pinned, then whichever is enabled
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
94 However, due to the design of the perf_events API, enabling an event does not
[all …]
|
| /kernel/linux/linux-5.10/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.
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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| 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:
|
| /kernel/linux/linux-5.10/drivers/eisa/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/staging/ |
| 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.
199 every rpmsg address in the system is bound to an rx callback (so when
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| 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
38 module source you will see a third type called an offset, which is just
60 For the above indirect map an autofs file system is mounted on /test and
65 The way that direct mounts are handled is by making an autofs mount on
74 For example, an indirect mount map entry could also be::
92 One of the issues with version 4 of autofs was that, when mounting an
107 The current autofs implementation uses an ioctl file descriptor opened
121 implement an isolated operation it was decided to re-implement the
128 autofs maps. They are recorded at mount request time and an operation
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | marvell,sei.txt | 4 Marvell SEI (System Error Interrupt) controller is an interrupt
6 them to a single interrupt line (an SPI) on the parent interrupt
19 - #interrupt-cells: number of cells to define an SEI wired interrupt
22 - interrupt-controller: identifies the node as an interrupt controller
24 - msi-controller: identifies the node as an MSI controller for the CPs
|
| /kernel/linux/linux-5.10/Documentation/core-api/irq/ |
| D | concepts.rst | 2 What is an IRQ?
5 An IRQ is an interrupt request from a device.
8 sharing an IRQ.
11 interrupt source. Typically this is an index into the global irq_desc
15 An IRQ number is an enumeration of the possible interrupt sources on a
|
| /kernel/linux/linux-5.10/Documentation/misc-devices/ |
| 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
117 is loaded. It first creates and initializes the CRQ. Next, an exchange of
120 Finally, the hypervisor requests that the management partition create an
145 After the basic VMC channel has been initialized, an HMC session level
146 connection can be established. The application layer performs an open() to
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | selection-api-intro.rst | 8 shrink or enlarge it to an image of arbitrary size. Next, the devices
10 part of an input image, scale it up or down and insert it at an
15 cropping target determine the area actually sampled. The sink is an
19 On a video *output* device the source is an image in a memory buffer,
20 and the cropping target is a part of an image to be shown on a display.
|
| /kernel/linux/linux-5.10/fs/verity/ |
| D | Kconfig | 12 filesystems (currently EXT4 and F2FS), userspace can use an
18 This serves as an integrity check, but the availability of the
28 protection against malicious disks vs. an ahead-of-time hash.
38 Say N unless you are an fs-verity developer.
50 used to provide an authenticity guarantee for verity files, as
51 an alternative to IMA appraisal. Userspace programs still
52 need to check that the verity bit is set in order to get an
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/virtio/ |
| D | mmio.txt | 21 - iommus: If the device accesses memory through an IOMMU, it should
22 have an "iommus" property [1]. Since virtio-iommu itself
23 does not access memory through an IOMMU, the "virtio,mmio"
24 node cannot have both an "#iommu-cells" and an "iommus"
|
| /kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
| D | backend-api.rst | 7 The FS-Cache system provides an API by which actual caches can be supplied to
83 In either case, this may not be an appropriate context in which to access the
168 An operation can be made exclusive upon an object by setting the
170 an operation needs more processing time, it should be enqueued again.
194 The to_do field is an empty list available for the cache backend to use as
226 This isn't strictly an operation, but should be pointed at a string naming
249 This method is used to look up an object, given that the object is already
276 This method is called to increment the reference count on an object. It
286 These methods are used to exclusively lock an object. It must be possible
295 These methods are used to pin an object into the cache. Once pinned an
[all …]
|