Home
last modified time | relevance | path

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

123

/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A 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.
H A 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.
H A Drk3288-veyron-speedy.dts87 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
243 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
H A Drk3288-veyron-jaq.dts95 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
251 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
H A Drk3288-veyron-minnie.dts147 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
308 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
H A Drk3288-veyron-mickey.dts275 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
375 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
H A Drk3288-veyron-fievel.dts217 * RECOVERY_SW_L is Chrome OS ABI. Schematics call
388 * AP_FLASH_WP_L is Chrome OS ABI. Schematics call
H A Dbcm2835-rpi-b.dts26 * Taken from Raspberry-Pi-Rev-1.0-Model-AB-Schematics.pdf
H A Dbcm2835-rpi-b-plus.dts33 * Taken from Raspberry-Pi-B-Plus-V1.2-Schematics.pdf
H A Dbcm2835-rpi-b-rev2.dts26 * Taken from Raspberry-Pi-Rev-2.0-Model-AB-Schematics.pdf
H A Dbcm2835-rpi-a.dts25 * Taken from Raspberry-Pi-Rev-1.0-Model-AB-Schematics.pdf
/OK3568_Linux_fs/kernel/Documentation/crypto/
H A 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
/OK3568_Linux_fs/kernel/arch/arm64/boot/dts/amlogic/
H A 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
/OK3568_Linux_fs/buildroot/board/zynq/
H A Dreadme.txt40 - ZC706 information including schematics, reference designs, and manuals are
44 - Zedboard/Microzed information including schematics, reference designs, and
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/iio/adc/
H A Dqcom,spmi-vadc.yaml82 ADC input of the platform as seen in the schematics.
85 the platform schematics name for this channel.
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/display/panel/
H A Dasus,z00t-tm5p5-nt35596.yaml16 as no schematics are released publicly.
/OK3568_Linux_fs/u-boot/arch/arm/dts/
H A Dmeson-gxbb-odroidc2.dts91 * signal name from schematics: TFLASH_VDD_EN
111 * signal name from schematics: TF_3V3N_1V8_EN
/OK3568_Linux_fs/kernel/arch/arm64/boot/dts/qcom/
H A Dsdm845-cheza-r3.dts149 * AP_FLASH_WP_L is crossystem ABI. Rev3 schematics
H A Dsc7180-trogdor-lazor.dtsi136 * AP_FLASH_WP_L is crossystem ABI. Schematics
H A Dsc7180-trogdor-r1.dts135 * AP_FLASH_WP_L is crossystem ABI. Schematics
/OK3568_Linux_fs/u-boot/board/freescale/mx28evk/
H A DREADME59 Look in the schematics for the proper component values.
/OK3568_Linux_fs/u-boot/board/amlogic/odroid-c2/
H A DREADME17 Schematics are available on the manufacturer website.
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/misc/
H A Dhisilicon-hikey-usb.yaml19 Schematics about the hub can be found here:
/OK3568_Linux_fs/kernel/include/linux/mfd/
H A Ddm355evm_msp.h9 * and tweaked to match source and rev D2 schematics by removing CPLD
/OK3568_Linux_fs/kernel/arch/arm64/boot/dts/allwinner/
H A Dsun50i-h5-orangepi-zero-plus2.dts132 * According to schematics CN1 MicroUSB port can be used to take

123