Home
last modified time | relevance | path

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

12345678910

/Linux-v6.1/Documentation/devicetree/bindings/arm/mstar/
Dmstar.yaml26 - 100ask,dongshanpione # 100ask DongShanPiOne
/Linux-v6.1/arch/arm/boot/dts/
Dmstar-infinity2m-ssd202d-100ask-dongshanpione.dts12 compatible = "100ask,dongshanpione", "mstar,infinity2m";
/Linux-v6.1/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
Dabituguru-datasheet.rst71 terminology for the addressing within a bank this is not 100% correct, in
141 don't ask why this is the way it is.
273 Flag 0x80 to enable control, Fan runs at 100% when disabled.
/Linux-v6.1/fs/afs/
Dafs_fs.h45 VRESTARTING = -100, /* Server is restarting */
56 VMOVED = 111, /* volume moved to new server - ask this FS where */
/Linux-v6.1/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()
/Linux-v6.1/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 */
/Linux-v6.1/mm/
Dshuffle.c43 * need to ask questions like... in shuffle_valid_page()
140 if ((i % (100 * order_pages)) == 0) { in __shuffle_zone()
/Linux-v6.1/Documentation/admin-guide/mm/damon/
Dusage.rst291 size quota for each scheme. In detail, users can ask DAMON to try to use only
347 should ask DAMON sysfs interface to updte the content of the files for the
413 example, below commands set those values to 5 ms, 100 ms, 1,000 ms, 10 and
475 example, below commands will set a couple of address ranges, ``1-100`` and
476 ``100-200`` as the initial monitoring target region of pid 42, which is the
478 ranges, ``20-40`` and ``50-100`` as that of pid 4242, which is the second one
484 # echo "0 1 100
485 0 100 200
487 1 50 100" > init_regions
614 # scheme+=" 0 0 100" # prioritization weights
/Linux-v6.1/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,
/Linux-v6.1/tools/perf/Documentation/
Dperf-top.txt218 sum of shown entries will be always 100%. "absolute" means it retains
310 Start perf top and ask it to only consider the cycles events when a
316 Alternatively one can ask for --group and then two overhead columns
/Linux-v6.1/Documentation/scsi/
Daha152x.rst32 DELAY: bus reset delay (default 100)
180 ask the user for verification. This might on not yet partitioned
/Linux-v6.1/drivers/i2c/busses/
Di2c-pnx.c28 #define I2C_PNX_SPEED_KHZ_DEFAULT 100
309 * or we didn't 'ask' for it yet. in i2c_pnx_master_rcv()
336 * Now we'll 'ask' for data: in i2c_pnx_master_rcv()
701 * desired serial period is 10000 ns (100 kHz), then CLKHI would be in i2c_pnx_probe()
702 * set to 0.5*(f_sys/f_i2c)-2=0.5*(20e6/100e3)-2=98. The actual value in i2c_pnx_probe()
/Linux-v6.1/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).
/Linux-v6.1/drivers/input/keyboard/
Dlkkbd.c71 static int bell_volume = 100; /* % */
73 MODULE_PARM_DESC(bell_volume, "Bell volume (in %). default is 100%");
75 static int keyclick_volume = 100; /* % */
77 MODULE_PARM_DESC(keyclick_volume, "Keyclick volume (in %), default is 100%");
79 static int ctrlclick_volume = 100; /* % */
81 MODULE_PARM_DESC(ctrlclick_volume, "Ctrlclick volume (in %), default is 100%");
320 if (volume_percent > 100) in volume_to_hw()
321 volume_percent = 100; in volume_to_hw()
568 /* Ask for ID */ in lkkbd_reinit()
/Linux-v6.1/net/batman-adv/
Dbat_v_elp.c64 * Return: The throughput towards the given neighbour in multiples of 100kpbs
83 /* if this is a wireless device, then ask its throughput through in batadv_v_elp_get_throughput()
114 return sinfo.expected_throughput / 100; in batadv_v_elp_get_throughput()
207 * to it in the last 100 milliseconds: this is the rate control in batadv_v_elp_wifi_neigh_probe()
303 * value retrieved in this step might be 100ms old because the in batadv_v_elp_periodic_work()
/Linux-v6.1/drivers/virt/vboxguest/
Dvmmdev.h135 * cursor itself, the guest installs a hardware mouse driver. Don't ask the
289 VBOXGUEST_FACILITY_TYPE_VBOX_SERVICE = 100,
305 VBOXGUEST_FACILITY_STATUS_TERMINATING = 100,
/Linux-v6.1/arch/mips/cavium-octeon/executive/
Dcvmx-helper-rgmii.c212 * Each pause frame transmitted will ask for about 10M in __cvmx_helper_rgmii_enable()
376 } else if (link_info.s.speed == 100) { in __cvmx_helper_rgmii_link_set()
389 } else if (link_info.s.speed == 100) { in __cvmx_helper_rgmii_link_set()
400 if ((link_info.s.speed == 10) || (link_info.s.speed == 100)) { in __cvmx_helper_rgmii_link_set()
/Linux-v6.1/drivers/crypto/qat/qat_common/
Dadf_pfvf_vf_proto.c16 #define ADF_PFVF_MSG_ACK_MAX_RETRY 100
271 * - VF expects a newer (longer) version, so we must not ask for in adf_send_vf2pf_blkmsg_req()
/Linux-v6.1/fs/xfs/libxfs/
Dxfs_rmap_btree.c643 xfs_extlen_t *ask, in xfs_rmapbt_calc_reserves() argument
673 *ask += max(agblocks / 100, xfs_rmapbt_max_size(mp, agblocks)); in xfs_rmapbt_calc_reserves()
/Linux-v6.1/drivers/net/wireless/realtek/rtlwifi/
Dps.c94 if (rfwait_cnt > 100) in rtl_ps_set_rf_state()
252 /* because when link with ap, mac80211 will ask us in rtl_ips_nic_off()
254 * this will cause link failed, so we delay 100ms here in rtl_ips_nic_off()
257 &rtlpriv->works.ips_nic_off_wq, MSECS(100)); in rtl_ips_nic_off()
420 * bt_ccoexist may ask to enter lps. in rtl_lps_enter_core()
/Linux-v6.1/drivers/comedi/drivers/
Ddt3000.c39 * for the 3k series. However, if you ask nicely, they might send
128 #define DPR_CMD_TIMEOUT 100
405 100 * 16 * 65535); in dt3k_ai_cmdtest()
430 dt3k_ns_to_timer(100, &arg, cmd->flags); in dt3k_ai_cmdtest()
477 tscandiv = dt3k_ns_to_timer(100, &cmd->scan_begin_arg, in dt3k_ai_cmd()
/Linux-v6.1/drivers/media/usb/au0828/
Dau0828-input.c314 /* This is how often we ask the chip for IR information */ in au0828_rc_register()
315 ir->polling = 100; /* ms */ in au0828_rc_register()
/Linux-v6.1/tools/objtool/Documentation/
Dobjtool.txt294 If you're 100% sure the code won't affect stack traces, or if you're
415 Feel free to ask the objtool maintainer for help.
421 If you _really_ need objtool to ignore something, and are 100% sure

12345678910