Searched full:usually (Results 1 – 25 of 2164) sorted by relevance
12345678910>>...87
| /linux-6.12.1/Documentation/sound/soc/ |
| D | dai.rst | 15 The bit clock (BCLK) is always driven by the CODEC (usually 12.288MHz) and the
16 frame (FRAME) (usually 48kHz) is always driven by the controller. Each AC97
30 usually varies depending on the sample rate and the master system clock
53 receive the audio data. Bit clock usually varies depending on sample rate
|
| /linux-6.12.1/drivers/clk/sunxi/ |
| D | Kconfig | 25 usually needed for the PMIC communication, mostly.
32 Those are usually needed for the PMIC communication,
40 usually needed for the PMIC communication, mostly.
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-ibft | 6 Usually this contains the Initiator name.
13 Usually this contains the target's IP address, boot LUN,
23 Usually this contains the IP address, MAC, and gateway of the NIC.
|
| /linux-6.12.1/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,omap-remoteproc.yaml | 13 The OMAP family of SoCs usually have one or more slave processor sub-systems
17 The processor cores in the sub-system are usually behind an IOMMU, and may
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
24 sub-system usually contains either a Dual-Core Cortex-M3 or Dual-Core
55 other peripheral device address spaces. This property usually
149 processors. This will usually be a single timer if the
167 will usually be one per executing processor core, even
|
| D | ti,davinci-rproc.txt | 4 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
8 The processor cores in the sub-system usually contain additional sub-modules
11 core used in Davinci SoCs is usually a C674x DSP CPU.
|
| /linux-6.12.1/Documentation/devicetree/bindings/display/panel/ |
| D | samsung,s6d7aa0.yaml | 37 description: Reset GPIO pin, usually GPIO_ACTIVE_LOW.
42 panels, and is usually somewhere around 3.3-5v.
45 description: VMIPI supply, usually 1.8v.
|
| D | jadard,jd9365da-h3.yaml | 30 description: supply regulator for VDD, usually 3.3V
33 description: supply regulator for VCCIO, usually 1.8V
|
| /linux-6.12.1/drivers/usb/serial/ |
| D | omninet.c | 83 * 3: unknown, usually 0
84 * 2: unknown, usually 0
85 * 1: handshaking, unknown, usually set to 1 in transmitted frames
86 * 0: handshaking, unknown, usually set to 1 in transmitted frames
|
| /linux-6.12.1/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-priority.rst | 60 - Lowest priority, usually applications running in background, for
69 - Medium priority, usually applications started and interactively
77 it blocks any other fd from changing device properties. Usually
|
| /linux-6.12.1/include/sound/ |
| D | emu8000.h | 56 unsigned long port1; /* Port usually base+0 */
57 unsigned long port2; /* Port usually at base+0x400 */
58 unsigned long port3; /* Port usually at base+0x800 */
|
| /linux-6.12.1/Documentation/admin-guide/media/ |
| D | cardlist.rst | 10 The platform-specific drivers are usually present on embedded systems,
11 or are supported by the main board. Usually, setting them is done via
|
| /linux-6.12.1/Documentation/locking/ |
| D | spinlocks.rst | 32 The above is usually pretty simple (you usually need and want only one
34 lot more complex and even slower and is usually worth it only for
55 If your data accesses have a very natural pattern where you usually tend
|
| D | hwspinlock.rst | 14 is usually running Linux and the slave processors, the M3 and the DSP,
47 API will usually want to communicate the lock's id to the remote core
57 if that hwspinlock is already in use. Usually board code will
412 order to register a new hwspinlock device (which is usually a bank of
423 to unregister an hwspinlock device (which is usually a bank of numerous
434 struct hwspinlock_device is a device which usually contains a bank
441 * struct hwspinlock_device - a device which usually spans numerous hwspinlocks
|
| /linux-6.12.1/Documentation/process/ |
| D | maintainer-soc.rst | 40 In this regard, "platform" usually refers to a series of SoCs from a given
48 sending pull requests to the main SoC tree. These trees are usually, but not
82 Note that the soc@kernel.org is usually not the place to discuss the patches,
114 Usually the branch that includes a driver change will also include the
156 Directories are usually named after the vendor of the SoC at the time of its
|
| /linux-6.12.1/Documentation/i2c/ |
| D | summary.rst | 43 drivers are usually in the ``drivers/i2c/busses/`` subdirectory.
52 While targets are usually separate external chips, Linux can also act as a
62 the I2C controller, and drivers for your I2C targets. Usually one driver for
|
| /linux-6.12.1/Documentation/networking/devlink/ |
| D | devlink-info.rst | 32 This is usually the serial number of the ASIC, also often available
50 This is usually the serial number of the board, often available in
109 - Version of API between components. API items are usually of limited
192 Unique identifier of the firmware parameter set. These are usually
|
| D | devlink-flash.rst | 16 (usually ``/lib/firmware/``). Drivers may send status updates to inform
50 Devices which require firmware to operate usually store it in non-volatile
61 On-disk firmware files are usually stored in ``/lib/firmware/``.
|
| /linux-6.12.1/Documentation/devicetree/bindings/net/ |
| D | intel,ixp46x-ptp-timer.yaml | 28 PRP timer, usually a GPIO interrupt.
30 PRP timer, usually a GPIO interrupt.
|
| /linux-6.12.1/Documentation/driver-api/media/ |
| D | dtv-core.rst | 12 - Frontend drivers that are usually implemented as two separate drivers:
16 physical channel. The output of a tuner is usually a baseband or
|
| /linux-6.12.1/samples/bpf/ |
| D | README.rst | 44 There are usually dependencies to header files of the current kernel.
77 manager, usually the package is ninja or ninja-build.
112 in its targets appropriate arm64 arch (usually it has several arches).
|
| /linux-6.12.1/tools/include/uapi/linux/ |
| D | stddef.h | 14 * @TAG: The tag name for the named sub-struct (usually empty)
16 * @ATTRS: Any struct attributes (usually empty)
|
| /linux-6.12.1/Documentation/driver-api/dmaengine/ |
| D | provider.rst | 48 transfers we usually have are not, and want to copy data from
58 The latter are usually programmed using a collection of chunks to
62 This collection is usually either a table or a linked list. You will
75 The one last thing is that usually, slave devices won't issue DRQ by
172 - It's usually used for copying pixel data between host memory and
245 - It's usually used for audio transfers, where you want to operate
257 - It's usually used for 2d content transfers, in which case you
622 - When using repeated transfers, DMA clients will usually need to set the
|
| /linux-6.12.1/include/linux/sched/ |
| D | sd_flags.h | 15 * is usually because the flag describes some shared resource (all CPUs in that
28 * set. This is usually for topology properties that start to appear above a
39 * more than one group. This is usually for balancing flags (load balancing
|
| /linux-6.12.1/arch/loongarch/include/asm/ |
| D | orc_types.h | 19 * is usually based on -- and PREV_SP and UNDEFINED -- which the previous FP is
20 * usually based on.
|
| /linux-6.12.1/tools/arch/loongarch/include/asm/ |
| D | orc_types.h | 19 * is usually based on -- and PREV_SP and UNDEFINED -- which the previous FP is
20 * usually based on.
|
12345678910>>...87