Searched full:within (Results 1 – 25 of 874) sorted by relevance
12345678910>>...35
| /Documentation/ABI/stable/ |
| D | sysfs-devices-system-cpu | 64 Description: internal kernel map of CPUs within the same core.
69 Description: human-readable list of CPUs within the same core.
86 Description: internal kernel map of CPUs within the same die.
94 Description: human-readable list of CPUs within the same die.
99 Description: internal kernel map of CPUs within the same cluster.
103 Description: human-readable list of CPUs within the same cluster.
108 Description: internal kernel map of cpuX's hardware threads within the same
113 Description: human-readable list of cpuX's hardware threads within the same
119 Description: internal kernel map of cpuX's hardware threads within the same
124 Description: human-readable list of cpuX's hardware threads within the same
|
| /Documentation/devicetree/bindings/ptp/ |
| D | ptp-ines.txt | 7 port index within the IP core.
14 Required format of the port handle within the PHY node:
17 the port channel within the IP core
|
| /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)
|
| /Documentation/admin-guide/perf/ |
| D | arm-ni.rst | 5 NI-700 and friends implement a distinct PMU for each clock domain within the
8 the clock domain ID within that particular instance. If multiple NI instances
9 exist within a system, the PMU devices can be correlated with the underlying
|
| /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.
41 There are 4 power domains within DAPM:
121 Inter widget audio data buffer within a DSP.
128 Sample Rate Converter within DSP or CODEC
130 Asynchronous Sample Rate Converter within DSP or CODEC
182 audio paths within the audio subsystem. They have the following form:
301 Widgets are connected to each other within the codec, platform and machine by
362 An endpoint is a start or end point (widget) of an audio signal within the
|
| /Documentation/ABI/testing/ |
| D | debugfs-scmi-raw | 10 entry if it arrived within the configured timeout.
25 entry if it arrived within the configured timeout.
27 from this same entry too if it arrived within the configured
78 entry if it arrived on channel <m> within the configured
102 entry if it arrived on channel <m> within the configured
105 from this same entry too if it arrived within the configured
|
| D | sysfs-devices | 9 devices within this tree will change.
15 within the /sys/devices tree of the individual devices.
|
| /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 …]
|
| /Documentation/mm/ |
| D | page_frags.rst | 6 which resides within a 0 or higher order compound page. Multiple
7 fragments within that page are individually refcounted, in the page's
32 only usable within the softirq context.
|
| /Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.yaml | 44 alphabetical port name and an integer GPIO name within the port. For
48 of implemented GPIOs within each port varies. GPIO registers within a
52 port, and the mapping from port name to register offset within a
56 The values chosen for the names are alphabetically sorted within a
61 signal represents the aggregate status for all GPIOs within a set of
71 different CPUs to each handle subsets of the interrupts within a port.
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | xlnx,versal-wwdt.yaml | 15 window with 32 bit width. Write to the watchdog timer within
18 restarted within the open window time. If software tries to restart
|
| /Documentation/arch/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
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | fixed-cell.yaml | 32 Offset in bit within the address range specified by reg.
35 Size in bit within the address range specified by reg.
|
| /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.
|
| /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
|
| /Documentation/scheduler/ |
| D | sched-bwc.rst | 12 The bandwidth allowed for a group is specified using a quota and period. Within
23 within each of these updates is tunable and described as the "slice".
51 have a p(95)*p(95) = 90.25% chance both tasks are within their quota and
70 Quota, period and burst are managed within the cpu subsystem via cgroupfs.
77 - cpu.cfs_quota_us: run-time replenished within a period (in microseconds)
146 within a hierarchy:
155 a. it fully consumes its own quota within a period
156 b. a parent's quota is fully consumed within its period
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | ti,omap-mailbox.yaml | 21 controller within a processor subsystem, and there can be more than one line
38 combine multiple clusters into a single IP block present within the Main
49 within a SoC. The sub-mailboxes (actual communication channels) are
74 fifo number within a mailbox cluster.
84 user id number within a mailbox cluster.
89 The omap-sub-mailbox is a child node within a Mailbox controller device
151 description: Number of h/w fifo queues within the mailbox IP block.
|
| /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
|
| /Documentation/hwmon/ |
| D | lm95245.rst | 34 is given within a range of -127 to +127.875 degrees. Remote temperatures are
35 given within a range of -127 to +255 degrees. Resolution depends on
|
| /Documentation/driver-api/tty/ |
| D | tty_ldisc.rst | 29 discipline. The reference count of the tty_ldisc structure within a tty counts
31 the number of threads of execution within an ldisc method (plus those about to
78 in this situation if used within these functions. Ldisc and driver code
|
| /Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 73 defined functional units within the pvrusb2 driver and bears no
82 or is otherwise instanced within the data structures implemented
93 messages that can be enabled within the driver.
106 interact with the Conexant mpeg2 encoder chip within the pvrusb2
128 within the jurisdiction of pvrusb-context not here).
153 operate corresponding chips within the pvrusb2 device. It is
|
| /Documentation/devicetree/bindings/rtc/ |
| D | atmel,at91sam9260-rtt.yaml | 45 - description: Offset within the GPBR block.
49 and the second one encodes the offset within the GPBR block (or in
|
| /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
|
12345678910>>...35