| /rk3399_rockchip-uboot/drivers/usb/gadget/ |
| H A D | core.c | 133 …usb_configuration_instance *usbd_device_configuration_instance (struct usb_device_instance *device, in usbd_device_configuration_instance() argument
136 if (configuration >= device->configurations) in usbd_device_configuration_instance()
139 return device->configuration_instance_array + configuration; in usbd_device_configuration_instance()
151 struct usb_interface_instance *usbd_device_interface_instance (struct usb_device_instance *device, … in usbd_device_interface_instance() argument
155 …if ((configuration_instance = usbd_device_configuration_instance (device, port, configuration)) ==… in usbd_device_interface_instance()
173 struct usb_alternate_instance *usbd_device_alternate_instance (struct usb_device_instance *device, … in usbd_device_alternate_instance() argument
177 …if ((interface_instance = usbd_device_interface_instance (device, port, configuration, interface))… in usbd_device_alternate_instance()
197 struct usb_device_descriptor *usbd_device_device_descriptor (struct usb_device_instance *device, in… in usbd_device_device_descriptor() argument
199 return (device->device_descriptor); in usbd_device_device_descriptor()
212 *device, int port, int configuration) in usbd_device_configuration_descriptor()
[all …]
|
| H A D | ep0.c | 60 static int ep0_get_status (struct usb_device_instance *device, in ep0_get_status() argument
76 cp[0] = usbd_endpoint_halted (device, index); in ep0_get_status()
96 static int ep0_get_one (struct usb_device_instance *device, struct urb *urb, in ep0_get_one() argument
169 static int ep0_get_descriptor (struct usb_device_instance *device, in ep0_get_descriptor() argument
194 usbd_device_device_descriptor (device, port))) { in ep0_get_descriptor()
217 usbd_device_device_descriptor (device, port))) { in ep0_get_descriptor()
230 usbd_device_configuration_descriptor (device, in ep0_get_descriptor()
276 usbd_device_class_descriptor_index (device, in ep0_get_descriptor()
306 (device, port, 0, bNumInterface, in ep0_get_descriptor()
331 device->qualifier_descriptor; in ep0_get_descriptor()
[all …]
|
| H A D | Kconfig | 33 a USB peripheral device. Configure one hardware driver for your
34 peripheral/device side bus controller, and a "gadget driver" for
40 string "Vendor name of the USB device"
44 Vendor name of the USB device emulated, reported to the host device.
45 This is usually either the manufacturer of the device or the SoC.
48 hex "Vendor ID of the USB device"
52 Vendor ID of the USB device emulated, reported to the host device.
57 hex "Product ID of the USB device"
61 Product ID of the USB device emulated, reported to the host device.
73 Enable the Broadcom UDC OTG physical device interface.
[all …]
|
| /rk3399_rockchip-uboot/drivers/block/ |
| H A D | ide.c | 208 unsigned char atapi_issue(int device, unsigned char *ccb, int ccblen, in atapi_issue() argument
218 ide_outb(device, ATA_DEV_HD, ATA_LBA | ATA_DEVICE(device)); in atapi_issue()
219 c = atapi_wait_mask(device, ATAPI_TIME_OUT, mask, res); in atapi_issue()
221 printf("ATAPI_ISSUE: device %d not ready status %X\n", device, in atapi_issue()
227 ide_outb(device, ATA_ERROR_REG, 0); /* no DMA, no overlaped */ in atapi_issue()
228 ide_outb(device, ATA_SECT_CNT, 0); in atapi_issue()
229 ide_outb(device, ATA_SECT_NUM, 0); in atapi_issue()
230 ide_outb(device, ATA_CYL_LOW, (unsigned char) (buflen & 0xFF)); in atapi_issue()
231 ide_outb(device, ATA_CYL_HIGH, in atapi_issue()
233 ide_outb(device, ATA_DEV_HD, ATA_LBA | ATA_DEVICE(device)); in atapi_issue()
[all …]
|
| /rk3399_rockchip-uboot/arch/arm/mach-uniphier/boot-device/ |
| H A D | Makefile | 5 obj-y += boot-device.o
7 obj-$(CONFIG_ARCH_UNIPHIER_LD4) += boot-device-ld4.o
8 obj-$(CONFIG_ARCH_UNIPHIER_PRO4) += boot-device-ld4.o
9 obj-$(CONFIG_ARCH_UNIPHIER_SLD8) += boot-device-ld4.o
10 obj-$(CONFIG_ARCH_UNIPHIER_PRO5) += boot-device-pro5.o
11 obj-$(CONFIG_ARCH_UNIPHIER_PXS2) += boot-device-pxs2.o
12 obj-$(CONFIG_ARCH_UNIPHIER_LD6B) += boot-device-pxs2.o
13 obj-$(CONFIG_ARCH_UNIPHIER_LD11) += boot-device-ld11.o
14 obj-$(CONFIG_ARCH_UNIPHIER_LD20) += boot-device-ld11.o
15 obj-$(CONFIG_ARCH_UNIPHIER_PXS3) += boot-device-pxs3.o
|
| /rk3399_rockchip-uboot/arch/sandbox/cpu/ |
| H A D | eth-raw-os.c | 32 struct sockaddr_ll *device; in _raw_packet_start() local
38 priv->device = malloc(sizeof(struct sockaddr_ll)); in _raw_packet_start()
39 if (priv->device == NULL) in _raw_packet_start()
41 device = priv->device; in _raw_packet_start()
42 memset(device, 0, sizeof(struct sockaddr_ll)); in _raw_packet_start()
43 device->sll_ifindex = if_nametoindex(ifname); in _raw_packet_start()
44 device->sll_family = AF_PACKET; in _raw_packet_start()
45 memcpy(device->sll_addr, ethmac, 6); in _raw_packet_start()
46 device->sll_halen = htons(6); in _raw_packet_start()
69 mr.mr_ifindex = device->sll_ifindex; in _raw_packet_start()
[all …]
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 1 Pre-relocation device tree manipulation
17 "extensions" of each other, where one device only differs from another in the
23 addition of the daughter board to the device realizes the "extension" of
24 functionality to the device described previously.
27 variations of the device. This means that the software somehow needs to cope
32 device tree overlay mechanism: There exists one "base" device tree, which
34 device. At the start of the kernel, the presence and type of the daughter
35 boards is then detected, and the corresponding device tree overlays are applied
42 In the U-Boot boot loader, support for device tree overlays has recently been
43 integrated, and is used on some boards to alter the device tree that is later
[all …]
|
| H A D | pci-info.txt | 9 Bus number 0 will need to be requested first, and the alias in the device
10 tree file will point to the correct device:
23 If there is no alias the devices will be numbered sequentially in the device
31 After probing a bus, the available devices will appear in the device tree
37 PCI devices can appear in the flattened device tree. If they do this serves to
38 specify the driver to use for the device. In this case they will be bound at
39 first. Each PCI device node must have a compatible string list as well as a
91 a PCI UART device "uart@a,1" is described. This exactly reflects the hardware
93 to a downstream device Topcliff chipset. Inside Topcliff chipset, it has a
95 device are on the PCI bus. Like other devices in the device tree, if we want
[all …]
|
| H A D | usb-info.txt | 51 necessary settings from the device tree.
59 exists when the device is probed (not when it is bound) and is removed when
63 in USB device mode (OTG operation). It can be omitted if that is not
67 call ehci_register() to register itself as an EHCI device. It should call
68 ehci_deregister() in the remove() method. Registering a new EHCI device
84 This holds information about a device on the bus. All devices have
86 have this structure. You can access it for a device 'dev' with
89 handles that). Once the device is set up, you can find the device
98 This holds platform data for a device. You can access it for a
99 device 'dev' with dev_get_parent_platdata(dev). It holds the device
[all …]
|
| H A D | README.txt | 240 This function looks up a device for the demo uclass. Given a device
241 number we can find the device because all devices have registered with
244 The device is automatically activated ready for use by uclass_get_device().
246 Now that we have the device we can do things like:
252 this particular device may use one or other of them.
315 The methods a device can provide are documented in the device.h header.
318 bind - make the driver model aware of a device (bind it to its driver)
319 unbind - make the driver model forget the device
320 ofdata_to_platdata - convert device tree data to platdata - see later
321 probe - make a device ready for use
[all …]
|
| H A D | of-plat.txt | 12 The overhead of adding device tree access to U-Boot is fairly modest,
14 that in most cases it is best to use device tree for configuration.
19 case the overhead of device tree access may be too great.
23 bypasses the use of device tree completely, effectively creating a parallel
27 device tree contents into C code which can be compiled into the SPL binary.
48 in the device tree file.
51 the naming in the device tree, which may result in C identifiers that
56 the code less robust in the face of device-tree changes. It also
64 normally also supports device tree it must use #ifdef to separate
76 A new tool called 'dtoc' converts a device tree file either into a set of
[all …]
|
| H A D | remoteproc-framework.txt | 12 3. Describing the device using platform data
13 4. Describing the device using device tree
75 state transitions of the device as necessary.
104 This allows for the device to be probed as part of the "init" command
108 appropriate for the device it maintains. It must, at the very least
109 provide a load and start function. We assume here that the device
113 3. Describing the device using platform data
121 Considering that many platforms are yet to move to device-tree model,
122 a simplified definition of a device is as follows:
141 3. Describing the device using device tree
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.power-framework | 28 The same device - e.g. MAX8997 uses two different I2C busses and addresses.
35 The "flat" hierarchy for power devices works well when each device performs only
38 The problem emerges when we have a device (battery) which conceptually shall be
43 Up till now u-boot doesn't support device model, so a simple one had to be
64 Everything is a power device described by struct pmic. Even battery is
65 considered as a valid power device. This helps for better management of those
85 prompt to change values of device's register (enable/disable LDO, BUCK).
94 - FG device (struct power_fg):
99 - Charger device (struct power_chrq):
107 - Battery device (struct power_battery):
[all …]
|
| H A D | README.marvell | 11 # sudo apt-get install device-tree-compiler
31 5. Configure the device-tree and build the U-Boot image:
33 Compile u-boot and set the required device-tree using:
40 By default, u-boot is compiled with armada-8040-db device-tree.
41 Using A80x0 device-tree on A70x0 might break the device.
42 In order to prevent this, the required device-tree MUST be set during compilation.
43 All device-tree files are located in ./arch/arm/dts/ folder.
|
| H A D | I2C_Edge_Conditions | 10 3) The I2C writes the device address.
15 2) The I2C controller writes the device address.
20 2) device address
22 4) device address "EEPROM interprets this as offset"
23 5) Offset in device, "EEPROM interprets this as data to write"
25 The device will interpret this sequence as a WRITE command and
27 as data to be written in location "device address".
34 controller and device available. For boards where a I2C bus reset
|
| /rk3399_rockchip-uboot/arch/powerpc/cpu/mpc85xx/ |
| H A D | fsl_corenet_serdes.c | 131 int is_serdes_configured(enum srds_prtcl device) in is_serdes_configured() argument
142 return (1 << device) & serdes_prtcl_map; in is_serdes_configured()
145 static int __serdes_get_first_lane(uint32_t prtcl, enum srds_prtcl device) in __serdes_get_first_lane() argument
150 if (serdes_get_prtcl(prtcl, i) == device) in __serdes_get_first_lane()
164 int serdes_get_first_lane(enum srds_prtcl device) in serdes_get_first_lane() argument
177 return __serdes_get_first_lane(prtcl, device); in serdes_get_first_lane()
188 static int serdes_get_bank_by_device(uint32_t prtcl, enum srds_prtcl device) in serdes_get_bank_by_device() argument
192 lane = __serdes_get_first_lane(prtcl, device); in serdes_get_bank_by_device()
199 static uint32_t __serdes_get_lane_count(uint32_t prtcl, enum srds_prtcl device, in __serdes_get_lane_count() argument
205 if (serdes_get_prtcl(prtcl, lane) != device) in __serdes_get_lane_count()
[all …]
|
| /rk3399_rockchip-uboot/drivers/ata/ |
| H A D | sata_sil3114.c | 437 static u8 do_one_read (int device, ulong block, u8 blkcnt, u16 * buff, in do_one_read() argument
445 if (!(sata_chk_status (&port[device].ioaddr, 0) & ATA_DRDY)) { in do_one_read()
446 printf ("Device ata%d not ready\n", device); in do_one_read()
454 writeb (0, port[device].ioaddr.nsect_addr); in do_one_read()
455 writeb ((blknr >> 24) & 0xFF, port[device].ioaddr.lbal_addr); in do_one_read()
456 writeb ((blknr >> 32) & 0xFF, port[device].ioaddr.lbam_addr); in do_one_read()
457 writeb ((blknr >> 40) & 0xFF, port[device].ioaddr.lbah_addr); in do_one_read()
460 writeb (blkcnt, port[device].ioaddr.nsect_addr); in do_one_read()
461 writeb (((blknr) >> 0) & 0xFF, port[device].ioaddr.lbal_addr); in do_one_read()
462 writeb ((blknr >> 8) & 0xFF, port[device].ioaddr.lbam_addr); in do_one_read()
[all …]
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/pmic/ |
| H A D | max77686.txt | 3 This device uses two drivers:
4 - drivers/power/pmic/max77686.c (for parent device)
10 - doc/device-tree-bindings/regulator/max77686.txt
16 With those two properties, the pmic device can be used for read/write only.
20 - voltage-regulators: subnode list of each device's regulator
|
| H A D | sandbox.txt | 3 This device uses two drivers:
4 - drivers/power/pmic/sandbox.c (for parent device)
10 - doc/device-tree-bindings/regulator/sandbox.txt
19 With the above properties, the pmic device can be used for read/write only.
23 - ldo/buck subnodes of each device's regulator (see regulator binding info)
|
| /rk3399_rockchip-uboot/drivers/demo/ |
| H A D | Kconfig | 13 bool "Enable simple demo device for driver model"
16 This device allows you to play around with driver model. It prints
18 this device. It can be used to help understand how driver model
22 bool "Enable shape demo device for driver model"
25 This device allows you to play around with driver model. It prints
27 this device. It can be used to help understand how driver model
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/ |
| H A D | chosen.txt | 3 The chosen node does not represent a real device, but serves as a place
4 for passing data like which serial device to used to print the logs etc
9 Device trees may specify the device to be used for boot console output
29 since device tree has all the timer nodes. Specify which timer to be
50 device may be probed by reading the image and verifying an image
53 If the SPL is configured through the device-tree, the boot-order can
55 Each list element of the property should specify a device to be probed
60 boot-order to direct U-Boot to insert the device the SPL was booted
62 it is not supported on any given SoC/board or if the boot-device is
|
| /rk3399_rockchip-uboot/arch/arm/cpu/armv7/ls102xa/ |
| H A D | fsl_ls1_serdes.c | 21 int is_serdes_configured(enum srds_prtcl device) in is_serdes_configured() argument
29 ret |= (1ULL << device) & serdes1_prtcl_map; in is_serdes_configured()
35 ret |= (1ULL << device) & serdes2_prtcl_map; in is_serdes_configured()
41 int serdes_get_first_lane(u32 sd, enum srds_prtcl device) in serdes_get_first_lane() argument
69 if (serdes_get_prtcl(sd, cfg, i) == device) in serdes_get_first_lane()
|
| /rk3399_rockchip-uboot/dts/ |
| H A D | Kconfig | 30 via a flattened device tree.
44 U-Boot's device tree (e.g. to delete device from it). This option
54 Some boards use device tree in U-Boot but only have 4KB of SRAM
55 which is not enough to support device tree. Enable this option to
72 Some boards use device tree in U-Boot but only have 4KB of SRAM
73 which is not enough to support device tree. Enable this option to
80 Normally U-Boot uses a flat device tree which saves space and
83 can invalidate driver-model device tree offsets. This option
95 If this option is enabled, the device tree will be built and
101 If this option is enabled, the device tree will be picked up and
[all …]
|
| /rk3399_rockchip-uboot/include/usb/ |
| H A D | udc.h | 41 void udc_setup_ep(struct usb_device_instance *device, unsigned int ep,
45 void udc_enable(struct usb_device_instance *device);
47 void udc_startup_events(struct usb_device_instance *device);
|
| /rk3399_rockchip-uboot/board/qualcomm/dragonboard410c/ |
| H A D | readme.txt | 17 6) Generate qualcomm device tree table with dtbTool [1]
39 - USB in EHCI mode (usb starts does switch device->host, usb stop does the opposite)
46 [1] To boot any kernel image, Little Kernel requires valid device tree for the
47 platform it runs on. dtbTool creates device tree table that Little Kernel scans.
48 Later on proper device tree is passed to next boot stage.
49 Full device tree is not required to boot u-boot. Enough would be:
69 existing Qualcomm device trees.
|