Home
last modified time | relevance | path

Searched refs:structure (Results 1 – 25 of 53) sorted by relevance

123

/rk3399_rockchip-uboot/board/freescale/m52277evb/
H A DREADME32 - include/asm-m68k/crossbar.h CrossBar structure and definition
33 - include/asm-m68k/dspi.h DSPI structure and definition
34 - include/asm-m68k/edma.h eDMA structure and definition
35 - include/asm-m68k/flexbus.h FlexBus structure and definition
36 - include/asm-m68k/fsl_i2c.h I2C structure and definition
37 - include/asm-m68k/global_data.h Global data structure
41 - include/asm-m68k/lcd.h LCD structure and definition
45 - include/asm-m68k/ptrace.h Exception structure
47 - include/asm-m68k/ssi.h SSI structure and definition
49 - include/asm-m68k/timer.h Timer structure and definition
[all …]
/rk3399_rockchip-uboot/doc/
H A DREADME.ubispl17 to load can contain. Used for sizing the scan data structure
22 structure
27 structure
31 scan data structure.
45 2k for the basic data structure
H A DREADME.m54418twr33 - arch/m68k/include/asm/fec.h FEC structure and definition
34 - arch/m68k/include/asm/global_data.h Global data structure
41 - arch/m68k/include/asm/ptrace.h Exception structure
44 - arch/m68k/include/asm/timer.h Timer structure and definition
46 - arch/m68k/include/asm/uart.h Uart structure and definition
47 - arch/m68k/include/asm/u-boot.h u-boot structure
193 bdinfo - print Board Info structure
H A DREADME.commands2 Commands are added to U-Boot by creating a new command structure.
18 The structure created is named with a special prefix and placed by
H A DREADME.unaligned-memory-access.txt79 structure:
87 Let us assume that an instance of the above structure resides in memory
91 structure, i.e. address 0x10002, but that address is not evenly divisible
96 Therefore, for standard structure types you can always rely on the compiler
109 that you could reorder the fields in the structure in order to place fields
111 resident memory size of structure instances. The optimal layout of the
121 byte of padding at the end of the structure. This padding is added in order
125 structure type. This GCC-specific attribute tells the compiler never to
136 structure padding is of importance.
H A DREADME.standalone8 'global_data' structure. The struct members for the jump table are
24 'global_data' structure: r2 on PowerPC, r9 on ARM, k0 on MIPS,
27 structure is passed as 'argv[-1]' pointer.
29 The application can access the 'global_data' structure in the same
H A DREADME.Heterogeneous-SoCs44 Global structure updated for dsp cores and other components
70 3. Changes in MPC85xx_SYS_INFO Global structure
73 DSP cores and other device's components have been added in this structure.
H A DREADME.armada-secureboot24 pertaining to the boot process. Furthermore, a eFuse structure (a
247 eFuse structure's values (this option is just needed for programming the eFuse
248 structure; production boot images may disable it).
274 ### Burn eFuse structure
277 | WARNING: Burning the eFuse structure is a irreversible |
286 the eFuse structure to the values needed for the used KAK digest, as well as
290 will write these values to the eFuse structure.
H A DREADME.JFFS226 structure to find the start of a JFFS2 disk (called partition in the code)
/rk3399_rockchip-uboot/board/freescale/m53017evb/
H A DREADME35 - include/asm-m68k/fec.h FEC structure and definition
36 - include/asm-m68k/fsl_i2c.h I2C structure and definition
37 - include/asm-m68k/global_data.h Global data structure
44 - include/asm-m68k/ptrace.h Exception structure
47 - include/asm-m68k/timer.h Timer structure and definition
49 - include/asm-m68k/uart.h Uart structure and definition
50 - include/asm-m68k/u-boot.h U-Boot structure
/rk3399_rockchip-uboot/board/freescale/m547xevb/
H A DREADME41 - include/asm-m68k/fec.h FEC structure and definition
42 - include/asm-m68k/fsl_i2c.h I2C structure and definition
43 - include/asm-m68k/fsl_mcddmafec.h DMA FEC structure and definition
44 - include/asm-m68k/global_data.h Global data structure
51 - include/asm-m68k/ptrace.h Exception structure
54 - include/asm-m68k/timer.h Timer structure and definition
56 - include/asm-m68k/uart.h Uart structure and definition
57 - include/asm-m68k/u-boot.h U-Boot structure
217 bdinfo - print Board Info structure
/rk3399_rockchip-uboot/doc/driver-model/
H A Dof-plat.txt62 - The platform data is provided to drivers as a C structure. The driver
63 must use the same structure to access the data. Since a driver
171 structure is not available when device tree is used. It would make no sense
172 to use this structure if device tree were available, since the structure has
175 Therefore it is recommended that the of-platdata structure should be used
181 How to structure your driver
256 The of-platdata struct contents is copied from the C structure data to the
H A Dspi-howto.txt11 Before driver model, SPI drivers have their own private structure which
15 driver-specific slave structure can now be port in private data for the
171 7. Set up your platform data structure
208 structure in your driver (called platform data). If you are not using
274 a structure. There is probably a structure in the driver that includes a
291 the slave structure, so we have:
H A Dspi-howto.rst13 Before driver model, SPI drivers have their own private structure which
17 driver-specific slave structure can now be port in private data for the
181 Set up your platform data structure
224 structure in your driver (called platform data). If you are not using
298 a structure. There is probably a structure in the driver that includes a
317 the slave structure, so we have:
H A DREADME.txt312 The U_BOOT_DRIVER macro creates a data structure accessible from C,
332 *** basically a C structure which is passed to drivers to tell them about
355 gives the driver name and a pointer to a structure containing information
373 Where does the platform data come from? It is either held in a structure
618 and uses the of_match table of the U_BOOT_DRIVER() structure to find the
690 using a device tree node or U_BOOT_DEVICE() structure. In either case,
691 the platform data is now stored in the platdata structure. Typically you
693 platform data structure, and U-Boot will automatically allocate and zero
773 device structure itself is not freed at this point. Should the device be
786 Driver model uses a doubly-linked list as the basic data structure. Some
[all …]
H A Dusb-info.txt85 this structure, even the root hub. The controller itself does not
86 have this structure. You can access it for a device 'dev' with
87 dev_get_parent_priv(dev). It matches the old structure except that the
90 descriptor and current configuration descriptor in this structure.
101 driver is actually set up. When probing the bus this structure is
128 in a tree structure, potentially with multiple hubs each with several ports
/rk3399_rockchip-uboot/include/
H A Dcommon.h783 #define check_member(structure, member, offset) _Static_assert( \ argument
784 offsetof(struct structure, member) == offset, \
785 "`struct " #structure "` offset for `" #member "` is not " #offset)
/rk3399_rockchip-uboot/board/freescale/m5373evb/
H A DREADME34 - include/asm-m68k/fec.h FEC structure and definition
35 - include/asm-m68k/fsl_i2c.h I2C structure and definition
36 - include/asm-m68k/global_data.h Global data structure
43 - include/asm-m68k/ptrace.h Exception structure
46 - include/asm-m68k/timer.h Timer structure and definition
48 - include/asm-m68k/uart.h Uart structure and definition
49 - include/asm-m68k/u-boot.h U-Boot structure
197 bdinfo - print Board Info structure
/rk3399_rockchip-uboot/board/freescale/m54455evb/
H A DREADME36 - include/asm-m68k/fec.h FEC structure and definition
37 - include/asm-m68k/fsl_i2c.h I2C structure and definition
38 - include/asm-m68k/global_data.h Global data structure
45 - include/asm-m68k/ptrace.h Exception structure
48 - include/asm-m68k/timer.h Timer structure and definition
50 - include/asm-m68k/uart.h Uart structure and definition
51 - include/asm-m68k/u-boot.h U-Boot structure
278 bdinfo - print Board Info structure
/rk3399_rockchip-uboot/doc/uImage.FIT/
H A Dsource_file_format.txt25 but the support is limited by simple format of the legacy uImage structure.
44 This document defines new uImage structure by providing FDT bindings for new
210 The 'configurations' node has has the following structure:
232 Each configuration has the following structure:
294 Normal kernel FIT image has data embedded within FIT structure. U-Boot image
/rk3399_rockchip-uboot/board/freescale/mpc8536ds/
H A DREADME54 The memory device should contain a specific data structure with control word
58 user can use any method to store the data structure to the memory device, only
/rk3399_rockchip-uboot/doc/device-tree-bindings/clock/
H A Drockchip.txt13 structure a matter of taste, as either all gates can be put into
/rk3399_rockchip-uboot/drivers/clk/at91/
H A DKconfig10 clocks a tree structure, such as master clock, usb device
/rk3399_rockchip-uboot/
H A DKconfig187 This option allows you to boot the new uImage structure,
190 in a single blob. To boot this new uImage structure,
300 bool "Enable fit image structure and data print"
303 Say y here if you want to enable fit image structure and data
374 bool "Enable fit image structure and data print in SPL"
377 Say y here if you want to enable fit image structure and data
/rk3399_rockchip-uboot/lib/lzma/
H A Dlzma.txt60 Source code structure
328 LZMA Decoder uses dictionary buffer and internal state structure.
329 Internal state structure consumes
427 3) Init LzmaDec structure before any new LZMA stream. And call LzmaDec_DecodeToBuf in loop
503 Then you can change some properties in that structure.

123