Searched full:boundaries (Results 1 – 25 of 510) sorted by relevance
12345678910>>...21
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | falloc.h | 21 * filesystem block size boundaries, but this boundary may be larger or
53 * boundaries, but this boundary may be larger or smaller depending on
70 * block size boundaries, but this boundary may be larger or smaller
|
| D | types.h | 42 * 64-bit values align to 4-byte boundaries on x86_32 (and possibly other
43 * architectures) and to 8-byte boundaries on 64-bit architectures. The new
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | gsc-hwmon.rst | 44 PWM value will be scalled depending on 6 temperature boundaries.
45 The tempeature boundaries are read-write and in millidegree Celcius and the
|
| D | adt7475.rst | 132 speed when the temperature is between the two temperature boundaries.
133 Temperature boundaries are associated to temperature channels rather than
|
| /kernel/linux/linux-5.10/arch/mips/net/ |
| D | bpf_jit_asm.S | 63 /* Offset within header boundaries */
92 /* Offset within header boundaries */
113 /* Offset within header boundaries */
145 /* Quick check. Are we within reasonable boundaries? */ \
|
| /kernel/linux/linux-5.10/drivers/char/ipmi/ |
| D | ipmi_dmi.c | 182 case 0: /* Byte boundaries */ in dmi_decode_ipmi()
185 case 1: /* 32-bit boundaries */ in dmi_decode_ipmi()
188 case 2: /* 16-byte boundaries */ in dmi_decode_ipmi()
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/intel/i40e/ |
| D | i40e_lan_hmc.h | 15 * boundaries. If we do not have the width of the variable set to the correct
48 * boundaries. If we do not have the width of the variable set to the correct
|
| /kernel/linux/linux-5.10/arch/powerpc/xmon/ |
| D | xmon_bpts.S | 7 /* Prefixed instructions can not cross 64 byte boundaries */
|
| /kernel/linux/linux-5.10/include/uapi/linux/sched/ |
| D | types.h | 83 * the utilization boundaries within which it should schedule the task. These
84 * boundaries are valuable hints to support scheduler decisions on both task
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | romfs.rst | 51 byte boundaries for fast access. The minimum space a file will take
146 aligned to 16 byte boundaries, but most hardware devices and the block
181 boundaries, thus it would be possible to directly map a big portion of
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | selection-api-configuration.rst | 39 active cropping area must lie completely inside the capture boundaries.
99 must lie completely inside the crop boundaries and the driver may
|
| /kernel/linux/linux-5.10/arch/sh/include/cpu-sh4/cpu/ |
| D | sq.h | 17 * to 32-byte boundaries, we need to be sure that all allocations are aligned.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,trx.txt | 18 TRX doesn't enforce any strict partition boundaries or size limits. All
|
| /kernel/linux/linux-5.10/arch/microblaze/ |
| D | Kconfig.platform | 17 boundary. However, if they are aligned on different boundaries
|
| /kernel/linux/linux-5.10/drivers/thermal/ |
| D | thermal_helpers.c | 121 * The function computes the next temperature boundaries by browsing
164 "new temperature boundaries: %d < x < %d\n", low, high); in thermal_zone_set_trips()
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/mediactl/ |
| D | media-controller-model.rst | 28 boundaries.
|
| /kernel/linux/linux-5.10/include/asm-generic/ |
| D | checksum.h | 22 * which always checksum on 4 octet boundaries.
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/82xx/ |
| D | pq2ads.h | 24 * only on word boundaries.
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | configfs-stp-policy-p_sys-t | 21 boundaries (which STP does), so this is off by default.
|
| /kernel/linux/linux-5.10/kernel/sched/ |
| D | pelt.c | 116 * Step 1: decay old *_sum if we crossed period boundaries. in accumulate_sum()
224 * Now we know we crossed measurement unit boundaries. The *_avg in ___update_load_sum()
228 * crossed period boundaries, finish. in ___update_load_sum()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/misc/ |
| D | qcom,fastrpc.txt | 5 invocations across DSP and APPS boundaries. This enables developers
|
| /kernel/linux/linux-5.10/arch/ia64/include/asm/ |
| D | checksum.h | 12 * which always checksum on 4 octet boundaries.
|
| /kernel/linux/linux-5.10/arch/alpha/include/asm/ |
| D | checksum.h | 9 * which always checksum on 4 octet boundaries.
|
| /kernel/linux/linux-5.10/Documentation/doc-guide/ |
| D | maintainer-profile.rst | 12 It's worth noting, though, that the boundaries of this subsystem are rather
|
| /kernel/linux/linux-5.10/arch/arm64/mm/ |
| D | mmap.c | 37 * such boundaries. in valid_phys_addr_range()
|
12345678910>>...21