| /linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-types.rst | 283 - typically, /dev/dvb/adapter?/frontend?
287 - typically, /dev/dvb/adapter?/demux?
291 - typically, /dev/dvb/adapter?/dvr?
295 - typically, /dev/dvb/adapter?/ca?
299 - typically, /dev/dvb/adapter?/net?
303 - typically, /dev/video?
307 - typically, /dev/vbi?
311 - typically, /dev/radio?
315 - typically, /dev/v4l-subdev?
319 - typically, /dev/swradio?
[all …]
|
| /linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/ |
| H A D | pipeline.json | 27 …s stalled and there is an interlock. Stall cycles due to a stall in Wr (typically awaiting load da…
30 …s stalled and there is an interlock. Stall cycles due to a stall in Wr (typically awaiting load da…
33 …to calculate the address in the AGU. Stall cycles due to a stall in Wr (typically awaiting load da…
36 …to calculate the address in the AGU. Stall cycles due to a stall in Wr (typically awaiting load da…
39 …o an FPU/NEON instruction. Stall cycles due to a stall in the Wr stage (typically awaiting load da…
42 …o an FPU/NEON instruction. Stall cycles due to a stall in the Wr stage (typically awaiting load da…
|
| /linux/Documentation/accel/ |
| H A D | introduction.rst | 12 Although these devices are typically designed to accelerate
16 Typically, a compute accelerator will belong to one of the following
21 are typically configured using registers and can work with or without DMA.
32 - Training data-center - Similar to Inference data-center cards, but typically
37 All these devices typically have different runtime user-space software stacks,
40 engines. Typically, the common layer in user-space will be the DL frameworks,
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | error-codes.rst | 29 - The ioctl can't be handled because the device is busy. Typically
55 - Permission denied. Typically returned in response to an attempt
61 - I/O error. Typically returned when there are problems communicating
68 - Typically returned when a feature requiring interrupt support was
|
| /linux/tools/perf/pmu-events/arch/powerpc/power10/ |
| H A D | others.json | 45 …itional recycle through the pipeline using the load gather buffer. This typically adds about 10 cy…
50 …itional recycle through the pipeline using the load gather buffer. This typically adds about 10 cy…
55 … unaligned and require an additional recycle through the pipeline. This typically adds about 10 cy…
60 … unaligned and require an additional recycle through the pipeline. This typically adds about 10 cy…
|
| /linux/Documentation/core-api/irq/ |
| H A D | concepts.rst | 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
17 machine. Typically, what is enumerated is the number of input pins on
|
| /linux/Documentation/RCU/ |
| H A D | rculist_nulls.rst | 113 lock_chain(); // typically a spin_lock()
117 unlock_chain(); // typically a spin_unlock()
130 lock_chain(); // typically a spin_lock()
132 unlock_chain(); // typically a spin_unlock()
208 lock_chain(); // typically a spin_lock()
215 unlock_chain(); // typically a spin_unlock()
|
| /linux/drivers/base/power/ |
| H A D | common.c | 93 * This function should typically be invoked from subsystem level code during
129 * This function should typically be invoked by a driver during the probe phase,
142 * dev_pm_domain_detach() on it, typically during the remove phase.
178 * caller, which is typically a driver's probe function, may provide a list of
188 * dev_pm_domain_detach_list(), typically during the remove phase.
351 * detaches @dev from its PM domain. Typically it should be invoked during the
369 * Typically it should be invoked during the remove phase from drivers.
397 * This function should typically be called during probe by a subsystem/driver,
|
| /linux/Documentation/devicetree/bindings/media/i2c/ |
| H A D | ovti,ov5670.yaml | 36 description: Analog circuit power. Typically 2.8V.
39 description: Digital circuit power. Typically 1.2V.
42 description: Digital I/O circuit power. Typically 2.8V or 1.8V.
|
| /linux/Documentation/livepatch/ |
| H A D | system-state.rst | 10 add, and even remove fixes. And it is typically safe to replace any version
122 The system state itself is typically modified in *post_patch()*
160 *pre_unpatch()* typically does symmetric operations to *post_patch()*.
165 *post_unpatch()* typically does symmetric operations to *pre_patch()*.
|
| /linux/Documentation/userspace-api/media/ |
| H A D | gen-errors.rst | 35 typically return while device is streaming, and an ioctl tried to
39 the problem first (typically: stop the stream before retrying).
77 - I/O error. Typically used when there are problems communicating with
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-virtual-misc-tdx_guest | 24 (RO) MRCONFIGID - 48-byte immutable storage typically used for
33 (RO) MROWNER - 48-byte immutable storage typically used for
41 (RO) MROWNERCONFIG - 48-byte immutable storage typically used
|
| /linux/include/linux/ |
| H A D | tsm-mr.h | 13 * @mr_size: size of the MR - typically the digest size of @mr_hash
28 * The semantics is typically to extend the MR but could vary depending on the
62 * Typically, writing to an MR extends the input buffer to that MR.
|
| /linux/Documentation/filesystems/ |
| H A D | ubifs.rst | 22 rather large size, typically about 128KiB. Block devices consist of
23 small blocks, typically 512 bytes.
31 typically 100K-1G for SLC NAND and NOR flashes, and 1K-10K for MLC
34 deal with this. Blocks on hard drives typically do not become bad,
|
| /linux/Documentation/security/ |
| H A D | snp-tdx-threat-model.rst | 29 processing can be performed and, as a result, they are typically further
57 (VMM) typically consists of a subset of traditional VMM features and
60 typically stays out of CoCo VM TCB, its access is limited to preserve the
108 The existing Linux kernel threat model typically assumes execution on a
113 attackers are typically considered, including those with access to enabled
130 traditional VMM or all of it), which is typically placed outside of the
198 host in a CoCo system typically controls the process of creating a CoCo
|
| /linux/Documentation/admin-guide/ |
| H A D | thunderbolt.rst | 11 Typically PCs come with a firmware connection manager for Thunderbolt 3
57 approval is needed. In BIOS settings this is typically called
64 In BIOS settings this is typically called *Unique ID*.
71 typically called *One time saved key*.
76 typically called *Display Port Only*.
89 the Thunderbolt domain the host controller manages. There is typically
204 Typically OEMs provide this firmware from their support site.
|
| /linux/include/linux/platform_data/x86/ |
| H A D | clk-pmc-atom.h | 15 * @name: identified, typically pmc_plt_clk_<x>, x=[0..5]
29 * @clks: pointer to set of registered clocks, typically 0..5
|
| /linux/Documentation/hid/ |
| H A D | hidraw.rst | 30 create hidraw device nodes. Udev will typically create the device nodes
147 specific report number. Typically, this is used to request the initial states of
157 output reports, but is added for completeness. Typically, this is used to set
166 endpoint. Typically, this is used to retrieve the initial state of
|
| /linux/Documentation/driver-api/mei/ |
| H A D | mei-client-bus.rst | 57 API. This is typically called at module initialization time.
59 Once the driver is registered and bound to the device, a driver will typically
139 The handler implementation will typically call :c:func:`mei_cldev_recv` and then
|
| /linux/Documentation/devicetree/bindings/usb/ |
| H A D | gr-udc.txt | 23 number. If the property is present it typically contains one entry for
29 number. If the property is present it typically contains one entry for
|
| /linux/tools/power/cpupower/man/ |
| H A D | cpupower.1 | 33 Some commands access all cores (typically the *\-set commands), some only
34 the first core (typically the *\-info commands) by default.
|
| /linux/arch/arm64/mm/ |
| H A D | cache.S | 21 * This is typically used when code has been written to a memory region,
49 * This is typically used when code has been written to a memory region,
65 * This is typically used when code has been written to a memory region,
|
| /linux/Documentation/devicetree/bindings/iio/chemical/ |
| H A D | senseair,sunrise.yaml | 32 Phandle to the GPIO line connected to the nDRY pin. Typically active low.
37 Phandle to the GPIO line connected to the EN pin. Typically active high.
|
| /linux/include/linux/pinctrl/ |
| H A D | pinctrl-state.h | 26 * example. Could typically be set from a pm_runtime_suspend() or
30 * its lowest sleep state. Could typically be set from an
|
| /linux/Documentation/gpu/ |
| H A D | drm-vm-bind-locking.rst | 30 meta-data. Typically one per client (DRM file-private), or one per
99 Furthermore, it typically protects the gpu_vm's list of evicted and
121 is protected by the ``gem_object->gpuva_lock``, which is typically the
146 gpu_vm's destructor. Drivers typically implements a gpu_vm close
161 gpu_vmas set up pointing to them. Typically, each gpu command buffer
255 gpu_vms the object is bound to are typically not held. Only
536 list. This is referred to as *linking* the gpu_vma, and typically
558 Since the unmapping (or zapping) of GPU ptes is typically taking place
580 typically focuses only on zeroing page-table or page-directory entries
|