/linux/drivers/pinctrl/mvebu/ |
H A D | pinctrl-kirkwood.c | 19 #define V(f6180, f6190, f6192, f6281, f6282, dx4122, dx1135) \ macro 25 VARIANT_MV88F6180 = V(1, 0, 0, 0, 0, 0, 0), 26 VARIANT_MV88F6190 = V(0, 1, 0, 0, 0, 0, 0), 27 VARIANT_MV88F6192 = V(0, 0, 1, 0, 0, 0, 0), 28 VARIANT_MV88F6281 = V(0, 0, 0, 1, 0, 0, 0), 29 VARIANT_MV88F6282 = V(0, 0, 0, 0, 1, 0, 0), 30 VARIANT_MV98DX4122 = V(0, 0, 0, 0, 0, 1, 0), 31 VARIANT_MV98DX1135 = V(0, 0, 0, 0, 0, 0, 1), 36 MPP_VAR_FUNCTION(0x0, "gpio", NULL, V(1, 1, 1, 1, 1, 1, 1)), 37 MPP_VAR_FUNCTION(0x1, "nand", "io2", V(1, 1, 1, 1, 1, 1, 1)), [all …]
|
/linux/tools/memory-model/ |
H A D | linux-kernel.def | 10 WRITE_ONCE(X,V) { __store{once}(X,V); } 13 smp_store_release(X,V) { __store{release}(*X,V); } 31 xchg(X,V) __xchg{mb}(X,V) 32 xchg_relaxed(X,V) __xchg{once}(X,V) 33 xchg_release(X,V) __xchg{release}(X,V) 34 xchg_acquire(X,V) __xchg{acquire}(X,V) 35 cmpxchg(X,V,W) __cmpxchg{mb}(X,V,W) 62 atomic_set(X,V) { WRITE_ONCE(*X,V); } 66 atomic_add(V,X) { __atomic_op(X,+,V); } 67 atomic_sub(V,X) { __atomic_op(X,-,V); } [all …]
|
/linux/Documentation/hwmon/ |
H A D | mc13783-adc.rst | 47 0 Battery Voltage (BATT) 2.50 - 4.65V -2.40V 49 2 Application Supply (BP) 2.50 - 4.65V -2.40V 51 0 - 20V /10 55 1.50 - 3.50V -1.20V 57 0 - 2.55V / x0.9 / No 58 8 General Purpose ADIN8 0 - 2.30V No 59 9 General Purpose ADIN9 0 - 2.30V No 73 0 Battery Voltage (BATT) 0 - 4.8V /2 77 0 - 20V /10 79 Touchscreen X-plate 1 0 - 2.4V No [all …]
|
H A D | dme1737.rst | 94 in0: +5VTR (+5V standby) 0V - 6.64V 97 in3: +5V 0V - 6.64V 98 in4: +12V 0V - 16V 100 in6: Vbat (+3.0V) 0V - 4.38V 104 in0: +2.5V 0V - 3.32V 107 in3: +5V 0V - 6.64V 108 in4: +12V 0V - 16V 110 in6: Vbat (+3.0V) 0V - 4.38V 120 in6: Vbat (+3.0V) 0V - 4.38V 130 in6: Vbat (+3.0V) 0V - 4.38V [all …]
|
/linux/arch/powerpc/lib/ |
H A D | xor_vmx.c | 25 unative_t *V = (unative_t *)V##_in; \ 26 unative_t V##_0, V##_1, V##_2, V##_3 28 #define LOAD(V) \ argument 30 V##_0 = V[0]; \ 31 V##_1 = V[1]; \ 32 V##_2 = V[2]; \ 33 V##_3 = V[3]; \ 38 V[0] = V##_0; \ 39 V[1] = V##_1; \ 40 V[2] = V##_2; \ [all …]
|
/linux/arch/m68k/fpsp040/ |
H A D | slogn.S | 389 |--[U + V*(A1+V*(A3+V*A5))] + [U*V*(A2+V*(A4+V*A6))] 400 fmulx %fp3,%fp1 | ...V*(A4+V*A6) 401 fmulx %fp3,%fp2 | ...V*(A3+V*A5) 403 faddd LOGA2,%fp1 | ...A2+V*(A4+V*A6) 406 fmulx %fp3,%fp1 | ...V*(A2+V*(A4+V*A6)) 408 fmulx %fp3,%fp2 | ...V*(A1+V*(A3+V*A5)), FP3 RELEASED 410 fmulx %fp0,%fp1 | ...U*V*(A2+V*(A4+V*A6)) 411 faddx %fp2,%fp0 | ...U+V*(A1+V*(A3+V*A5)), FP2 RELEASED 413 faddx (%a0),%fp1 | ...LOG(F)+U*V*(A2+V*(A4+V*A6)) 436 |--LET V=U*U, W=V*V, CALCULATE [all …]
|
/linux/Documentation/translations/zh_CN/arch/riscv/ |
H A D | boot.rst | 11 RISC-V内核启动要求和限制 17 这份文档描述了RISC-V内核对引导加载程序和固件的期望,以及任何开发者在接触 24 RISC-V内核对引导加载程序和平台固件有以下要求: 29 RISC-V内核期望: 37 RISC-V内核期望: 44 RISC-V内核在直接映射中不能映射任何常驻内存或用PMPs保护的内存, 56 固件可以将设备树或ACPI表传递给RISC-V内核。 83 使用UEFI启动时,RISC-V内核将只使用EFI内存映射来填充系统内存。 94 RISC-V内核。EFI stub使用以下方法之一获取引导hartid: 105 RISC-V内核的早期启动过程遵循以下约束: [all …]
|
H A D | patch-acceptance.rst | 18 RISC-V指令集体系结构是公开开发的: 20 生更改---有时以不兼容的方式对以前的草案进行更改。这种灵活性可能会给RISC-V Linux 22 们希望推广同样的规则到即将被内核合并的RISC-V相关代码。 26 我们仅接受相关标准已经被RISC-V基金会标准为“已批准”或“已冻结”的扩展或模块的补丁。 29 此外,RISC-V规范允许爱好者创建自己的自定义扩展。这些自定义拓展不需要通过RISC-V 30 基金会的任何审核或批准。为了避免将爱好者一些特别的RISC-V拓展添加进内核代码带来 31 的维护复杂性和对性能的潜在影响,我们将只接受RISC-V基金会正式冻结或批准的的扩展
|
H A D | vm-layout.rst | 12 RISC-V Linux上的虚拟内存布局 18 这份文件描述了RISC-V Linux内核使用的虚拟内存布局。 20 32位 RISC-V Linux 内核 23 RISC-V Linux Kernel SV32 28 64位 RISC-V Linux 内核 31 RISC-V特权架构文档指出,64位地址 "必须使第63-48位值都等于第47位,否则将发生缺页异常。":这将虚 32 拟地址空间分成两半,中间有一个非常大的洞,下半部分是用户空间所在的地方,上半部分是RISC-V Linux 35 RISC-V Linux Kernel SV39 71 RISC-V Linux Kernel SV48
|
/linux/drivers/media/dvb-frontends/ |
H A D | mb86a16.c | 776 (*(V + 30 + v) > *(V + 30 + v - 1)) && in swp_freq_calcuation() 785 (*(V + 30 + v - 1) > *(V + 30 + v)) && in swp_freq_calcuation() 801 (*(V + 30 + v) > *(V + 30 + v - 2)) && in swp_freq_calcuation() 806 if (*(V + 30 + v) >= *(V + 30 + v - 1)) { in swp_freq_calcuation() 830 (*(V + 30 + v + 1) > *(V + 30 + v)) && in swp_freq_calcuation() 839 (*(V + 30 + v) > *(V + 30 + v + 1)) && in swp_freq_calcuation() 840 (*(V + 30 + v) > *(V + 30 + v + 2)) && in swp_freq_calcuation() 849 (*(V + 30 + v + 1) > *(V + 30 + v)) && in swp_freq_calcuation() 865 (*(V + 30 + v) > *(V + 30 + v + 2)) && in swp_freq_calcuation() 867 (*(V + 30 + v) > *(V + 30 + v + 3)) && in swp_freq_calcuation() [all …]
|
/linux/Documentation/virt/hyperv/ |
H A D | overview.rst | 6 enlightened guest on Microsoft's Hyper-V hypervisor. Hyper-V 10 partitions. In this documentation, references to Hyper-V usually 15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests 16 are supported on both. The functionality and behavior of Hyper-V is 19 Linux Guest Communication with Hyper-V 21 Linux guests communicate with Hyper-V in four different ways: 24 some guest actions trap to Hyper-V. Hyper-V emulates the action and 29 Hyper-V, passin 55 Hyper-V Top Level Functional Spec (TLFS)Linux Guest Communication with Hyper-V global() argument [all...] |
H A D | clocks.rst | 8 On arm64, Hyper-V virtualizes the ARMv8 architectural system counter 12 architectural system counter is functional in guest VMs on Hyper-V. 13 While Hyper-V also provides a synthetic system clock and four synthetic 15 Linux kernel in a Hyper-V guest on arm64. However, older versions 16 of Hyper-V for arm64 only partially virtualize the ARMv8 19 Linux kernel versions on these older Hyper-V versions requires an 20 out-of-tree patch to use the Hyper-V synthetic clocks/timers instead. 24 On x86/x64, Hyper-V provides guest VMs with a synthetic system clock 25 and four synthetic per-CPU timers as described in the TLFS. Hyper-V 29 Hyper-V perform [all...] |
H A D | vpci.rst | 5 In a Hyper-V guest VM, PCI pass-thru devices (also called 16 Hyper-V terminology for vPCI devices is "Discrete Device 17 Assignment" (DDA). Public documentation for Hyper-V DDA is 25 driver to interact directly with the hardware. See Hyper-V 125 a message, the Hyper-V virtual PCI driver in Linux 182 The Hyper-V virtual PCI driver implements the 201 Hyper-V which guest vCPU should be interrupted by each 216 the Hyper-V host to change the interrupt targeting and 292 in the Hyper-V virtual PCI driver. In normal VMs, 295 But in CoCo VMs, memory encryption prevents Hyper-V [all …]
|
/linux/tools/build/tests/ |
H A D | run.sh | 5 make -C ex V=1 clean > ex.out 2>&1 6 make -C ex V=1 >> ex.out 2>&1 13 make -C ex V=1 clean > /dev/null 2>&1 18 make -C ex V=1 clean > ex.out 2>&1 21 make -rR -C ex V=1 ex.o >> ex.out 2>&1 22 make -rR -C ex V=1 ex.i >> ex.out 2>&1 23 make -rR -C ex V=1 ex.s >> ex.out 2>&1 35 make -C ex V=1 clean > /dev/null 2>&1 40 make -C ex V=1 clean > ex.out 2>&1 53 make -C ex V=1 >> ex.out 2>&1 [all …]
|
/linux/Documentation/devicetree/bindings/media/i2c/ |
H A D | samsung,s5k5baf.yaml | 39 description: Analog power supply 2.8V (2.6V to 3.0V) 42 description: I/O power supply 1.8V (1.65V to 1.95V) or 2.8V (2.5V to 3.1V) 46 Regulator input power supply 1.8V (1.7V to 1.9V) or 2.8V (2.6V to 3.0)
|
H A D | thine,thp7312.yaml | 54 1.2V supply for core, PLL, MIPI rx and MIPI tx. 58 Supply for input (RX). 1.8V for MIPI, or 1.8/2.8/3.3V for parallel. 62 Supply for output (TX). 1.8V for MIPI, or 1.8/2.8/3.3V for parallel. 66 Supply for host interface. 1.8V, 2.8V, or 3.3V. 70 Supply for sensor interface. 1.8V, 2.8V, or 3.3V. 74 Supply for GPIO_0. 1.8V, 2.8V, or 3.3V. 78 Supply for GPIO_1. 1.8V, 2.8V, or 3.3V.
|
/linux/arch/alpha/kernel/ |
H A D | entry.S | 691 #define V(n) stt $f##n, FR(n) macro 692 V( 0); V( 1); V( 2); V( 3) 693 V( 4); V( 5); V( 6); V( 7) 694 V( 8); V( 9); V(10); V(11) 695 V(12); V(13); V(14); V(15) 696 V(16); V(17); V(18); V(19) 697 V(20); V(21); V(22); V(23) 698 V(24); V(25); V(26); V(27) 700 V(28); V(29); V(30)
|
/linux/arch/arm/boot/dts/samsung/ |
H A D | exynos3250-artik5.dtsi | 102 regulator-name = "VLDO1_1.0V"; 110 regulator-name = "VLDO2_1.2V"; 121 regulator-name = "VLDO3_1.8V"; 129 regulator-name = "VLDO4_1.8V"; 137 regulator-name = "VLDO5_1.0V"; 145 regulator-name = "VLDO6_1.0V"; 156 regulator-name = "VLDO7_1.8V"; 164 regulator-name = "VLDO8_3.0V"; 172 regulator-name = "VLDO9_1.2V"; 179 regulator-name = "VLDO10_1.0V"; [all …]
|
H A D | s5pv210-aquila.dts | 44 regulator-name = "V_TF_2.8V"; 89 regulator-name = "VALIVE_1.1V"; 103 regulator-name = "VADC_3.3V"; 109 regulator-name = "VTF_2.8V"; 116 regulator-name = "VCC_3.3V"; 123 regulator-name = "VCC_3.0V"; 145 regulator-name = "VPLL_1.1V"; 167 regulator-name = "CAM_A_2.8V"; 202 regulator-name = "VARM_1.2V"; 209 regulator-name = "VINT_1.2V"; [all …]
|
H A D | exynos4210-origen.dts | 45 regulator-name = "VMEM_VDD_2.8V"; 195 regulator-name = "VDD_ABB_3.3V"; 208 regulator-name = "VMIPI_1.1V"; 214 regulator-name = "VDD_RTC_1.8V"; 221 regulator-name = "VMIPI_1.8V"; 228 regulator-name = "VDD_AUD_1.8V"; 234 regulator-name = "VADC_3.3V"; 247 regulator-name = "VDD_PLL_1.1V"; 267 regulator-name = "VDD_SWB_3.3V"; 274 regulator-name = "VDD_MIF_1.2V"; [all …]
|
/linux/Documentation/fb/ |
H A D | viafb.modes | 29 # D: 25.175 MHz, H: 31.469 kHz, V: 59.94 Hz 32 # D: 24.823 MHz, H: 39.780 kHz, V: 60.00 Hz 53 # D: 31.50 MHz, H: 37.500 kHz, V: 75.00 Hz 74 # D: 36.000 MHz, H: 43.269 kHz, V: 85.00 Hz 95 # D: 43.163 MHz, H: 50.900 kHz, V: 100.00 Hz 116 # D: 52.406 MHz, H: 61.800 kHz, V: 120.00 Hz 137 # D: 26.880 MHz, H: 30.000 kHz, V: 60.24 Hz 158 # D: 29.500 MHz, H: 29.738 kHz, V: 60.00 Hz 179 # D: 32.668 MHz, H: 35.820 kHz, V: 60.00 Hz 200 # D: 40.00 MHz, H: 37.879 kHz, V: 60.32 Hz [all …]
|
/linux/Documentation/devicetree/bindings/sound/ |
H A D | cs35l32.txt | 25 3 = Boost voltage fixed at 5 V. 40 0 = 3.1V 41 1 = 3.2V 42 2 = 3.3V (Default) 43 3 = 3.4V 46 0 = 3.1V 47 1 = 3.2V 48 2 = 3.3V 49 3 = 3.4V (Default) 50 4 = 3.5V [all …]
|
H A D | ti,ts3a227e.yaml | 34 - 0 # 2.1 V 35 - 1 # 2.2 V 36 - 2 # 2.3 V 37 - 3 # 2.4 V 38 - 4 # 2.5 V 39 - 5 # 2.6 V 40 - 6 # 2.7 V 41 - 7 # 2.8 V
|
/linux/drivers/comedi/drivers/tests/ |
H A D | ni_routes_test.c | 29 #define V(x) ((x) | 0x80) macro 118 [x1] = V(x1), [x2] = V(x2), [x3] = V(x3), [x4] = V(x4), \ 119 [x5] = V(x5), [x6] = V(x6), [x7] = V(x7), [x8] = V(x8), \ 120 [x9] = V(x9), 135 [B(NI_RGOUT0)] = {[B(rgout0_src0)] = V(0), 136 [B(rgout0_src1)] = V(1)}, 137 [B(NI_RTSI_BRD(0))] = {[B(brd0_src0)] = V(0), 138 [B(brd0_src1)] = V(1)}, 140 [B(brd1_src1)] = V(1)}, 142 [B(brd2_src1)] = V(1)}, [all …]
|
/linux/Documentation/devicetree/bindings/regulator/ |
H A D | ltc3589.txt | 21 0.3625 V to 0.75 V in 12.5 mV steps. The output voltage thus ranges between 22 0.3625 * (1 + R1/R2) V and 0.75 * (1 + R1/R2) V. Regulators bb-out and ldo1 23 have a fixed 0.8 V reference and thus output 0.8 * (1 + R1/R2) V. The ldo3 24 regulator is fixed to 1.8 V on LTC3589 and to 2.8 V on LTC3589-1,2. The ldo4 25 regulator can output between 1.8 V and 3.3 V on LTC3589 and between 1.2 V 26 and 3.2 V on LTC3589-1,2 in four steps. The ldo1 standby regulator can not
|