Home
last modified time | relevance | path

Searched full:referred (Results 1 – 25 of 360) sorted by relevance

12345678910>>...15

/linux/Documentation/devicetree/bindings/fpga/
H A Daltera-passive-serial.txt4 referred to as "passive serial".
15 - nconfig-gpios: config pin (referred to as nCONFIG in the manual)
16 - nstat-gpios: status pin (referred to as nSTATUS in the manual)
19 - confd-gpios: confd pin (referred to as CONF_DONE in the manual)
H A Dxlnx,fpga-slave-serial.yaml14 over what is referred to as slave serial interface.The slave serial link is
41 config pin (referred to as PROGRAM_B in the manual)
46 config status pin (referred to as DONE in the manual)
52 (referred to as INIT_B in the manual)
/linux/Documentation/sound/soc/
H A Dclocking.rst12 Every audio subsystem is driven by a master clock (sometimes referred to as MCLK
24 The Digital Audio Interface is usually driven by a Bit Clock (often referred to
29 clock is sometimes referred to as LRC (left right clock) or FRAME. This clock
/linux/Documentation/admin-guide/pm/
H A Dstrategies.rst17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
22 is affected by the state changes, this strategy is referred to as the
25 The other strategy, referred to as the :doc:`working-state power management
H A Dsleep-states.rst32 referred to as S2I or S2Idle). It allows more energy to be saved relative to
78 This state (also referred to as STR or S2RAM), if supported, offers significant
112 This state (also referred to as Suspend-to-Disk or STD) offers the greatest
139 (referred to as the ``restore kernel``) looks for a hibernation image in
143 kernel stored in the image (referred to as the ``image kernel``), which is where
H A Dintel_idle.rst30 first of which, referred to as a *hint*, can be used by the processor to
49 configurations (with reduced power draw) resulting from that are referred to
241 least) two levels of idle states (or C-states). One level, referred to as
243 level, referred to as "package C-states", covers the entire processor package
254 put the target core into the low-power state referred to as "core ``C3``" (or
260 low-power state referred to as "package ``C3``" (or ``PC3``), which happens if
H A Dsuspend-flows.rst16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
20 the target sleep state is referred to as *system suspend* too (in the majority
23 working state is referred to as *system resume*.
36 states are mostly identical, so they both together will be referred to as
H A Dcpuidle.rst66 multiple individual single-core "processors", referred to as *hardware threads*
80 Logical CPUs, simply referred to as "CPUs" in what follows, are regarded as
118 calls into a code module referred to as the *governor* that belongs to the CPU
155 was idle after it has been woken up (that time will be referred to as the *idle
254 stopped on idle CPUs are referred to as *tickless* systems and they are
273 that the scheduler tick will be stopped. That time, referred to as the *sleep
369 For example, take a processor with two cores in a larger unit referred to as
/linux/include/uapi/linux/dvb/
H A Ddmx.h60 * @DMX_PES_AUDIO0: first audio PID. Also referred as @DMX_PES_AUDIO.
61 * @DMX_PES_VIDEO0: first video PID. Also referred as @DMX_PES_VIDEO.
62 * @DMX_PES_TELETEXT0: first teletext PID. Also referred as @DMX_PES_TELETEXT.
63 * @DMX_PES_SUBTITLE0: first subtitle PID. Also referred as @DMX_PES_SUBTITLE.
65 * Also referred as @DMX_PES_PCR.
/linux/Documentation/userspace-api/gpio/
H A Dchardev_v1.rst44 on the GPIO device file is referred to as ``chip_fd``.
72 Within this documentation, the line handle file descriptor is referred to
97 Within this documentation, the line event file descriptor is referred to
H A Dchardev.rst48 on the GPIO device file is referred to as ``chip_fd``.
75 Within this documentation, the line request file descriptor is referred to
/linux/arch/arm/mach-omap2/
H A Dcm33xx.c138 * Returns true if the clockdomain referred to by (@inst, @cdoffs)
157 * Put a clockdomain referred to by (@inst, @cdoffs) into
170 * Put a clockdomain referred to by (@inst, @cdoffs) into
184 * Put a clockdomain referred to by (@inst, @cdoffs) into idle
197 * Take a clockdomain referred to by (@inst, @cdoffs) out of idle,
H A Dcminst44xx.c196 * Returns true if the clockdomain referred to by (@part, @inst, @cdoffs)
216 * Put a clockdomain referred to by (@part, @inst, @cdoffs) into
230 * Put a clockdomain referred to by (@part, @inst, @cdoffs) into
245 * Take a clockdomain referred to by (@part, @inst, @cdoffs) out of idle,
/linux/Documentation/arch/powerpc/
H A Dassociativity.rst11 From the platform view, these groups are also referred to as domains.
14 grouping details to the OS. These are referred to as Form 0, Form 1 and Form2
69 this document, this offset will be referred to as domain distance offset.
/linux/Documentation/devicetree/bindings/arm/
H A Darm,integrator.yaml16 "core tiles" and referred to in the device tree as "core modules".
25 expansion modules, it is referred to as an "ASIC Development
/linux/Documentation/userspace-api/media/v4l/
H A Dpixfmt-intro.rst46 and are referred to as "multi-planar formats". For example, a
51 3-planar case. Those sub-buffers are referred to as "*planes*".
H A Dyuv-formats.rst46 sited between the two original pixels. This is referred to as centered or
54 odd number of taps. This is referred to as co-sited chroma.
/linux/Documentation/firmware-guide/acpi/dsd/
H A Ddata-node-references.rst12 Hierarchical data extension nodes may not be referred to directly, hence this
17 data extension node which is referred to by the key shall lie directly under
H A Dleds.rst15 "flash-leds" property documentation. In short, LEDs are directly referred to by
31 followed by the referred object name. That object shall be named "LED" followed
/linux/Documentation/driver-api/surface_aggregator/
H A Doverview.rst35 exposed to ACPI via a shim driver (referred to as Surface ACPI Notify, or
71 (sometimes also referred to as notifications), sent from EC to host without
/linux/Documentation/PCI/
H A Dpci-iov-howto.rst20 devices. The physical device is referred to as Physical Function (PF)
21 while the virtual devices are referred to as Virtual Functions (VF).
/linux/drivers/gpu/host1x/
H A DKconfig17 by host1x are referred to as clients. host1x includes some other
/linux/Documentation/devicetree/bindings/mips/cavium/
H A Ddma-engine.txt4 The DMA Engine will be referred to by phandle by any device that is
/linux/Documentation/devicetree/bindings/interrupt-controller/
H A Dti,omap4-wugen-mpu5 is also referred to as "WUGEN-MPU", hence the name of the binding.
/linux/Documentation/userspace-api/media/dvb/
H A Dca-set-descr.rst35 keys (referred as control words).

12345678910>>...15