Home
last modified time | relevance | path

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

12345678910

/linux/Documentation/devicetree/bindings/arm/mstar/
H A Dmstar.yaml26 - 100ask,dongshanpione # 100ask DongShanPiOne
/linux/Documentation/hwmon/
H A 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.
H A 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
/linux/arch/arm/boot/dts/sigmastar/
H A Dmstar-infinity2m-ssd202d-100ask-dongshanpione.dts12 compatible = "100ask,dongshanpione", "mstar,infinity2m";
H A DMakefile4 mstar-infinity2m-ssd202d-100ask-dongshanpione.dtb \
/linux/Documentation/devicetree/bindings/riscv/
H A Dsunxi.yaml24 - const: 100ask,dongshan-nezha-stu
/linux/arch/riscv/boot/dts/allwinner/
H A Dsun20i-d1-dongshan-nezha-stu.dts14 compatible = "100ask,dongshan-nezha-stu", "allwinner,sun20i-d1";
/linux/fs/afs/
H A Dafs_fs.h45 VRESTARTING = -100, /* Server is restarting */
56 VMOVED = 111, /* volume moved to new server - ask this FS where */
/linux/drivers/rtc/
H A Drtc-ssd202d.c75 ret = read_poll_timeout(read_iso_ctrl_ack, val, val == (i % 2), 100, in ssd202d_rtc_isoctrl()
76 20 * 100, true, priv->base); in ssd202d_rtc_isoctrl()
87 ret = read_poll_timeout(read_iso_en, val, val, 100, 22 * 100, true, priv->base); in ssd202d_rtc_isoctrl()
100 /* Ask for the content of an RTC value into RDDATA by gating iso_en, in ssd202d_rtc_read_reg()
/linux/drivers/net/wireless/ti/wl1251/
H A 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/lib/
H A 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/Documentation/process/
H A 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
/linux/mm/
H A Dshuffle.c43 * need to ask questions like... in shuffle_valid_page()
140 if ((i % (100 * order_pages)) == 0) { in __shuffle_zone()
/linux/Documentation/admin-guide/
H A 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/include/linux/firmware/intel/
H A Dstratix10-svc-client.h81 * @COMMAND_RECONFIG: ask for FPGA configuration preparation, return status
171 COMMAND_MBOX_SEND_CMD = 100,
/linux/drivers/i2c/busses/
H A Di2c-pnx.c27 #define I2C_PNX_SPEED_KHZ_DEFAULT 100
285 * or we didn't 'ask' for it yet. in i2c_pnx_master_rcv()
312 * Now we'll 'ask' for data: in i2c_pnx_master_rcv()
668 * desired serial period is 10000 ns (100 kHz), then CLKHI would be in i2c_pnx_probe()
669 * set to 0.5*(f_sys/f_i2c)-2=0.5*(20e6/100e3)-2=98. The actual value in i2c_pnx_probe()
/linux/Documentation/admin-guide/mm/damon/
H A Dusage.rst348 users should ask DAMON sysfs interface to update the content of the file for
465 should ask DAMON sysfs interface to update the content of the files for the
639 example, below commands set those values to 5 ms, 100 ms, 1,000 ms, 10 and
702 example, below commands will set a couple of address ranges, ``1-100`` and
703 ``100-200`` as the initial monitoring target region of pid 42, which is the
705 ranges, ``20-40`` and ``50-100`` as that of pid 4242, which is the second one
711 # echo "0 1 100 \
712 0 100 200 \
714 1 50 100" > init_regions
835 # scheme+=" 0 0 100" # prioritization weights
/linux/Documentation/scsi/
H A Daha152x.rst32 DELAY: bus reset delay (default 100)
180 ask the user for verification. This might on not yet partitioned
/linux/Documentation/timers/
H A Dhrtimers.rst7 One might ask the question: we already have a timer subsystem
76 from 250 Hz to 100 HZ (or even smaller).
/linux/tools/perf/Documentation/
H A Dperf-top.txt225 sum of shown entries will be always 100%. "absolute" means it retains
351 Start perf top and ask it to only consider the cycles events when a
357 Alternatively one can ask for a group and then two overhead columns
/linux/drivers/input/keyboard/
H A 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/net/batman-adv/
H A Dbat_v_elp.c63 * Return: The throughput towards the given neighbour in multiples of 100kpbs
82 /* if this is a wireless device, then ask its throughput through in batadv_v_elp_get_throughput()
113 return sinfo.expected_throughput / 100; in batadv_v_elp_get_throughput()
206 * to it in the last 100 milliseconds: this is the rate control in batadv_v_elp_wifi_neigh_probe()
302 * value retrieved in this step might be 100ms old because the in batadv_v_elp_periodic_work()
/linux/drivers/virt/vboxguest/
H A 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/arch/mips/cavium-octeon/executive/
H A 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/drivers/crypto/intel/qat/qat_common/
H A 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()

12345678910