Searched full:an (Results 1 – 25 of 2987) sorted by relevance
12345678910>>...120
| /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 provide the allocator function with an irq_domain_ops structure.
58 When an interrupt is received, irq_find_mapping() function should
86 hwirq number. When a hwirq is mapped, an irq_desc is allocated for
97 accepts an Open Firmware specific 'struct device_node', while the latter
111 IRQs. When an hwirq is mapped, an irq_desc is allocated and the
121 accepts an Open Firmware specific 'struct device_node', while the latter
163 controller to manage IRQ allocations and it requires an irq_desc to be
[all …]
|
| /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
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/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 …]
|
| /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.
18 An enclave runs alongside the VM that spawned it. This setup matches low latency
21 process running in the primary VM, that communicates with the NE driver via an
26 1. An enclave abstraction process - a user space process running in the primary
27 VM guest that uses the provided ioctl interface of the NE driver to spawn an
34 maps to an enclave start PCI command. The PCI device commands are then
41 for the enclave VM. An enclave does not have persistent storage attached.
43 The memory regions carved out of the primary VM and given to an enclave need to
46 user space [2][3]. The memory size for an enclave needs to be at least 64 MiB.
[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/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/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.
|
| /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
145 is backing. An object should retired when put_object() is called if it is
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
[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 | idr.rst | 17 provides the ability to map an ID to a pointer, while the IDA provides
23 Start by initialising an IDR, either with DEFINE_IDR()
27 You can call idr_alloc() to allocate an unused ID. Look up
31 If you need to change the pointer associated with an ID, you can call
32 idr_replace(). One common reason to do this is to reserve an
46 To perform an action on all pointers used by the IDR, you can
49 idr_for_each_entry_continue() to continue an iteration. You can
52 When you have finished using an IDR, you can call idr_destroy()
|
| /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 …]
|
| /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/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
|
| /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/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/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() — Register an FPGA region
51 * fpga_region_unregister() — Unregister an FPGA region
57 * fpga_mgr_get() — Get a reference to an FPGA manager, raise ref count
58 * of_fpga_mgr_get() — Get a reference to an FPGA manager, raise ref count,
60 * fpga_mgr_put() — Put an FPGA manager
69 * fpga_bridge_get_to_list() — Get a ref of an FPGA bridge, add it to a
71 * of_fpga_bridge_get_to_list() — Get a ref of an FPGA bridge, add it to a
|
| /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:
|
| /Documentation/driver-api/ |
| D | io-mapping.rst | 8 The io_mapping functions in linux/io-mapping.h provide an abstraction for
9 efficiently mapping small regions of an I/O device to the CPU. The initial
35 creation function yields undefined results. Using an offset
36 which is not page aligned yields an undefined result. The
81 mechanisms and so provides only an abstraction layer and no new
90 kmap_atomic_pfn to map the specified page in an atomic fashion;
92 provides an efficient mapping for this usage.
96 performs an IPI to inform all processors about the new mapping. This results
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | open-pic.txt | 4 representation of an Open PIC compliant interrupt controller. This binding is
20 as an Open PIC. No property value shall be defined.
22 - #interrupt-cells: Specifies the number of cells needed to encode an
25 - #address-cells: Specifies the number of cells needed to encode an
55 * An Open PIC interrupt controller
58 // This is an interrupt controller node.
81 * An interrupt generating device that is wired to an Open PIC.
|
| 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
|
12345678910>>...120