| /openbmc/linux/Documentation/userspace-api/media/mediactl/ |
| H A 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 …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Power/ |
| H A D | ACPIPowerState.interface.yaml | 27 Hardware context maintained, typically equates to proc/chip set
31 Typically equates to stopped clocks with proc/cache context
35 Typically equates to "suspend-to-RAM".
38 Typically equates to "suspend-to-disk".
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A 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
|
| /openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/ |
| H A 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…
|
| /openbmc/linux/Documentation/accel/ |
| H A 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,
|
| /openbmc/u-boot/include/ |
| H A D | wdt.h | 16 * which typically include placing the system in a safe, known state.
39 * Reset the timer, typically restoring the counter to
49 * This is typically used to reset the board or peripherals.
83 * Reset the timer, typically restoring the counter to
|
| /openbmc/linux/Documentation/RCU/ |
| H A 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()
|
| /openbmc/linux/Documentation/devicetree/bindings/media/i2c/ |
| H A 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.
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A 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
|
| /openbmc/linux/Documentation/userspace-api/media/ |
| H A 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
|
| /openbmc/u-boot/arch/arm/mach-imx/mx3/ |
| H A D | Kconfig | 22 Frequency in Hz of the high frequency input clock. Typically
29 Frequency in Hz of the low frequency input clock. Typically
|
| /openbmc/linux/Documentation/livepatch/ |
| H A 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()*.
|
| /openbmc/linux/drivers/base/power/ |
| H A 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,
|
| /openbmc/linux/drivers/platform/x86/x86-android-tablets/ |
| H A D | Kconfig | 11 typically have various problems with their DSDTs. The factory kernels
12 shipped on these devices typically have device addresses and GPIOs
|
| /openbmc/linux/Documentation/core-api/irq/ |
| H A 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
|
| /openbmc/linux/drivers/staging/fieldbus/Documentation/ |
| H A 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
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A 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
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | marvell,armada-8k-pic.txt | 6 typically connected to the GIC as the primary interrupt controller.
15 typically the GIC
|
| /openbmc/linux/include/linux/platform_data/x86/ |
| H A 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
|
| /openbmc/linux/Documentation/filesystems/ |
| H A 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,
|
| /openbmc/linux/Documentation/devicetree/bindings/usb/ |
| H A 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
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | thunderbolt.rst | 11 Typically PCs come with a firmware connection manager for Thunderbolt 3
57 approval is needed. In BIOS settings this is typically called
64 In BIOS settings this is typically called *Unique ID*.
71 typically called *One time saved key*.
76 typically called *Display Port Only*.
89 the Thunderbolt domain the host controller manages. There is typically
204 Typically OEMs provide this firmware from their support site.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Chassis.interface.yaml | 18 An enclosed or semi-enclosed, typically vertically-oriented,
31 A small, typically removable, chassis or card that contains
|
| /openbmc/linux/tools/power/cpupower/man/ |
| H A 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.
|
| /openbmc/u-boot/doc/device-tree-bindings/spi/ |
| H A D | soft-spi.txt | 5 performance will typically be much lower than a real SPI bus.
22 typically holds the GPIO number.
|