| /openbmc/linux/drivers/net/wireless/ath/ath9k/ |
| H A D | dynack.c | 126 struct ath_node *an; in ath_dynack_compute_ackto() local
129 list_for_each_entry(an, &da->nodes, list) in ath_dynack_compute_ackto()
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
176 an = (struct ath_node *)sta->drv_priv; in ath_dynack_compute_to()
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
236 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 …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/Callout/ |
| H A D | README.md | 5 A callout is typically an indication of a faulty hardware component in a system.
7 would be `xyz.openbmc_project.Error.Callout.IIC`, to indicate an IIC callout.
10 is familiar to them, such as a sysfs entry, or an IIC address. It would be up to
17 metadata would be defined in the callout YAML interface. Here is an example (for
29 An application wanting to add an IIC callout will have to provide values for the
31 figure out that this is in fact an IIC callout.
33 A callout is typically associated with an error log. For eg,
34 `xyz.openbmc_project.Error.Foo` may want to add an IIC callout. This is
45 include Callout.IIC's as well, so an application wanting to add an IIC callout
48 figure out that the error Foo includes an IIC callout.
[all …]
|
| /openbmc/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
51 Broxton pinctrl driver provides an interface that allows
58 This pinctrl driver provides an interface that allows configuring
65 This pinctrl driver provides an interface that allows configuring
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
[all …]
|
| /openbmc/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 …]
|
| /openbmc/u-boot/drivers/video/bridge/ |
| H A D | Kconfig | 7 requires LVDS, an eDP->LVDS bridge chip can be used to provide the
15 differential signalling) converters. They enable an LVDS LCD panel
16 to be connected to an eDP output device such as an SoC that lacks
25 signalling) converter. It enables an LVDS LCD panel to be connected
26 to an eDP output device such as an SoC that lacks LVDS capability,
34 The Analogix ANX6345 is RGB-to-DP converter. It enables an eDP LCD
35 panel to be connected to an parallel LCD interface.
|
| /openbmc/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
|
| /openbmc/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
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 …]
|
| /openbmc/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 …]
|
| /openbmc/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 …]
|
| /openbmc/linux/tools/bpf/bpftool/Documentation/ |
| H A D | bpftool-cgroup.rst | 96 **sock_create** opening of an inet socket (since 4.10);
99 **bind4** call to bind(2) for an inet4 socket (since 4.17);
100 **bind6** call to bind(2) for an inet6 socket (since 4.17);
101 **post_bind4** return from bind(2) for an inet4 socket (since 4.17);
102 **post_bind6** return from bind(2) for an inet6 socket (since 4.17);
103 **connect4** call to connect(2) for an inet4 socket (since 4.17);
104 **connect6** call to connect(2) for an inet6 socket (since 4.17);
105 **sendmsg4** call to sendto(2), sendmsg(2), sendmmsg(2) for an
107 **sendmsg6** call to sendto(2), sendmsg(2), sendmmsg(2) for an
110 an unconnected udp4 socket (since 5.2);
[all …]
|
| /openbmc/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
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 …]
|
| /openbmc/linux/drivers/gpu/drm/sun4i/ |
| H A D | Kconfig | 12 Choose this option if you have an Allwinner SoC with a
23 Choose this option if you have an Allwinner A10/A10s/A20/A31
24 SoC with an HDMI controller.
32 Choose this option if you have an Allwinner A10/A10s/A20/A31
33 SoC with an HDMI controller and want to use CEC.
40 Choose this option if you have an Allwinner SoC with the
53 Choose this option if you want have an Allwinner SoC with
63 Choose this option if you have an Allwinner SoC with the
72 Choose this option if you have an Allwinner SoC with the
|
| /openbmc/openbmc/poky/meta-selftest/recipes-test/license/ |
| H A D | incompatible-license-alias.bb | 1 SUMMARY = "Recipe with an alias of an SPDX license"
2 DESCRIPTION = "Is licensed with an alias of an SPDX license to be used for testing"
|
| /openbmc/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 …]
|
| /openbmc/linux/Documentation/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 …]
|
| /openbmc/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 …]
|
| /openbmc/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_HW_PAGETABLE, representing an actual hardware I/O page table
90 2. IOMMUFD_OBJ_DEVICE is created when an external driver calls the IOMMUFD kAPI
91 to bind a device to an iommufd. The driver is expected to implement a set of
97 3. IOMMUFD_OBJ_HW_PAGETABLE is created when an external driver calls the IOMMUFD
98 kAPI to attach a bound device to an IOAS. Similarly the external driver uAPI
110 Future IOMMUFD updates will provide an API to create and manipulate the
113 A device can only bind to an iommufd due to DMA ownership claim and attach to at
[all …]
|
| /openbmc/linux/Documentation/staging/ |
| H 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.
199 every rpmsg address in the system is bound to an rx callback (so when
[all …]
|
| /openbmc/linux/drivers/eisa/ |
| H 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
|
| /openbmc/qemu/docs/devel/ |
| H A D | multiple-iothreads.rst | 16 QEMU is an event-driven program that can do several things at once using an
53 The main difference between legacy code and new code that can run in an
67 * LEGACY ``qemu_aio_set_event_notifier()`` - monitor an event notifier
71 * LEGACY ``qemu_aio_wait()`` - run an event loop iteration
74 runs in an ``IOThread``. They might cause a crash or deadlock if called from an
79 * ``aio_set_event_notifier()`` - monitor an event notifier
83 * ``aio_poll()`` - run an event loop iteration
93 ``qemu_get_aio_context()``. Code that takes an ``AioContext`` argument
97 How to synchronize with an ``IOThread``
104 are thread-safe. They can be used to trigger activity in an ``IOThread``.
[all …]
|
| /openbmc/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 …]
|
| /openbmc/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
|
| /openbmc/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 …]
|
| /openbmc/u-boot/doc/device-tree-bindings/gpu/ |
| H A 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 …]
|