Home
last modified time | relevance | path

Searched refs:side (Results 1 – 25 of 31) sorted by relevance

12

/u-boot/board/BuS/eb_cpu5282/
A Deb_cpu5282.c232 ulong side; in do_brightness() local
237 side = simple_strtoul(argv[1], NULL, 10); in do_brightness()
239 if ((side >= 0) && (side <= 3) && in do_brightness()
241 vcxk_setbrightness(side, bright); in do_brightness()
/u-boot/doc/
A DREADME.i2c5 The implementation on the master side in software is quite complex.
16 reboots by either side without difficulty.
32 sure that the other side doesn't want it also. A detailed explanation is best
38 2. Waits a little bit for the other side to notice (slew time)
46 7. Panic. The other side is hung with the CLAIM line set.
60 wait for access to the bus assuming that the other side isn't using it.
A DREADME.Heterogeneous-SoCs1 DSP side awareness for Freescale heterogeneous multicore chips based on
9 Code for DSP side awareness provides such functionality for Freescale
A DREADME.usb224 eth2addr). There is similar support on the USB network side, using the
/u-boot/drivers/video/
A Dbus_vcxk.c99 void vcxk_setbrightness(unsigned int side, short brightness);
272 void vcxk_setbrightness(unsigned int side, short brightness) in vcxk_setbrightness() argument
275 if ((side == 0) || (side & 0x1)) in vcxk_setbrightness()
277 if ((side == 0) || (side & 0x2)) in vcxk_setbrightness()
/u-boot/include/
A Dbus_vcxk.h16 extern void vcxk_setbrightness(unsigned int side, short brightness);
/u-boot/api/
A DREADME23 leaving as much processing as possible on the consumer application side,
47 - entry point at the consumer side, allows to make syscall, mandatory
/u-boot/drivers/usb/ulpi/
A DKconfig7 Select ULPI viewport (SoC-side interface to ULPI) implementation
/u-boot/drivers/usb/gadget/
A DKconfig6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
28 familiar host side controllers have names like "EHCI", "OHCI",
34 peripheral/device side bus controller, and a "gadget driver" for
231 Ethernet MAC address of the device-side (ie. local board's) MAC
238 Ethernet MAC address of the host-side (ie. remote device's) MAC
/u-boot/doc/device-tree-bindings/spi/
A Dsoft-spi.txt4 SPI bus. No SPI host is required for this to work. The down-side is that the
/u-boot/doc/board/actions/
A Dcubieboard7.rst33 The user needs to run the following command on the PC side to check if the ADFU
35 the PC side has been correctly detected ADFU device, the development board
/u-boot/board/wandboard/
A DREADME34 - Insert the SD card into the slot located in the bottom of the board (same side
/u-boot/arch/arm/dts/
A Darmada-xp-gp.dts153 /* Front-side USB slot */
158 /* Back-side USB slot */
A Darmada-xp-maxbcm.dts221 /* Front-side USB slot */
226 /* Back-side USB slot */
A Dfsl-imx8dx.dtsi58 * Shouldn't be used at A core and Linux side.
/u-boot/drivers/usb/
A DKconfig26 If your system has a device-side USB port, used in the peripheral
27 side of the USB protocol, see the "USB Gadget" framework instead.
/u-boot/doc/imx/misc/
A Dsdp.txt24 The host side utilities are typically capable to interpret the i.MX
27 specific legacy image format (see mkimage(1)). Also the U-Boot side
/u-boot/arch/x86/cpu/quark/
A Dsmc.c2090 uint8_t side; /* LEFT/RIGHT side indicator (0=L, 1=R) */ in wr_train() local
2160 for (side = L; side <= R; side++) { in wr_train()
2161 mrc_post_code(0x08, 0x10 + side); in wr_train()
2172 set_wdq(ch, rk, bl, delay[side][ch][rk][bl]); in wr_train()
2201 if (side == L) in wr_train()
2213 delay[side][ch][rk][bl]); in wr_train()
2220 mrc_post_code(0xee, 0x80 + side); in wr_train()
/u-boot/doc/android/
A Dfastboot.rst190 On the client side you can fetch the bootloader version for instance::
216 and on the U-Boot side you should see::
/u-boot/doc/usage/
A Dnetconsole.rst30 On the host side, please use this script to access the console
A Ddfu.rst275 For example dfu-util is a host side implementation of the DFU 1.1
297 On the Host side:
/u-boot/doc/board/google/
A Dchromebook_coral.rst214 - left-side USB
/u-boot/doc/uImage.FIT/
A Dsignature.txt49 openssl on the host side (e.g. mkimage), it is not desirable for U-Boot.
50 For the run-time verification side, it is important to keep code and data
/u-boot/doc/uefi/
A Du-boot_on_efi.rst204 - Add more drivers to the application side (e.g. video, block devices, USB,
/u-boot/drivers/mmc/
A DKconfig783 an on-board level shifter that is 1.8v on SoC side and 3.3v on SD card
784 side. For boards without hardware workaround, this option could be

Completed in 25 milliseconds

12