Home
last modified time | relevance | path

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

12345678910>>...15

/u-boot/drivers/usb/gadget/
A Dcore.c98 unsigned int port, unsigned int configuration) in usbd_device_configuration_instance() argument
100 if (configuration >= device->configurations) in usbd_device_configuration_instance()
103 return device->configuration_instance_array + configuration; in usbd_device_configuration_instance()
119 …if ((configuration_instance = usbd_device_configuration_instance (device, port, configuration)) ==… in usbd_device_interface_instance()
141 …if ((interface_instance = usbd_device_interface_instance (device, port, configuration, interface))… in usbd_device_alternate_instance()
176 *device, int port, int configuration) in usbd_device_configuration_descriptor() argument
179 if (!(configuration_instance = usbd_device_configuration_instance (device, port, configuration))) { in usbd_device_configuration_descriptor()
197 *device, int port, int configuration, int interface, int alternate) in usbd_device_interface_descriptor() argument
200 …if (!(interface_instance = usbd_device_interface_instance (device, port, configuration, interface)… in usbd_device_interface_descriptor()
221 *device, int port, int configuration, int interface, int alternate, int index) in usbd_device_endpoint_descriptor_index() argument
[all …]
/u-boot/drivers/pinctrl/mscc/
A DKconfig12 Support pin multiplexing and pin configuration control on
21 Support pin multiplexing and pin configuration control on
30 Support pin multiplexing and pin configuration control on
39 Support pin multiplexing and pin configuration control on
48 Support pin multiplexing and pin configuration control on
/u-boot/doc/
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:
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.
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 …]
/u-boot/arch/arm/mach-zynqmp-r5/
A DKconfig17 string "Board configuration name"
20 This option contains information about board configuration name.
22 will be used for board configuration.
/u-boot/doc/device-tree-bindings/pinctrl/
A Dnexell,s5pxx18-pinctrl.txt11 phrase "pin configuration node".
26 Nexell's pin configuration nodes act as a container for an arbitrary number of
27 subnodes. Each of these subnodes represents some desired configuration for a
28 pin, a group, or a list of pins or groups. This configuration can include the
29 mux function to select on those pin(s)/group(s), and various pin configuration
35 - pin-pull = Pull up/down configuration.
36 - pin-strength = Drive strength configuration.
A Dpinctrl-bindings.txt3 Hardware modules that control pin multiplexing or configuration parameters
8 Hardware modules whose signals are affected by pin configuration are
22 configuration used by those states.
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
55 pin configuration nodes.
90 * For an IP block whose binding supports pin configuration,
171 a single pin multiplexing configuration.
183 == Generic pin configuration node content ==
[all …]
/u-boot/board/xilinx/microblaze-generic/
A DKconfig10 string "Board configuration name"
13 This option contains information about board configuration name.
15 will be used for board configuration.
/u-boot/doc/mvebu/
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
/u-boot/drivers/pinctrl/nxp/
A DKconfig17 configuration. This driver is different from the linux one,
31 configuration. This driver is different from the linux one,
45 configuration. This driver is different from the linux one,
58 This feature depends on device tree configuration. This driver
73 This feature depends on device tree configuration. This driver
87 This feature depends on device tree configuration. This driver
100 configuration.
111 This feature depends on device tree configuration. This driver
126 configuration. This driver is different from the linux one,
/u-boot/arch/arm/mach-socfpga/
A Dqts-filter.sh28 * Altera SoCFPGA IOCSR configuration
71 * Altera SoCFPGA PinMux configuration
107 * Altera SoCFPGA Clock and PLL configuration
150 * Altera SoCFPGA SDRAM configuration
/u-boot/lib/efi_loader/
A Defi_hii_config.c47 const efi_string_t configuration, in route_config() argument
50 EFI_ENTRY("%p, \"%ls\", %p", this, configuration, progress); in route_config()
115 const efi_string_t configuration, in route_config_access() argument
118 EFI_ENTRY("%p, \"%ls\", %p", this, configuration, progress); in route_config_access()
/u-boot/drivers/pinctrl/nexell/
A DKconfig6 Support of pin multiplexing and pin configuration for Nexell
15 Support of pin multiplexing and pin configuration for S5P4418
/u-boot/arch/arm/mach-k3/
A DKconfig95 string "File name of SYSFW firmware and configuration blob"
99 Filename of the combined System Firmware and configuration image tree
103 hex "MMC sector to load SYSFW firmware and configuration blob from"
108 configuration image tree blob from, when the MMC is being used
112 hex "MMC partition to load SYSFW firmware and configuration blob from"
116 Partition on the MMC to the combined System Firmware and configuration
125 runtime for loading the combined System Firmware and configuration image
130 hex "SPI offset of SYSFW firmware and configuration blob"
134 Offset of the combined System Firmware and configuration image tree
/u-boot/drivers/pinctrl/mvebu/
A DKconfig7 Support pin multiplexing and pin configuration control on
14 Support pin multiplexing and pin configuration control on
/u-boot/arch/arm/mach-zynqmp/
A DKconfig38 string "Board configuration name"
41 This option contains information about board configuration name.
43 will be used for board configuration.
69 string "PMU firmware configuration object to load at runtime by SPL"
72 Path to a binary PMU firmware configuration object to be linked
75 The ZynqMP Power Management Unit (PMU) needs a configuration
78 the top source tree) of your configuration, which must be a
84 configuration object or you are loading it by any other means.
/u-boot/drivers/pinctrl/broadcom/
A DKconfig6 Support pin multiplexing and pin configuration control on
14 Support pin multiplexing and pin configuration control on
/u-boot/board/gateworks/gw_ventana/
A DKconfig18 Provides access to EEPROM configuration on Gateworks Ventana
23 Provides access to the GSC configuration:
/u-boot/doc/uImage.FIT/
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>[#..]]
136 overlays to apply on the base device tree supplied by the first configuration
144 - boot configuration "cfg-1" from a new uImage located at 200000:
[all …]
/u-boot/
A D.readthedocs.yml2 # Read the Docs configuration file
10 configuration: doc/conf.py
/u-boot/board/freescale/corenet_ds/
A Dpbi.cfg24 #Initialize eSPI controller, default configuration is slow for eSPI to
25 #load data, this configuration comes from u-boot eSPI driver.
/u-boot/board/varisys/cyrus/
A Dpbi.cfg26 #Initialize eSPI controller, default configuration is slow for eSPI to
27 #load data, this configuration comes from u-boot eSPI driver.
/u-boot/board/freescale/t208xqds/
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.
/u-boot/board/freescale/t208xrdb/
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.

Completed in 35 milliseconds

12345678910>>...15