Home
last modified time | relevance | path

Searched full:schematics (Results 1 – 25 of 62) sorted by relevance

123

/Linux-v5.10/arch/arm/boot/dts/
Dmeson8b-ec100.dts97 /* X2 in the schematics */
118 * signal name from the schematics: USB_PWR_EN
127 * in the schematics
137 * signal name from the schematics: 3V3_5V_EN
182 * VDDIO_AO3.3V in the schematics.
197 * DDR3_1.5V in the schematics.
232 * in a part of the schematics.
Dmeson8b-odroidc1.dts55 * signal name from schematics: TFLASH_VDD_EN
79 * signal name from schematics: TF_3V3N_1V8_EN
94 /* X3 in the schematics */
105 * VDD1V8 according to the schematics.
120 * also VDD3V3 and VDDIO_AO3V3 according to the schematics.
152 * also DDR3_1V5 according to the schematics.
Drk3288-veyron-speedy.dts87 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
243 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
Drk3288-veyron-jaq.dts95 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
251 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
Drk3288-veyron-minnie.dts147 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
308 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
Dbcm2835-rpi-b.dts26 * Taken from Raspberry-Pi-Rev-1.0-Model-AB-Schematics.pdf
Drk3288-veyron-fievel.dts217 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
388 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
Drk3288-veyron-mickey.dts275 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
375 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
Dbcm2835-rpi-a.dts25 * Taken from Raspberry-Pi-Rev-1.0-Model-AB-Schematics.pdf
Dbcm2835-rpi-b-plus.dts33 * Taken from Raspberry-Pi-B-Plus-V1.2-Schematics.pdf
Dbcm2835-rpi-b-rev2.dts26 * Taken from Raspberry-Pi-Rev-2.0-Model-AB-Schematics.pdf
/Linux-v5.10/Documentation/crypto/
Ddevel-algos.rst71 Here are schematics of how these functions are called when operated from
73 before or after any of these schematics happen, but must not happen
171 Here are schematics of how these functions are called when operated from
173 before or after any of these schematics happen, but must not happen
/Linux-v5.10/arch/arm64/boot/dts/amlogic/
Dmeson-gxbb-odroidc2.dts40 * signal name from schematics: PWREN
45 * signal name from schematics: USB_POWER
86 * signal name from schematics: TFLASH_VDD_EN
102 * signal name from schematics: TF_3V3N_1V8_EN
Dmeson-gxl-s905x-hwacom-amazetv.dts40 /* Based on P200 schematics, signal CARD_1.8V/3.3V_CTR */
/Linux-v5.10/Documentation/devicetree/bindings/display/panel/
Dasus,z00t-tm5p5-nt35596.yaml16 as no schematics are released publicly.
/Linux-v5.10/arch/arm64/boot/dts/qcom/
Dsdm845-cheza-r3.dts149 * AP_FLASH_WP_L is crossystem ABI. Rev3 schematics
Dsc7180-trogdor-lazor.dtsi136 * AP_FLASH_WP_L is crossystem ABI. Schematics
Dsc7180-trogdor-r1.dts135 * AP_FLASH_WP_L is crossystem ABI. Schematics
/Linux-v5.10/Documentation/devicetree/bindings/iio/adc/
Dqcom,spmi-vadc.yaml82 ADC input of the platform as seen in the schematics.
85 the platform schematics name for this channel.
/Linux-v5.10/arch/arm64/boot/dts/allwinner/
Dsun50i-h5-orangepi-zero-plus2.dts132 * According to schematics CN1 MicroUSB port can be used to take
/Linux-v5.10/Documentation/devicetree/bindings/sound/
Daxentia,tse850-pcm5142.txt13 The schematics explaining the gpios are as follows:
/Linux-v5.10/include/linux/mfd/
Ddm355evm_msp.h9 * and tweaked to match source and rev D2 schematics by removing CPLD
/Linux-v5.10/include/dt-bindings/pinctrl/
Domap.h82 * the schematics before using these.
/Linux-v5.10/arch/arm64/boot/dts/rockchip/
Drk3399-ficus.dts6 * Schematics available at https://dl.vamrs.com/products/ficus/docs/hw
/Linux-v5.10/arch/arm64/boot/dts/mediatek/
Dmt8183-kukui-krane.dtsi249 * AP_FLASH_WP_L is crossystem ABI. Rev1 schematics

123