Home
last modified time | relevance | path

Searched +full:100 +full:ask (Results 1 – 25 of 498) sorted by relevance

12345678910>>...20

/kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/mstar/
Dmstar.yaml26 - 100ask,dongshanpione # 100ask DongShanPiOne
/kernel/linux/linux-6.6/arch/arm/boot/dts/sigmastar/
DMakefile4 mstar-infinity2m-ssd202d-100ask-dongshanpione.dtb \
Dmstar-infinity2m-ssd202d-100ask-dongshanpione.dts12 compatible = "100ask,dongshanpione", "mstar,infinity2m";
/kernel/linux/linux-5.10/Documentation/hwmon/
Df71805f.rst85 in2 VIN2 VRAM 100K 100K 2.00 ~1.25 V [1]_
86 in3 VIN3 VCHIPSET 47K 100K 1.47 2.24 V [2]_
166 You ask for a specific PWM duty cycle or DC voltage by writing to the
177 You ask for a specific fan speed by writing to the fan<n>_target file.
Df71882fg.rst154 voltage) mode, where 0-100% duty cycle (0-100% of 12V) is specified. And RPM
156 gets specified as 0-100% of the fan#_full_speed file.
158 Since both modes work in a 0-100% (mapped to 0-255) scale, there isn't a
160 important difference is that in RPM mode the 0-100% controls the fan speed
161 between 0-100% of fan#_full_speed. It is assumed that if the BIOS programs
176 You ask for a specific PWM duty cycle / DC voltage or a specific % of
/kernel/linux/linux-6.6/Documentation/hwmon/
Df71805f.rst85 in2 VIN2 VRAM 100K 100K 2.00 ~1.25 V [1]_
86 in3 VIN3 VCHIPSET 47K 100K 1.47 2.24 V [2]_
166 You ask for a specific PWM duty cycle or DC voltage by writing to the
177 You ask for a specific fan speed by writing to the fan<n>_target file.
Df71882fg.rst154 voltage) mode, where 0-100% duty cycle (0-100% of 12V) is specified. And RPM
156 gets specified as 0-100% of the fan#_full_speed file.
158 Since both modes work in a 0-100% (mapped to 0-255) scale, there isn't a
160 important difference is that in RPM mode the 0-100% controls the fan speed
161 between 0-100% of fan#_full_speed. It is assumed that if the BIOS programs
176 You ask for a specific PWM duty cycle / DC voltage or a specific % of
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/riscv/
Dsunxi.yaml24 - const: 100ask,dongshan-nezha-stu
/kernel/linux/linux-6.6/fs/afs/
Dafs_fs.h45 VRESTARTING = -100, /* Server is restarting */
56 VMOVED = 111, /* volume moved to new server - ask this FS where */
/kernel/linux/linux-5.10/arch/mips/include/asm/
Dcompat.h14 #define COMPAT_USER_HZ 100
94 #define _COMPAT_NSIG 128 /* Don't ask !$@#% ... */
/kernel/linux/linux-6.6/arch/riscv/boot/dts/allwinner/
Dsun20i-d1-dongshan-nezha-stu.dts14 compatible = "100ask,dongshan-nezha-stu", "allwinner,sun20i-d1";
/kernel/linux/linux-5.10/fs/afs/
Dafs_fs.h45 VRESTARTING = -100, /* Server is restarting */
56 VMOVED = 111, /* volume moved to new server - ask this FS where */
/kernel/linux/linux-6.6/drivers/net/wireless/ti/wl1251/
Dinit.c204 /* we now ask for the firmware built memory map */ in wl1251_hw_init_mem_config()
226 (QOS_TX_HIGH_BE_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
228 (QOS_TX_LOW_BE_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
232 (QOS_TX_HIGH_BK_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
234 (QOS_TX_LOW_BK_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
238 (QOS_TX_HIGH_VI_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
240 (QOS_TX_LOW_VI_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
244 (QOS_TX_HIGH_VO_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
246 (QOS_TX_LOW_VO_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
/kernel/linux/linux-5.10/drivers/net/wireless/ti/wl1251/
Dinit.c204 /* we now ask for the firmware built memory map */ in wl1251_hw_init_mem_config()
226 (QOS_TX_HIGH_BE_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
228 (QOS_TX_LOW_BE_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
232 (QOS_TX_HIGH_BK_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
234 (QOS_TX_LOW_BK_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
238 (QOS_TX_HIGH_VI_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
240 (QOS_TX_LOW_VI_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
244 (QOS_TX_HIGH_VO_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
246 (QOS_TX_LOW_VO_DEF * num_blocks) / 100; in wl1251_hw_init_txq_fill()
/kernel/linux/linux-5.10/lib/
Dtest_linear_ranges.c17 * walking through all the possible execution branches will nail down 100% of
22 * Ask people to provide line coverage and they do. I've seen clever tools
30 * Especially if you were are asked to proivde 100% line-coverage x_x. So what
63 * values (4): 100 150 200 250
82 #define RANGE2_MIN 100
90 /* 100, 150, 200, 250 */
/kernel/linux/linux-6.6/lib/
Dtest_linear_ranges.c17 * walking through all the possible execution branches will nail down 100% of
22 * Ask people to provide line coverage and they do. I've seen clever tools
30 * Especially if you were are asked to proivde 100% line-coverage x_x. So what
63 * values (4): 100 150 200 250
82 #define RANGE2_MIN 100
90 /* 100, 150, 200, 250 */
/kernel/linux/linux-6.6/Documentation/process/
Dstable-kernel-rules.rst11 - It cannot be bigger than 100 lines, with context.
47 2. Ask the stable team to pick up a patch already mainlined.
59 When using option 2 or 3 you can ask for your change to be included in specific
/kernel/linux/linux-6.6/mm/
Dshuffle.c43 * need to ask questions like... in shuffle_valid_page()
140 if ((i % (100 * order_pages)) == 0) { in __shuffle_zone()
/kernel/linux/linux-5.10/mm/
Dshuffle.c44 * need to ask questions like... in shuffle_valid_page()
141 if ((i % (100 * order_pages)) == 0) { in __shuffle_zone()
/kernel/linux/linux-6.6/include/linux/firmware/intel/
Dstratix10-svc-client.h81 * @COMMAND_RECONFIG: ask for FPGA configuration preparation, return status
171 COMMAND_MBOX_SEND_CMD = 100,
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dperf-top.txt217 sum of shown entries will be always 100%. "absolute" means it retains
297 Start perf top and ask it to only consider the cycles events when a
303 Alternatively one can ask for --group and then two overhead columns
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dsvga.rst20 Short intro for the impatient: Just use vga=ask for the first time,
96 program will try to ask the BIOS for all possible video mode numbers and test
128 (Usually 940=80x43, 941=132x25, 942=132x44, 943=80x60, 944=100x60,
/kernel/linux/linux-6.6/Documentation/admin-guide/
Dsvga.rst20 Short intro for the impatient: Just use vga=ask for the first time,
96 program will try to ask the BIOS for all possible video mode numbers and test
128 (Usually 940=80x43, 941=132x25, 942=132x44, 943=80x60, 944=100x60,
/kernel/linux/linux-6.6/tools/perf/Documentation/
Dperf-top.txt221 sum of shown entries will be always 100%. "absolute" means it retains
317 Start perf top and ask it to only consider the cycles events when a
323 Alternatively one can ask for a group and then two overhead columns
/kernel/linux/linux-6.6/Documentation/timers/
Dhrtimers.rst7 One might ask the question: we already have a timer subsystem
76 from 250 Hz to 100 HZ (or even smaller).

12345678910>>...20