| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-ref-variables-context.rst | 19 Variables starting with ``BB_`` usually configure the behaviour of BitBake itself.
29 Those variables are usually configured globally.
42 handled. Those are usually set by ``bitbake.conf`` and might get adapted in a
47 :term:`PERSISTENT_DIR`. Those are usually global.
71 the name or revision of a recipe or package. Usually, the default set in
85 a recipe like :term:`SRC_URI` or :term:`SRCDATE`. Those are also usually set
|
| /openbmc/linux/Documentation/sound/soc/ |
| H A 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
|
| /openbmc/linux/drivers/clk/sunxi/ |
| H A 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.
|
| /openbmc/u-boot/doc/ |
| H A D | README.memory-test | 45 used for the exception vectors (usually at the very lower end of
47 these are usually at the very upper end of system memory). But
72 Unfortunately, this is only true for the relatively harmless, usually
76 which usually happen not with simple read or write cycles on the bus,
78 accesses usually happen only for certain DMA operations, or for heavy
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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.
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A 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
|
| H A D | ti,davinci-rproc.txt | 7 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
11 The processor cores in the sub-system usually contain additional sub-modules
14 core used in Davinci SoCs is usually a C674x DSP CPU.
|
| /openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
| H A D | samsung,s6d7aa0.yaml | 36 description: Reset GPIO pin, usually GPIO_ACTIVE_LOW.
41 panels, and is usually somewhere around 3.3-5v.
44 description: VMIPI supply, usually 1.8v.
|
| H A D | jadard,jd9365da-h3.yaml | 27 description: supply regulator for VDD, usually 3.3V
30 description: supply regulator for VCCIO, usually 1.8V
|
| /openbmc/docs/designs/ |
| H A D | sol-sysrq.md | 12 low-level commands. BMC usually provides SysRq support in KVM and SOL functions,
18 The key combination consists of Alt+SysRq (usually the `PrintScreen` key) and
20 requires special handling. A serial console usually invokes SysRq feature by
22 is usually generated by `ctrl+break` key combination.[2]
|
| /openbmc/linux/drivers/usb/serial/ |
| H A D | omninet.c | 84 * 3: unknown, usually 0
85 * 2: unknown, usually 0
86 * 1: handshaking, unknown, usually set to 1 in transmitted frames
87 * 0: handshaking, unknown, usually set to 1 in transmitted frames
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A 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
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | yocto-project-compatible.rst | 15 the aspects of the final output. This usually isn't intentional but happens
92 kernel modules needed for the hardware. Such layers usually correspond
98 configuration and choices of software components. This would usually
101 - "software" layers are usually recipes. A layer might target a
|
| /openbmc/linux/include/sound/ |
| H A 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 */
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/ |
| H A D | Item.interface.yaml | 22 Any inventory Items (usually Boards or Chassis) can optionally
31 association to provide a link to exactly one Item (usually a Board or
68 Any inventory Item (usually Boards or Chassis) can optionally
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A 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
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/gtkperf/gtkperf/ |
| H A D | Makevars | 3 # Usually the message domain is the same as the package name.
24 # message catalogs shall be used. It is usually empty.
|
| /openbmc/linux/Documentation/locking/ |
| H A 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
|
| H A 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
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A 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
187 Unique identifier of the firmware parameter set. These are usually
|
| /openbmc/openbmc/poky/meta/recipes-devtools/gcc/gcc/ |
| H A D | 0012-Avoid-using-libdir-from-.la-which-usually-points-to-.patch | 4 Subject: [PATCH] Avoid using libdir from .la which usually points to a host
23 + # Instead of using libdir from .la which usually points to a host path,
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | intel,ixp46x-ptp-timer.yaml | 28 PRP timer, usually a GPIO interrupt.
30 PRP timer, usually a GPIO interrupt.
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A 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
|
| /openbmc/openbmc/poky/meta/recipes-devtools/perl/files/ |
| H A D | 0001-cpan-Sys-Syslog-Makefile.PL-Fix-_PATH_LOG-for-determ.patch | 8 usually doesn't have /dev/log which leads to a different build result since
9 other host usually has /dev/log, so make it always use the default value to fix
|
| /openbmc/linux/samples/bpf/ |
| H A 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).
|