Searched refs:within (Results 1 – 25 of 776) sorted by relevance
12345678910>>...32
| /Linux-v5.4/drivers/char/tpm/ |
| D | Kconfig | 15 say Yes and it will be accessible from within Linux. For
55 within Linux. To compile this driver as a module, choose M here;
67 within Linux. To compile this driver as a module, choose M here;
75 accessible from within Linux.
85 Specification 0.20 say Yes and it will be accessible from within
96 from within Linux.
105 say Yes and it will be accessible from within Linux. To
114 will be accessible from within Linux. To compile this driver
123 will be accessible from within Linux.
134 will be accessible from within Linux. To compile this driver
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/mips/cavium/ |
| D | ciu.txt | 12 - #interrupt-cells: Must be <2>. The first cell is the bank within
14 within the bank and may have a value between 0 and 63.
22 * 2) Bit within the register (0..63)
|
| D | ciu2.txt | 12 - #interrupt-cells: Must be <2>. The first cell is the bank within
14 the bit within the bank and may also have a value between 0 and 63.
22 * 2) Bit within the register (0..63)
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | cputopology.rst | 41 internal kernel map of CPUs within the same core.
46 human-readable list of CPUs within the same core.
61 internal kernel map of CPUs within the same die.
65 human-readable list of CPUs within the same die.
69 internal kernel map of cpuX's hardware threads within the same
74 human-readable list of cpuX's hardware threads within the same
79 internal kernel map of cpuX's hardware threads within the same
84 human-readable list of cpuX's hardware threads within the same
|
| /Linux-v5.4/Documentation/sound/soc/ |
| D | pops-clicks.rst | 6 of components within the audio subsystem. This is noticeable on PCs when an
11 because the components within the subsystem are being dynamically powered
21 suppression. Pops can be reduced within playback by powering the audio
50 An unwanted zipper noise can occur within the audio playback or capture stream
|
| D | dapm.rst | 9 Linux devices to use the minimum amount of power within the audio
14 all power switching is done within the ASoC core. No code changes or
17 activity and audio mixer settings within the device.
19 DAPM spans the whole machine. It covers power control within the entire
23 There are 4 power domains within DAPM
109 Inter widget audio data buffer within a DSP.
116 Sample Rate Converter within DSP or CODEC
118 Asynchronous Sample Rate Converter within DSP or CODEC
170 audio paths within the audio subsystem. They have the following form:-
248 Widgets are connected to each other within the codec, platform and machine by
[all …]
|
| /Linux-v5.4/Documentation/arm64/ |
| D | perf.txt | 27 never counted within a guest.
43 never counted within a guest.
70 The statements above also apply when these attributes are used within a
71 non-VHE guest however please note that EL2 is never counted within a guest.
|
| /Linux-v5.4/drivers/staging/iio/Documentation/ |
| D | ring.txt | 1 Buffer support within IIO
4 a buffer may supply and how it is specified within IIO. For more
22 The function pointers within here are used to allow the core to handle
|
| /Linux-v5.4/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.txt | 33 name and an integer GPIO name within the port. For example, GPIO_PA0, GPIO_PN6,
37 implemented GPIOs within each port varies. GPIO registers within a controller
41 the mapping from port name to register offset within a controller, are both
45 sorted within a particular controller. Drivers need to map between the DT GPIO
49 represents the aggregate status for all GPIOs within a set of ports. Thus, the
58 handle subsets of the interrupts within a port. The status of each of these
|
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ |
| D | st,stm32-rcc.txt | 42 The secondary index is the bit number within the RCC register bank, starting
46 Where bit_offset is the bit offset within the register (LSB is 0, MSB is 31).
127 The index is the bit number within the RCC registers bank, starting from RCC
130 Where bit_offset is the bit offset within the register.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices | 9 devices within this tree will change.
15 within the /sys/devices tree of the individual devices.
|
| /Linux-v5.4/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 42 the fixed fields within these two options are administered by the Defense
77 systems within a single Domain of Interpretation (DOI). A DOI is a
82 mapping to hosts within the authority's domain. These mappings may be
123 a mapping table within CIPSO hosts to map these numbers to their
139 to identify which mapping was used for the values within the option.
151 all tags, as well as fields within a tag, are not aligned on any particular
230 restriction of 40 bytes the value within this field is between 4 and 34.
316 restriction of 40 bytes the value within this field is between 4 and 34.
347 by their position within a bit field. The length of each category is 2
350 value. The categories MUST be listed in ascending order within the tag.
[all …]
|
| /Linux-v5.4/Documentation/vm/ |
| D | page_frags.rst | 8 which resides within a 0 or higher order compound page. Multiple
9 fragments within that page are individually refcounted, in the page's
34 only usable within the softirq context.
|
| /Linux-v5.4/Documentation/devicetree/bindings/pci/ |
| D | ti-pci.txt | 37 should contain the register offset within syscon
47 they are locally accessed within the DIF CS space
49 they are locally accessed within the DIF CS2 space
55 should contain the register offset within syscon
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| D | sacos.S | 13 | Accuracy and Monotonicity: The returned result is within 3 ulps in
14 | 64 significant bit, i.e. within 0.5001 ulp to 53 bits if the
|
| /Linux-v5.4/Documentation/xtensa/ |
| D | booting.rst | 19 virtual or physical address. In either case it must be within the default
20 virtual mapping. It is considered physical if it is within the range of
|
| /Linux-v5.4/Documentation/fb/ |
| D | pxafb.rst | 96 1. overlay can start at a 32-bit word aligned position within the base
130 d. the rectangle of the overlay should be within the base plane,
151 3. for YUV planar formats, these are actually not supported within the
153 and lengths of each component within the framebuffer.
|
| /Linux-v5.4/Documentation/devicetree/bindings/net/ |
| D | wiznet,w5x00.txt | 5 For each device connected to a SPI bus, define a child node within
14 - interrupts: Specify the interrupt index within the interrupt controller (referred
|
| D | microchip,enc28j60.txt | 5 For each device connected to a SPI bus, define a child node within
11 - interrupts: Specify the interrupt index within the interrupt controller (referred
|
| /Linux-v5.4/Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.txt | 28 adjustment within a range.
31 When baud rate set on controller falls within the range mentioned in this
34 Increase baud rate by 2% when set baud rate falls within range 9600 to 115200
|
| /Linux-v5.4/arch/alpha/lib/ |
| D | ev6-memset.S | 65 xor $16,$6,$1 # E : will complete write be within one quadword?
70 bic $1,7,$1 # E : fit within a single quadword?
248 xor $16,$6,$1 # E : will complete write be within one quadword?
251 bic $1,7,$1 # E : fit within a single quadword
432 xor $16,$6,$1 # E : will complete write be within one quadword?
436 bic $1,7,$1 # E : fit within a single quadword
|
| /Linux-v5.4/Documentation/devicetree/bindings/thermal/ |
| D | thermal.txt | 21 - thermal zones: used to describe thermal data within the hardware;
37 to identify uniquely the sensor instances within
105 - trip: A phandle of a trip point node within the same thermal
113 of all cooling contributions within a thermal zone.
329 /* each zone within the SoC may have its own trips */
343 /* each zone within the SoC may have its own cooling */
356 /* each zone within the SoC may have its own trips */
370 /* each zone within the SoC may have its own cooling */
383 /* each zone within the SoC may have its own trips */
397 /* each zone within the SoC may have its own cooling */
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/mmc/ |
| D | amlogic,meson-mx-sdio.txt | 30 - compatible : must be "mmc-slot" (see mmc.txt within this directory)
36 please refer to mmc.txt within this directory
|
| /Linux-v5.4/Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.txt | 16 SATA port to a combophy and a lane within that
21 - calxeda,led-order : a u32 array that map port numbers to offsets within the
|
| /Linux-v5.4/Documentation/devicetree/bindings/hwlock/ |
| D | hwlock.txt | 51 The following example has a node requesting two hwlocks, a hwlock within
53 hwlock within the hwlock device node 'hwlock2' with #hwlock-cells value of 2.
|
12345678910>>...32
