| /linux/drivers/net/wireless/ath/ath9k/ |
| H A 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 …]
|
| H 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->deflink.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 …]
|
| /linux/Documentation/devicetree/bindings/fsi/ |
| H A 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 …]
|
| /linux/drivers/pinctrl/intel/ |
| H A D | Kconfig | 21 Cherryview/Braswell pinctrl driver provides an interface that
29 provides an interface that allows configuring of PCH pins and
44 This pinctrl driver provides an interface that allows configuring
55 This pinctrl driver provides an interface that allows configuring
65 Broxton pinctrl driver provides an interface that allows
72 This pinctrl driver provides an interface that allows configuring
79 This pinctrl driver provides an interface that allows configuring
86 This pinctrl driver provides an interface that allows configuring
93 This pinctrl driver provides an interface that allows configuring
100 This pinctrl driver provides an interface that allows configuring
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| H 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
51 All URBs of an anchor are unanchored en masse.
56 This function waits for all URBs associated with an anchor to finish
63 Returns true if no URBs are associated with an anchor. Locking
69 Returns the oldest anchored URB of an anchor. The URB is unanchored
|
| /linux/tools/bpf/bpftool/Documentation/ |
| H A D | bpftool-cgroup.rst | 97 - **sock_create** opening of an inet socket (since 4.10)
100 - **bind4** call to bind(2) for an inet4 socket (since 4.17)
101 - **bind6** call to bind(2) for an inet6 socket (since 4.17)
102 - **post_bind4** return from bind(2) for an inet4 socket (since 4.17)
103 - **post_bind6** return from bind(2) for an inet6 socket (since 4.17)
104 - **connect4** call to connect(2) for an inet4 socket (since 4.17)
105 - **connect6** call to connect(2) for an inet6 socket (since 4.17)
107 …- **sendmsg4** call to sendto(2), sendmsg(2), sendmmsg(2) for an unconnected udp4 socket (since 4.…
108 …- **sendmsg6** call to sendto(2), sendmsg(2), sendmmsg(2) for an unconnected udp6 socket (since 4.…
109 …- **sendmsg_unix** call to sendto(2), sendmsg(2), sendmmsg(2) for an unconnected unix socket (sinc…
[all …]
|
| /linux/arch/m68k/ifpsp060/ |
| H 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.
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 …]
|
| /linux/Documentation/ABI/testing/ |
| H 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/networking/ |
| H A 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 …]
|
| /linux/Documentation/i2c/ |
| H A 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
44 they are requested to use such an address.
51 Also returned when trying to invoke an I2C operation in an
56 Returned by SMBus logic when an invalid Packet Error Code byte
71 This rather vague error means an invalid parameter has been
77 performing an I/O operation. Use a more specific fault
94 of a transfer didn't get an ACK. While it might just mean
95 an I2C device was temporarily not responding, usually it
102 Returned by an adapter when asked to perform an operation
[all …]
|
| /linux/Documentation/userspace-api/ |
| H A D | iommufd.rst | 35 - IOMMUFD_OBJ_IOAS, representing an I/O address space (IOAS), allowing map/unmap
39 container it copies an IOVA map to a list of iommu_domains held within it.
41 - IOMMUFD_OBJ_DEVICE, representing a device that is bound to iommufd by an
44 - IOMMUFD_OBJ_HWPT_PAGING, representing an actual hardware I/O page table
46 primarily indicates this type of HWPT should be linked to an IOAS. It also
47 indicates that it is backed by an iommu_domain with __IOMMU_DOMAIN_PAGING
48 feature flag. This can be either an UNMANAGED stage-1 domain for a device
55 - IOMMUFD_OBJ_HWPT_NESTED, representing an actual hardware I/O page table
57 "NESTED" indicates that this type of HWPT should be linked to an HWPT_PAGING.
58 It also indicates that it is backed by an iommu_domain that has a type of
[all …]
|
| /linux/Documentation/core-api/ |
| H A 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 …]
|
| /linux/drivers/gpu/drm/sun4i/ |
| H A D | Kconfig | 13 Choose this option if you have an Allwinner SoC with a
27 Choose this option if you have an Allwinner A10/A10s/A20/A31
28 SoC with an HDMI controller.
36 Choose this option if you have an Allwinner A10/A10s/A20/A31
37 SoC with an HDMI controller and want to use CEC.
44 Choose this option if you have an Allwinner SoC with the
57 Choose this option if you want have an Allwinner SoC with
67 Choose this option if you have an Allwinner SoC with the
76 Choose this option if you have an Allwinner SoC with the
|
| /linux/Documentation/staging/ |
| H A D | rpmsg.rst | 22 its own instance of RTOS in an AMP configuration.
87 Returns 0 on success and an appropriate error value on failure.
97 its length (in bytes), and an explicit destination address.
111 Returns 0 on success and an appropriate error value on failure.
128 Returns 0 on success and an appropriate error value on failure.
139 its length (in bytes), and an explicit destination address.
149 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
159 appropriate callback handler) by means of an rpmsg_endpoint struct.
161 This function allows drivers to create such an endpoint, and by that,
[all …]
|
| /linux/Documentation/arch/powerpc/ |
| H 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
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 …]
|
| /linux/Documentation/filesystems/ |
| H 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
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 …]
|
| /linux/Documentation/ABI/stable/ |
| H 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/ |
| H 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
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 …]
|
| /linux/Documentation/core-api/irq/ |
| H A D | concepts.rst | 2 What is an IRQ?
5 An IRQ is an interrupt request from a device. Currently, they can come
7 the same pin thus sharing an IRQ. Such as on legacy PCI bus: All devices
8 typically share 4 lanes/pins. Note that each device can request an
12 interrupt source. Typically, this is an index into the global irq_desc
16 An IRQ number is an enumeration of the possible interrupt sources on a
|
| /linux/drivers/fsi/ |
| H A D | Kconfig | 43 allow chaining of FSI links to an arbitrary depth. This allows for
60 This option enables a FSI master that is present behind an OPB bridge
63 Enable it for your BMC kernel in an OpenPower or IBM Power system.
70 behind an IBM I2C Responder (I2CR) chip. The I2CR is an I2C device
72 implementing an FSI master and bus.
77 This option enables an FSI based SCOM device driver.
83 This option enables an FSI based SBEFIFO device driver. The SBEFIFO is
91 This option enables an SBEFIFO based On-Chip Controller (OCC) device
101 This option enables an I2C Responder based SCOM device driver. The
|
| /linux/Documentation/userspace-api/accelerators/ |
| H A D | ocxl.rst | 5 OpenCAPI is an interface between processors and accelerators. It aims
12 It allows an accelerator (which could be an FPGA, ASICs, ...) to access
86 OpenCAPI includes the possibility for an AFU to send an interrupt to a
91 The driver allows a process to allocate an interrupt and obtain its
131 Based on the AFU definition found in the config space, an AFU may
147 Allocate an AFU interrupt and return an identifier.
155 Associate an event fd to an AFU interrupt so that the user process
156 can be notified when the AFU sends an interrupt.
|
| /linux/Documentation/driver-api/fpga/ |
| H A D | fpga-region.rst | 12 an FPGA Manager and a bridge (or bridges) with a reprogrammable region of an
50 * __fpga_region_register_full() - Create and register an FPGA region using the
52 * __fpga_region_register() - Create and register an FPGA region using standard
54 * fpga_region_unregister() - Unregister an FPGA region
63 * fpga_mgr_get() - Get a reference to an FPGA manager, raise ref count
64 * of_fpga_mgr_get() - Get a reference to an FPGA manager, raise ref count,
66 * fpga_mgr_put() - Put an FPGA manager
75 * fpga_bridge_get_to_list() - Get a ref of an FPGA bridge, add it to a
77 * of_fpga_bridge_get_to_list() - Get a ref of an FPGA bridge, add it to a
|
| /linux/drivers/net/phy/ |
| H A D | nxp-c45-tja11xx-macsec.c | 187 u8 an; member
404 enum nxp_c45_sa_type sa_type, u8 an) in nxp_c45_find_sa() argument
409 if (pos->an == an && pos->type == sa_type) in nxp_c45_find_sa()
416 enum nxp_c45_sa_type sa_type, u8 an) in nxp_c45_sa_alloc() argument
425 if (pos->an == an) in nxp_c45_sa_alloc()
445 tmp->an = an; in nxp_c45_sa_alloc()
527 nxp_c45_macsec_write(phydev, MACSEC_RXAN0INUSS + sa->an * 4, 0); in nxp_c45_rx_sa_clear_stats()
528 nxp_c45_macsec_write(phydev, MACSEC_RXAN0IPUSS + sa->an * 4, 0); in nxp_c45_rx_sa_clear_stats()
561 cfg = sa->an << MACSEC_RXSA_CS_AN_OFF; in nxp_c45_rx_sa_update()
574 cfg |= sa->an << MACSEC_TXSC_CFG_AN_OFF; in nxp_c45_tx_sa_update()
[all …]
|
| /linux/Documentation/bpf/ |
| H A D | map_of_maps.rst | 14 an outer map contains instances of a single type of inner map, for example
17 When creating an outer map, an inner map instance is used to initialize the
28 - Any BPF map type can be used as an inner map, except for
32 For ``BPF_MAP_TYPE_ARRAY_OF_MAPS`` the key is an unsigned 32-bit integer index
64 This snippet shows how to create and initialise an array of devmaps in a BPF
93 This snippet shows how to create an array based outer map:
111 This snippet shows how to add an inner map to an outer map:
|
| H A D | map_xskmap.rst | 44 accept XDP frames from that <netdev/queue_id>. If an XDP program tries to redirect
48 Typically an XSKMAP is created per netdev. This map contains an array of XSK File
72 If the map is empty at an index, the packet is dropped. This means that it is
73 necessary to have an XDP program loaded with at least one XSK in the
107 - BPF_ANY: Create a new element or update an existing element.
109 - BPF_EXIST: Update an existing element.
130 When `libxdp`_ deletes an XSK it also removes the associated socket
139 ``xsks_map`` and how to redirect packets to an XSK.
164 The following code snippet shows how to update an XSKMAP with an XSK entry.
179 For an example on how create AF_XDP sockets, please see the AF_XDP-example and
|