Searched full:typically (Results 1 – 25 of 1411) sorted by relevance
12345678910>>...57
| /Linux-v6.1/Documentation/userspace-api/media/mediactl/ |
| 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-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/ |
| 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-v6.1/Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 28 Description: physical package id of cpuX. Typically corresponds to a physical
34 Description: the CPU die ID of cpuX. Typically it is the hardware platform's
40 Description: the CPU core ID of cpuX. Typically it is the hardware platform's
46 Description: the cluster ID of cpuX. Typically it is the hardware platform's
52 Description: the book ID of cpuX. Typically it is the hardware platform's
58 Description: the drawer ID of cpuX. Typically it is the hardware platform's
|
| /Linux-v6.1/Documentation/RCU/ |
| D | rculist_nulls.rst | 101 lock_chain(); // typically a spin_lock()
110 unlock_chain(); // typically a spin_unlock()
122 lock_chain(); // typically a spin_lock()
124 unlock_chain(); // typically a spin_unlock()
189 lock_chain(); // typically a spin_lock()
200 unlock_chain(); // typically a spin_unlock()
|
| /Linux-v6.1/Documentation/devicetree/bindings/sound/ |
| D | fsl,ssi.txt | 33 codec connected to this SSI. This node is typically
57 playback of audio. This is typically dictated by SOC
61 capture (recording) of audio. This is typically dictated
69 - clock-frequency: The frequency of the input clock, which typically comes
|
| /Linux-v6.1/Documentation/userspace-api/media/ |
| 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).
79 - I/O error. Typically used when there are problems communicating with
|
| /Linux-v6.1/Documentation/livepatch/ |
| 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-v6.1/drivers/base/power/ |
| D | common.c | 92 * This function should typically be invoked from subsystem level code during
128 * This function should typically be invoked by a driver during the probe phase,
141 * dev_pm_domain_detach() on it, typically during the remove phase.
177 * detaches @dev from its PM domain. Typically it should be invoked during the
194 * This function should typically be called during probe by a subsystem/driver,
|
| /Linux-v6.1/Documentation/x86/ |
| D | tdx.rst | 67 The #VE MSRs are typically able to be handled by the hypervisor. Guests
138 A modest amount of memory (typically 512M) is pre-accepted by the firmware
151 fatal. Typically, an unhandled userspace #VE results in a SIGSEGV.
154 Handling nested exceptions on x86 is typically nasty business. A #VE
178 In TDX, MMIO regions typically trigger a #VE exception in the guest. The
|
| /Linux-v6.1/drivers/staging/fieldbus/Documentation/ |
| D | fieldbus_dev.txt | 14 operate the system. This is typically linked to a middle layer of programmable
25 Communication between PLC and device typically happens via process data memory,
35 They are typically used when a Linux device wants to expose itself as an
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | edac.rst | 21 typically 72 bits, in order to provide 64 bits + 8 bits of ECC data.
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
44 controller. Typically, it contains two channels. Two channels at the
56 one 64 bits parallel access. Typically used with SDR, DDR, DDR2 and DDR3
|
| /Linux-v6.1/Documentation/filesystems/ |
| 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-v6.1/Documentation/core-api/irq/ |
| D | concepts.rst | 11 interrupt source. Typically this is an index into the global irq_desc
16 machine. Typically what is enumerated is the number of input pins on
|
| /Linux-v6.1/Documentation/devicetree/bindings/interrupt-controller/ |
| D | marvell,armada-8k-pic.txt | 6 typically connected to the GIC as the primary interrupt controller.
15 typically the GIC
|
| /Linux-v6.1/include/linux/platform_data/x86/ |
| 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-v6.1/Documentation/admin-guide/ |
| 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-v6.1/Documentation/devicetree/bindings/usb/ |
| 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-v6.1/tools/power/cpupower/man/ |
| 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-v6.1/Documentation/driver-api/mei/ |
| 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-v6.1/Documentation/devicetree/bindings/iio/chemical/ |
| 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-v6.1/include/linux/pinctrl/ |
| 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-v6.1/Documentation/hid/ |
| 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 retrive the initial state of
|
| /Linux-v6.1/Documentation/devicetree/bindings/gnss/ |
| D | brcm,bcm4751.yaml | 35 Main voltage supply, pin name VDD_AUXIN, typically connected
40 IO voltage supply, pin name VDDIO, typically 1.8V
|
| /Linux-v6.1/arch/arm64/mm/ |
| 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,
64 * This is typically used when code has been written to a memory region,
|
| /Linux-v6.1/Documentation/ia64/ |
| D | aliasing.rst | 24 System memory typically uses the WB attribute. The UC attribute is
56 The kern_memmap table typically contains only a subset of the system
87 User mappings are typically done with 16K or 64K pages. The smaller
116 specific PCI bus. Typically this is the first megabyte of
150 registers typically can be accessed only with four-byte or
|
12345678910>>...57
