Searched full:typically (Results 1 – 25 of 2405) sorted by relevance
12345678910>>...97
| /kernel/linux/linux-4.19/Documentation/media/uapi/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-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-4.19/Documentation/RCU/ |
| D | rculist_nulls.txt | 84 lock_chain(); // typically a spin_lock()
93 unlock_chain(); // typically a spin_unlock()
103 lock_chain(); // typically a spin_lock()
105 unlock_chain(); // typically a spin_unlock()
161 lock_chain(); // typically a spin_lock()
172 unlock_chain(); // typically a spin_unlock()
|
| /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-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-4.19/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/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-4.19/sound/soc/intel/ |
| D | Kconfig | 60 typically used for Chromebooks. This is a recommended option.
71 then enable this option by saying Y or m. This was typically used
86 enable this option by saying Y or m. Distros will typically not
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/ |
| 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-4.19/Documentation/filesystems/ |
| D | ubifs.txt | 16 rather large size, typically about 128KiB. Block devices consist of
17 small blocks, typically 512 bytes.
25 typically 100K-1G for SLC NAND and NOR flashes, and 1K-10K for MLC
28 deal with this. Blocks on hard drives typically do not become bad,
|
| /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-4.19/Documentation/ia64/ |
| D | aliasing.txt | 19 System memory typically uses the WB attribute. The UC attribute is
50 The kern_memmap table typically contains only a subset of the system
79 User mappings are typically done with 16K or 64K pages. The smaller
105 specific PCI bus. Typically this is the first megabyte of
137 registers typically can be accessed only with four-byte or
|
| /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-4.19/Documentation/devicetree/bindings/net/can/ |
| D | can-transceiver.txt | 4 CAN transceiver typically limits the max speed in standard CAN and CAN FD
5 modes. Typically these limitations are static and the transceivers themselves
|
| /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-4.19/Documentation/ |
| D | IRQ.txt | 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/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-4.19/Documentation/admin-guide/ |
| D | thunderbolt.rst | 34 approval is needed. In BIOS settings this is typically called
41 In BIOS settings this is typically called *Unique ID*.
48 typically called *One time saved key*.
53 typically called *Display Port Only*.
62 the Thunderbolt domain the host controller manages. There is typically
141 Typically OEMs provide this firmware from their support site.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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,
|
| /kernel/linux/linux-4.19/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>>...97