Searched full:an (Results 1 – 25 of 3071) sorted by relevance
12345678910>>...123
| /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.
10 An IRQ number is a kernel identifier used to talk about a hardware
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
|
| D | irq-domain.rst | 33 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
37 irq_domain also implements translation from an abstract irq_fwspec
44 An interrupt controller driver creates and registers an irq_domain by
48 must provide the allocator function with an irq_domain_ops structure.
68 - generic_handle_domain_irq() handles an interrupt described by a
99 hwirq number. When a hwirq is mapped, an irq_desc is allocated for
110 accepts an Open Firmware specific 'struct device_node', while the latter
124 IRQs. When an hwirq is mapped, an irq_desc is allocated and the
134 accepts an Open Firmware specific 'struct device_node', while the latter
184 controller to manage IRQ allocations and it requires an irq_desc to be
[all …]
|
| /Documentation/ABI/testing/ |
| 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
|
| /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
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 …]
|
| /Documentation/arch/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
70 An EBB event must be created with the "pinned" and "exclusive" attributes set.
74 An EBB event must NOT set any of the "inherit", "sample_period", "freq" or
77 An EBB event must be attached to a task. This is specified to perf_event_open()
[all …]
|
| /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
59 An optional boolean property can be added to indicate that a particular master
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.
[all …]
|
| /Documentation/virt/ |
| D | ne_overview.rst | 14 For example, an application that processes sensitive data and runs in a VM,
16 application then runs in a separate VM than the primary VM, namely an enclave.
25 primary VM, that communicates with the NE kernel driver via an ioctl interface.
29 1. An enclave abstraction process - a user space process running in the primary
30 VM guest that uses the provided ioctl interface of the NE driver to spawn an
37 maps to an enclave start PCI command. The PCI device commands are then
44 for the enclave VM. An enclave does not have persistent storage attached.
46 The memory regions carved out of the primary VM and given to an enclave need to
49 user space [2][3][7]. The memory size for an enclave needs to be at least
52 An enclave runs on dedicated cores. CPU 0 and its CPU siblings need to remain
[all …]
|
| /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 …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller-model.rst | 11 objects on an oriented graph. The object types that constitute the graph
14 - An **entity** is a basic media hardware or software building block.
20 - An **interface** is a graph representation of a Linux Kernel
24 - A **pad** is a data connection endpoint through which an entity can
26 by an entity flows from the entity's output to one or more entity
34 - An **interface link** is a point-to-point bidirectional control
35 connection between a Linux Kernel interface and an entity.
37 - An **ancillary link** is a point-to-point connection denoting that two
|
| /Documentation/userspace-api/ |
| 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
85 1. IOMMUFD_OBJ_IOAS is created via the IOMMU_IOAS_ALLOC uAPI. An iommufd can
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
[all …]
|
| /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 …]
|
| /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 …]
|
| D | xarray.rst | 12 The XArray is an abstract data type which behaves like a very large array
32 objects, as long as those objects have an alignment of at least 4.
35 You must first convert it into an entry using xa_mk_value().
36 When you retrieve an entry from the XArray, you can check whether it is
38 an integer by calling xa_to_value().
41 call xa_tag_pointer() to create an entry with a tag, xa_untag_pointer()
42 to turn a tagged entry back into an untagged pointer and xa_pointer_tag()
43 to retrieve the tag of an entry. Tagged pointers use the same bits that
51 An unusual feature of the XArray is the ability to create entries which
61 Start by initialising an XArray, either with DEFINE_XARRAY()
[all …]
|
| D | maple_tree.rst | 17 entry in a cache-efficient manner. The tree can also be put into an RCU-safe
20 the lock to an external lock of a different type.
24 use the normal API. An :ref:`maple-tree-advanced-api` exists for more complex
57 ``0`` upwards or ``ULONG_MAX`` down. An allocation tree can be used by
62 success or an error code otherwise. mtree_store_range() works in the same way
64 given index. You can use mtree_erase() to erase an entire range by only
65 knowing one value within that range, or mtree_store() call with an entry of
72 You can search for an entry from an index upwards by using mt_find().
84 You can use mtree_dup() to duplicate an entire maple tree. It is a more
103 The Maple Tree uses RCU and an internal spinlock to synchronise access:
[all …]
|
| /Documentation/staging/ |
| 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.
136 Returns 0 on success and an appropriate error value on failure.
153 Returns 0 on success and an appropriate error value on failure.
164 its length (in bytes), and an explicit destination address.
174 Returns 0 on success and an appropriate error value on failure.
195 Returns 0 on success and an appropriate error value on failure.
203 every rpmsg address in the system is bound to an rx callback (so when
[all …]
|
| /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
45 locator and meta data). An ILA domain maintains a database
49 An IPv6 address composed of a SIR prefix (upper sixty-
50 four bits) and an identifier (lower sixty-four bits).
[all …]
|
| D | ppp_generic.rst | 12 The generic PPP driver in linux-2.4 provides an implementation of the
60 * ioctl() provides an interface which can be used by a user-space
62 procedure will be called when a user-space program does an ioctl
63 system call on an instance of /dev/ppp which is bound to the
90 (e.g. an ioctl) to transmit this back to user-space, as user-space
91 will need it to attach an instance of /dev/ppp to this channel.
105 communications medium and prepare it to do PPP. For example, with an
127 The channel must provide an instance of a ppp_channel struct to
259 this way an effect similar to Solaris' clone open is obtained,
260 allowing us to control an arbitrary number of PPP interfaces and
[all …]
|
| /Documentation/arch/x86/ |
| D | sgx.rst | 15 * Unprivileged (ring-3) ENCLU functions allow an application to enter and
18 These memory regions are called enclaves. An enclave can be only entered at a
37 SGX utilizes an *Enclave Page Cache (EPC)* to store pages that are associated
38 with an enclave. It is contained in a BIOS-reserved region of physical memory.
42 Only a CPU executing inside an enclave can directly access enclave memory.
43 However, a CPU executing inside an enclave may access normal memory outside the
56 Regular EPC pages contain the code and data of an enclave.
59 Thread Control Structure pages define the entry points to an enclave and
60 track the execution state of an enclave thread.
70 *Enclave Page Cache Map (EPCM)*. The EPCM contains an entry for each EPC page
[all …]
|
| /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.
|
| /Documentation/driver-api/fpga/ |
| D | fpga-region.rst | 12 an FPGA Manager and a bridge (or bridges) with a reprogrammable region of an
22 An fpga-region can be set up to know the following things:
40 An example of usage can be seen in the probe function of [#f2]_.
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
[all …]
|
| /Documentation/driver-api/nfc/ |
| 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
91 - hci_ready() is an optional entry point that is called right after the hci
95 - start_poll() is an optional entrypoint that shall set the hardware in polling
102 - target_from_gate() is an optional entrypoint to return the nfc protocols
104 - complete_target_discovered() is an optional entry point to let the driver
114 - check_presence() is an optional entry point that will be called regularly
115 by the core to check that an activated tag is still in the field. If this is
[all …]
|
| /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 …]
|
| /Documentation/devicetree/bindings/fpga/ |
| D | fpga-region.yaml | 42 * A section of an FPGA is reprogrammed while the rest of the FPGA is not
48 * A PRR is a specific section of an FPGA reserved for reconfiguration.
59 * An FPGA image that is designed to be loaded into a PRR. There may be
68 * FPGA bridges may be actual hardware or soft logic on an FPGA.
76 * An FPGA image may create a set of reprogrammable regions, each having its
80 * An FPGA Manager is a hardware block that programs an FPGA under the control
85 * An FPGA image that is designed to do full reconfiguration of the FPGA.
106 Figure 1: An FPGA set up with a base image that created three regions. Each
115 When a DT overlay that targets an FPGA Region is applied, the FPGA Region will
131 FPGA Regions represent FPGA's and FPGA PR regions in the device tree. An FPGA
[all …]
|
| /Documentation/hwmon/ |
| D | ltc2992.rst | 39 inX_min_alarm An undervoltage occurred. Cleared on read.
40 inX_max_alarm An overvoltage occurred. Cleared on read.
47 currX_min_alarm An undercurrent occurred. Cleared on read.
48 currX_max_alarm An overcurrent occurred. Cleared on read.
55 powerX_min_alarm An underpower occurred. Cleared on read.
56 powerX_max_alarm An overpower occurred. Cleared on read.
|
| /Documentation/hid/ |
| D | hidraw.rst | 59 the device has an INTERRUPT OUT endpoint, the report will be sent on that
133 Send an Input Report
135 This ioctl will send an input report to the device, using the control endpoint.
136 In most cases, setting an input HID report on a device is meaningless and has
137 no effect, but some devices may choose to use this to set or reset an initial
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
155 This ioctl will send an output report to the device, using the control endpoint.
[all …]
|
12345678910>>...123