/openbmc/linux/Documentation/devicetree/bindings/arm/mstar/ |
H A D | mstar.yaml | 26 - 100ask,dongshanpione # 100ask DongShanPiOne
|
/openbmc/linux/arch/arm/boot/dts/sigmastar/ |
H A D | mstar-infinity2m-ssd202d-100ask-dongshanpione.dts | 12 compatible = "100ask,dongshanpione", "mstar,infinity2m";
|
H A D | Makefile | 4 mstar-infinity2m-ssd202d-100ask-dongshanpione.dtb \
|
/openbmc/linux/Documentation/hwmon/ |
H A D | f71805f.rst | 85 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 D | f71882fg.rst | 154 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
|
/openbmc/linux/Documentation/devicetree/bindings/riscv/ |
H A D | sunxi.yaml | 24 - const: 100ask,dongshan-nezha-stu
|
/openbmc/linux/fs/afs/ |
H A D | afs_fs.h | 45 VRESTARTING = -100, /* Server is restarting */ 56 VMOVED = 111, /* volume moved to new server - ask this FS where */
|
/openbmc/linux/arch/riscv/boot/dts/allwinner/ |
H A D | sun20i-d1-dongshan-nezha-stu.dts | 14 compatible = "100ask,dongshan-nezha-stu", "allwinner,sun20i-d1";
|
/openbmc/linux/drivers/net/wireless/ti/wl1251/ |
H A D | init.c | 204 /* 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()
|
/openbmc/linux/lib/ |
H A D | test_linear_ranges.c | 17 * 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 */
|
/openbmc/linux/Documentation/process/ |
H A D | stable-kernel-rules.rst | 11 - 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
|
/openbmc/linux/mm/ |
H A D | shuffle.c | 43 * need to ask questions like... in shuffle_valid_page() 140 if ((i % (100 * order_pages)) == 0) { in __shuffle_zone()
|
/openbmc/linux/include/linux/firmware/intel/ |
H A D | stratix10-svc-client.h | 81 * @COMMAND_RECONFIG: ask for FPGA configuration preparation, return status 171 COMMAND_MBOX_SEND_CMD = 100,
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | svga.rst | 20 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,
|
/openbmc/linux/tools/perf/Documentation/ |
H A D | perf-top.txt | 221 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
|
/openbmc/linux/Documentation/scsi/ |
H A D | aha152x.rst | 32 DELAY: bus reset delay (default 100) 180 ask the user for verification. This might on not yet partitioned
|
/openbmc/linux/Documentation/timers/ |
H A D | hrtimers.rst | 7 One might ask the question: we already have a timer subsystem 76 from 250 Hz to 100 HZ (or even smaller).
|
/openbmc/linux/drivers/i2c/busses/ |
H A D | i2c-pnx.c | 27 #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()
|
/openbmc/linux/drivers/input/keyboard/ |
H A D | lkkbd.c | 71 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()
|
/openbmc/linux/net/batman-adv/ |
H A D | bat_v_elp.c | 63 * 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()
|
/openbmc/linux/drivers/virt/vboxguest/ |
H A D | vmmdev.h | 135 * 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,
|
/openbmc/linux/arch/mips/cavium-octeon/executive/ |
H A D | cvmx-helper-rgmii.c | 212 * 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()
|
/openbmc/qemu/hw/usb/ |
H A D | quirks-ftdi-ids.h | 90 * ASK.fr devices 92 #define FTDI_ASK_RDR400_PID 0xC991 /* ASK RDR 400 series card reader */ 210 * The previously included PID for the UO 100 module was incorrect. 211 * In fact, that PID was for ELV's UR 100 USB-RS232 converter (0xFB58). 213 * Armin Laeuger originally sent the PID for the UM 100 module. 217 #define FTDI_ELV_KL100_PID 0xE002 /* ELV Kfz-Leistungsmesser KL 100 */ 226 #define FTDI_ELV_UMS100_PID 0xE0EB /* ELV USB Master-Slave Schaltsteckdose UMS 100 */ 233 #define FTDI_ELV_PCK100_PID 0xE0F2 /* PC-Kabeltester (PCK 100) */ 248 #define FTDI_ELV_UR100_PID 0xFB58 /* USB-RS232-Umsetzer (UR 100) */ 249 #define FTDI_ELV_UM100_PID 0xFB5A /* USB-Modul UM 100 */ [all …]
|
/openbmc/linux/drivers/crypto/intel/qat/qat_common/ |
H A D | adf_pfvf_vf_proto.c | 16 #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()
|
/openbmc/linux/drivers/net/wireless/realtek/rtlwifi/ |
H A D | ps.c | 94 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()
|