Home
last modified time | relevance | path

Searched refs:V8 (Results 1 – 25 of 27) sorted by relevance

12

/kernel/linux/linux-5.10/Documentation/hwmon/
Dlochnagar.rst33 in1_input Measured voltage for 1V8 DSP (milliVolts)
34 in1_label "1V8 DSP"
35 curr2_input Measured current for 1V8 DSP (milliAmps)
36 curr2_label "1V8 DSP"
37 power2_average Measured average power for 1V8 DSP (microWatts)
39 power2_label "1V8 DSP"
40 in2_input Measured voltage for 1V8 CDC (milliVolts)
41 in2_label "1V8 CDC"
42 curr3_input Measured current for 1V8 CDC (milliAmps)
43 curr3_label "1V8 CDC"
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dbcm2835-rpi-cm1.dtsi28 regulator-name = "1V8";
Dbcm2837-rpi-cm3.dtsi30 regulator-name = "1V8";
Dgemini-nas4220b.dts110 pins = "V8 GMAC0 RXDV", "T10 GMAC1 RXDV";
Dr8a73a4-ape6evm.dts58 regulator-name = "1V8";
Dgemini-sl93512r.dts222 pins = "U8 GMAC0 RXD0", "V8 GMAC0 RXD1",
Dgemini-sq201.dts185 pins = "V8 GMAC0 RXDV";
Dgemini-dlink-dns-313.dts249 pins = "U8 GMAC0 RXD0", "V8 GMAC0 RXD1",
Dstm32mp15xx-dhcor-avenger96.dtsi8 /* Avenger96 uses DHCOR SoM configured for 1V8 IO operation */
Dam335x-boneblue.dts196 AM33XX_PADCONF(AM335X_PIN_GPMC_AD5, PIN_INPUT_PULLUP, MUX_MODE1) /* (V8) gpmc_ad5.mmc1_dat5 */
Dste-ux500-samsung-skomer.dts287 /* Intended for 1V8 for touchscreen but actually left unused */
Dgemini-dlink-dir-685.dts401 pins = "V8 GMAC0 RXDV", "T10 GMAC1 RXDV",
/kernel/linux/linux-5.10/drivers/regulator/
Dpcap-regulator.c118 VREG_INFO(V8, PCAP_REG_VREG2, 5, 6, 16, 22),
227 VREG(V8), VREG(V9), VREG(V10), VREG(VAUX1), VREG(VAUX2), VREG(VAUX3),
DKconfig1029 This driver supports internal regulators (1V1, 1V8, 3V3) in the
/kernel/linux/linux-5.10/include/linux/mfd/
Dezx-pcap.h120 #define V8 7 macro
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dperf-inject.txt65 if you are monitoring environment using JIT runtimes, such as Java, DART or V8.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/
Dphy-stm32-usbphyc.txt44 - vdda1v8-supply: phandle to the regulator providing 1V8 power to the PHY
/kernel/linux/linux-5.10/arch/arm64/boot/dts/amlogic/
Dmeson-gxl-s905x-libretech-cc-v2.dts155 regulator-name = "VCC 1V8";
Dmeson-gxbb-odroidc2.dts255 gpio-line-names = "UART TX", "UART RX", "VCCK En", "TF 3V3/1V8 En",
/kernel/linux/linux-5.10/arch/arm64/boot/dts/xilinx/
Dzynqmp-zcu100-revC.dts252 interrupts = <76 IRQ_TYPE_EDGE_RISING>; /* MIO76 WLAN_IRQ 1V8 */
/kernel/linux/linux-5.10/Documentation/arm64/
Dsve.rst454 Z8 | : * V8 |
487 This follows from the way these bits are mapped to V8..V15, which are caller-
511 * V8 | |
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mmc/
Dnvidia,tegra20-sdhci.txt59 using pads at 3V3 and 1V8 levels.
/kernel/linux/linux-5.10/drivers/eisa/
Deisa.ids611 ICU0220 "Microfield Graphics V8 Video Controller"
1060 ISAE401 "Microfield V8 Color Graphics Controller"
/kernel/linux/linux-5.10/drivers/video/fbdev/
DKconfig1383 and 340 series as well as XGI V3XT, V5, V8, Z7 graphics chipsets.
1401 as XGI V3XT, V5, V8 and Z7.
/kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/
D0030_linux_drivers_pci_misc_nvmem_of_mtd_mmc.patch13339 - * NEEDS_PAD_CONTROL NVQUIRK is for SoC's having separate 3V3 and 1V8 pads.
13340 - * 3V3/1V8 pad selection happens through pinctrl state selection depending
13410 - * voltage are applicable for SoCs supporting 3V3 and 1V8 pad controls.

12