Home
last modified time | relevance | path

Searched refs:configuration (Results 1 – 25 of 254) sorted by relevance

1234567891011

/rk3399_rockchip-uboot/drivers/usb/gadget/
H A Dcore.c134 unsigned int port, unsigned int configuration) 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 …interface_instance (struct usb_device_instance *device, int port, int configuration, int interface) in usbd_device_interface_instance() argument
155 …if ((configuration_instance = usbd_device_configuration_instance (device, port, configuration)) ==… in usbd_device_interface_instance()
173 …alternate_instance (struct usb_device_instance *device, int port, int configuration, int interface… in usbd_device_alternate_instance() argument
177 …if ((interface_instance = usbd_device_interface_instance (device, port, configuration, interface))… in usbd_device_alternate_instance()
212 *device, int port, int configuration) in usbd_device_configuration_descriptor() argument
215 if (!(configuration_instance = usbd_device_configuration_instance (device, port, configuration))) { in usbd_device_configuration_descriptor()
233 *device, int port, int configuration, int interface, int alternate) in usbd_device_interface_descriptor() argument
[all …]
/rk3399_rockchip-uboot/doc/
H A DREADME.plan92 configuration information to the kernel. An environment variable named
5 configuration.
12 uninitialized to permit manual configuration. For example, PC-style
13 configuration could be simulated by issuing a fatload in bootcmd:
H A DREADME.kconfig4 This document describes the configuration infrastructure of U-Boot.
6 The conventional configuration was replaced by Kconfig at v2014.10-rc1 release.
20 Here are some worth-mentioning configuration targets.
26 for the compatibility with the old configuration system:
54 configuration. It is still supported for backward compatibility, so
58 The other configuration targets work as in Linux Kernel.
64 Prior to Kconfig, the C preprocessor based board configuration had been used
70 configuration infrastructures should coexist.
71 The configuration files are generated by both Kconfig and the old preprocessor
72 based configuration as follows:
[all …]
H A DREADME.fsl-trustzone-components5 While most of the configuration related programming of these peripherals
14 - Depends on CONFIG_FSL_TZPC_BP147 configuration flag.
21 - Depends on CONFIG_FSL_TZASC_400 configuration flag.
H A DREADME.mxsimage10 To generate an image, write an image configuration file and run:
12 mkimage -A arm -O u-boot -T mxsimage -n <path to configuration file> \
16 that the example configuration files for producing bootable BootStream with
20 mxsimage.mx23.cfg -- This is an example configuration for i.MX23
21 mxsimage.mx28.cfg -- This is an example configuration for i.MX28
23 Each configuration file uses very simple instruction semantics and a few
27 - Each line of the configuration file contains exactly one instruction.
29 - The configuration file is a concatenation of blocks called "sections" and
96 - An optional "DCD" blocks can be added at the begining of the configuration
99 configuration file.
H A DREADME.distro29 This model assumes that boards will load boot configuration files from a
33 board-specific installer/boot-configuration support in a distro.
42 configuration file generation logic can still be board-agnostic.
49 configuration files from there. A U-Boot board port that enables the features
50 mentioned in this document will search for boot configuration files in the
54 configuration data to indicate which storage device the system should boot
57 Distros simply need to install the boot configuration files (see next
61 conceptually identical to creating a grub2 configuration file on a desktop
66 configuration files. Other bootloaders are recommended to do the same, since
70 U-Boot can also search for boot configuration files from a TFTP server.
[all …]
/rk3399_rockchip-uboot/board/xilinx/microblaze-generic/
H A DKconfig10 string "Board configuration name"
13 This option contains information about board configuration name.
15 will be used for board configuration.
/rk3399_rockchip-uboot/doc/device-tree-bindings/pinctrl/
H A Dpinctrl-bindings.txt3 Hardware modules that control pin multiplexing or configuration parameters
8 Hardware modules whose signals are affected by pin configuration are
14 single static pin configuration, e.g. set up during initialization. Others
22 configuration used by those states.
26 driver loads. This would allow representing a board's static pin configuration
31 they require certain specific named states for dynamic pin configuration.
37 property exists to define the pin configuration. Each state may also be
47 pinctrl-0: List of phandles, each pointing at a pin configuration
48 node. These referenced pin configuration nodes must be child
53 contributing part of the overall configuration. See the next
[all …]
/rk3399_rockchip-uboot/doc/mvebu/
H A Darmada-8k-memory.txt6 This assumes that the SoC includes Dual CP configuration, in case the flavor is using
7 a single CP configuration, then all secondary-CP mappings are invalid.
19 0xF2000000 0xF3FFFFFF CP-0 Internal (configuration) registers
22 0xF4000000 0xF5FFFFFF CP-1 Internal (configuration) registers
/rk3399_rockchip-uboot/arch/arm/mach-socfpga/
H A Dqts-filter.sh27 * Altera SoCFPGA IOCSR configuration
71 * Altera SoCFPGA PinMux configuration
108 * Altera SoCFPGA Clock and PLL configuration
152 * Altera SoCFPGA SDRAM configuration
/rk3399_rockchip-uboot/doc/uImage.FIT/
H A Dcommand_syntax_extensions.txt83 Ad. 8. Image at <addr1> is assumed to contain a default configuration, which
85 - boot method: FDT or non-FDT, depending on whether the default configuration
92 Ad. 10. Boot configuration <conf> from the image at <addr1>.
93 - boot method: FDT or non-FDT, depending on whether the configuration given
129 - new uImage configuration specification
130 <addr>#<configuration unit_name>
132 - new uImage configuration specification with extra configuration components
133 <addr>#<configuration unit_name>[#<extra configuration unit_name>[#..]]
135 The extra configuration currently is supported only for additional device tree
136 overlays to apply on the base device tree supplied by the first configuration
[all …]
H A Doverlay-fdt-boot.txt9 that matches the desired configuration.
22 Without using overlays the configuration would be as follows for every case.
98 multitude of configuration grows the image quite a bit.
197 they are declared in the configuration.
206 Although the configuration in the previous section works is a bit inflexible
207 since it requires all possible configuration options to be laid out before
211 Note the two bar & baz configuration nodes. To boot a reva board with
220 The limitation for a feature selection configuration node is that a single
H A Dmulti.its114 description = "tqm5200 vanilla-2.6.23 configuration";
121 description = "tqm5200s denx-2.6.23 configuration";
128 description = "tqm5200s denx-2.4.25 configuration";
/rk3399_rockchip-uboot/drivers/pinctrl/mvebu/
H A DKconfig7 Support pin multiplexing and pin configuration control on
14 Support pin multiplexing and pin configuration control on
/rk3399_rockchip-uboot/board/gateworks/gw_ventana/
H A DKconfig15 Provides access to EEPROM configuration on Gateworks Ventana
20 Provides access to the GSC configuration:
/rk3399_rockchip-uboot/board/varisys/cyrus/
H A Dpbi.cfg26 #Initialize eSPI controller, default configuration is slow for eSPI to
27 #load data, this configuration comes from u-boot eSPI driver.
/rk3399_rockchip-uboot/board/freescale/corenet_ds/
H A Dpbi.cfg26 #Initialize eSPI controller, default configuration is slow for eSPI to
27 #load data, this configuration comes from u-boot eSPI driver.
/rk3399_rockchip-uboot/drivers/pinctrl/nxp/
H A DKconfig14 configuration. This driver is different from the linux one,
28 configuration. This driver is different from the linux one,
42 configuration. This driver is different from the linux one,
55 This feature depends on device tree configuration. This driver
/rk3399_rockchip-uboot/arch/arm/mach-zynq/
H A DKconfig49 string "Board configuration name"
52 This option contains information about board configuration name.
54 will be used for board configuration.
/rk3399_rockchip-uboot/doc/device-tree-bindings/ram/
H A Dst,stm32-fmc.txt9 - st,sdram-control : parameters for sdram configuration, in this order:
43 /* sdram memory configuration from sdram datasheet */
51 /* sdram memory configuration from sdram datasheet */
/rk3399_rockchip-uboot/board/freescale/t208xqds/
H A Dt208x_pbi.cfg25 #Initialize eSPI controller, default configuration is slow for eSPI to
26 #load data, this configuration comes from u-boot eSPI driver.
/rk3399_rockchip-uboot/board/freescale/t208xrdb/
H A Dt2080_pbi.cfg25 #Initialize eSPI controller, default configuration is slow for eSPI to
26 #load data, this configuration comes from u-boot eSPI driver.
/rk3399_rockchip-uboot/doc/device-tree-bindings/misc/
H A Dintel,irq-router.txt8 - reg : Specifies the interrupt router's PCI configuration space address as
13 "pci": IRQ routing is controlled by PCI configuration registers
16 configuration space, required only if intel,pirq-config = "ibase".
21 in the interrupt router's PCI configuration space, or IBASE.
/rk3399_rockchip-uboot/drivers/pinctrl/
H A DKconfig20 subsystem. This feature depends on device tree configuration because
38 some pin configuration parameters. It would be easier if you only
39 need the generic DT interface for pin muxing and pin configuration.
56 bool "Support pin configuration controllers"
59 This option enables pin configuration through the generic pinctrl
63 bool "Support recursive binding for pin configuration nodes"
68 In the Linux pinctrl binding, the pin configuration nodes need not be
75 configuration; you can save memory footprint when this feature is
117 bool "Support pin configuration controllers in SPL"
124 bool "Support recursive binding for pin configuration nodes in SPL"
[all …]
/rk3399_rockchip-uboot/doc/device-tree-bindings/gpio/
H A Dintel,x86-broadwell-pinctrl.txt5 These pin states use phandles and are referred to but a configuration section
30 The first pin state will be the default, so pins without a configuration will
33 The pin configuration node is also a sub-node of the pinctrl master node, but
36 - config - configuration to use for each pin. Each entry has of 3 cells:
38 - phandle of configuration (above)
42 But missing pins will receive the default configuration.

1234567891011