Searched full:typically (Results 1 – 25 of 2782) sorted by relevance
12345678910>>...112
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/ |
| D | media-types.rst | 276 - typically, /dev/dvb/adapter?/frontend?
280 - typically, /dev/dvb/adapter?/demux?
284 - typically, /dev/dvb/adapter?/dvr?
288 - typically, /dev/dvb/adapter?/ca?
292 - typically, /dev/dvb/adapter?/net?
296 - typically, /dev/video?
300 - typically, /dev/vbi?
304 - typically, /dev/radio?
308 - typically, /dev/v4l-subdev?
312 - typically, /dev/swradio?
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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…
|
| /kernel/linux/linux-6.6/Documentation/accel/ |
| 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,
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/Documentation/RCU/ |
| 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()
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | cputopology.rst | 11 physical package id of cpuX. Typically corresponds to a physical
17 the CPU die ID of cpuX. Typically it is the hardware platform's
23 the CPU core ID of cpuX. Typically it is the hardware platform's
29 the book ID of cpuX. Typically it is the hardware platform's
35 the drawer ID of cpuX. Typically it is the hardware platform's
|
| D | thunderbolt.rst | 11 Typically PCs come with a firmware connection manager for Thunderbolt 3
54 approval is needed. In BIOS settings this is typically called
61 In BIOS settings this is typically called *Unique ID*.
68 typically called *One time saved key*.
73 typically called *Display Port Only*.
82 the Thunderbolt domain the host controller manages. There is typically
181 Typically OEMs provide this firmware from their support site.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/media/i2c/ |
| 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.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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()*.
|
| /kernel/linux/linux-6.6/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()*.
|
| /kernel/linux/linux-6.6/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,
|
| /kernel/linux/linux-5.10/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 * Typically it should be invoked during the remove phase, either from
194 * This function should typically be called during probe by a subsystem/driver,
|
| /kernel/linux/linux-6.6/drivers/platform/x86/x86-android-tablets/ |
| D | Kconfig | 11 typically have various problems with their DSDTs. The factory kernels
12 shipped on these devices typically have device addresses and GPIOs
|
| /kernel/linux/linux-6.6/Documentation/arch/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
241 as input and included in the TDREPORT. Typically it can be some nonce
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
|
12345678910>>...112