Searched full:typically (Results 1 – 25 of 1202) sorted by relevance
12345678910>>...49
| /Linux-v5.4/Documentation/media/uapi/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-v5.4/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()
|
| /Linux-v5.4/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 | 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
161 Typically OEMs provide this firmware from their support site.
|
| /Linux-v5.4/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-v5.4/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
|
| /Linux-v5.4/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,
|
| /Linux-v5.4/Documentation/media/uapi/ |
| D | gen-errors.rst | 42 typically return while device is streaming, and an ioctl tried to
46 the problem first (typically: stop the stream before retrying).
86 - I/O error. Typically used when there are problems communicating with
|
| /Linux-v5.4/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-v5.4/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
|
| /Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/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-v5.4/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
|
| /Linux-v5.4/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-v5.4/drivers/staging/iio/Documentation/ |
| D | ring.txt | 9 A given buffer implementation typically embeds a struct
11 IIO core. Access to the embedding structure is typically done via
|
| /Linux-v5.4/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-v5.4/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-v5.4/Documentation/devicetree/bindings/bus/ |
| D | ti-sysc.txt | 16 target module and typically are named REVISION, SYSCONFIG and SYSSTATUS.
73 TRM for SYSSTATUS registers, typically 1 with some devices
79 typically available for all interconnect targets on TI SoCs
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| D | soc-camera.rst | 13 of connecting to a variety of systems and interfaces, typically uses i2c for
15 - camera host - an interface, to which a camera is connected. Typically a
87 soc-camera core when a video-device is opened, the host driver would typically
98 Sensor drivers can use struct soc_camera_link, typically provided by the
|
| /Linux-v5.4/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
|
| /Linux-v5.4/sound/soc/intel/ |
| D | Kconfig | 61 typically used for Chromebooks. This is a recommended option.
72 then enable this option by saying Y or m. This was typically used
87 enable this option by saying Y or m. Distros will typically not
|
| /Linux-v5.4/include/drm/ |
| D | drm_panel.h | 40 * The .prepare() function is typically called before the display controller
47 * to call the .enable() function. This will typically enable the backlight to
55 * the .disable() function. Analogously to .enable() this typically involves
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | bq24190.txt | 16 phase (typically 20% of battery capacity).
19 this setting (typically 10% of battery capacity).
|
12345678910>>...49
