- 30 10月, 2015 12 次提交
-
-
由 Hou Zhiqiang 提交于
The FMan IM driver is developed for 32-bit platfroms and isn't friendly to 64-bit platforms, so do the minimal refactor: 1. Refine the MURAM management and access. 2. Correct the initialization and operations for QDs and BDs. Signed-off-by: NHou Zhiqiang <B48286@freescale.com> Signed-off-by: NGong Qianyu <Qianyu.Gong@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Hou Zhiqiang 提交于
The Frame Manager(FMan) is a big-endian peripheral, so the registers, internal MURAM and BDs, which are allocated in main memory and used to communication between core and FMan, should be accessed in big-endian. The big-endian platforms can access them directly as the code implemented so far, while for the little-endian platforms it need to swap the byte-order. Signed-off-by: NHou Zhiqiang <B48286@freescale.com> Signed-off-by: NShaohui Xie <Shaohui.Xie@freescale.com> Signed-off-by: NMingkai Hu <Mingkai.Hu@freescale.com> Signed-off-by: NGong Qianyu <Qianyu.Gong@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Mingkai Hu 提交于
Config Security Level Register is different between different SoCs, so put the CSL register definition into the arch specific directory. Signed-off-by: NMingkai Hu <Mingkai.Hu@freescale.com> Signed-off-by: NHou Zhiqiang <B48286@freescale.com> Signed-off-by: NGong Qianyu <Qianyu.Gong@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Gong Qianyu 提交于
For most PPC platforms, they will call the first get_clocks() in init_sequence_f[] as they define CONFIG_PPC. CONFIG_SYS_FSL_CLK is then defined to call the second get_clocks(), which should be redundant for PPC. Signed-off-by: NGong Qianyu <Qianyu.Gong@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
Enable snooping for CAAM read & write transactions by programming the SCFG snoop configuration register: SCFG_SNPCNFGCR[SECRDSNP] SCFG_SNPCNFGCR[SECWRSNP] Signed-off-by: NHoria Geantă <horia.geanta@freescale.com> Reviewed-by: NZhengxiong Jin <Jason.Jin@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Prabhakar Kushwaha 提交于
Add support of setting RANDOM MAC address if env variable not available. Signed-off-by: NPrabhakar Kushwaha <prabhakar@freescale.com> Reviewed-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Prabhakar Kushwaha 提交于
Currently ldpaa ethernet driver rely on DPL file to statically configure mac address for the DPNIs. It is not a correct approach. Add support setting MAC address from env variable or Random MAC address. Signed-off-by: NPrabhakar Kushwaha <prabhakar@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Shaohui Xie 提交于
To support on board Aquantia's PHY AQR405. Signed-off-by: NShaohui Xie <Shaohui.Xie@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Aneesh Bansal 提交于
The SEC driver code has been cleaned up to work for 64 bit physical addresses and systems where endianess of SEC block is different from the Core. Changes: 1. Descriptor created on Core is modified as per SEC block endianness before the job is submitted. 2. The read/write of physical addresses to Job Rings will be depend on endianness of SEC block as 32 bit low and high part of the 64 bit address will vary. 3. The 32 bit low and high part of the 64 bit address in descriptor will vary depending on endianness of SEC. Signed-off-by: NAneesh Bansal <aneesh.bansal@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Aneesh Bansal 提交于
Data types and I/O functions have been defined for 64 bit physical addresses in arm. Signed-off-by: NAneesh Bansal <aneesh.bansal@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Aneesh Bansal 提交于
For the Chain of Trust, the esbc_validate command supports 32 bit fields for location of the image. In the header structure definition, these were declared as pointers which made them 64 bit on a 64 bit core. Signed-off-by: NAneesh Bansal <aneesh.bansal@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Alison Wang 提交于
As QSPI/DSPI and IFC are pin multiplexed, IFC is disabled in SD boot for QSPI. This patch will add fdt support for this rule. Signed-off-by: NAlison Wang <alison.wang@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
- 27 10月, 2015 5 次提交
-
-
由 Alison Wang 提交于
As QSPI and IFC are pin-multiplexed on LS1021A, only IFC is supported in SD boot now. For the customer's demand, QSPI needs to be supported in SD boot too. This patch adds QSPI or IFC support in SD boot according to the corresponding defconfig. For detail, ls1021atwr_sdcard_ifc_defconfig is used to support IFC in SD boot and ls1021atwr_sdcard_qspi_defconfig is used to support QSPI in SD boot. Signed-off-by: NAlison Wang <alison.wang@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Zhao Qiang 提交于
The address of uboot changed, so change qe ucode Signed-off-by: NZhao Qiang <B45475@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Alison Wang 提交于
Pointer 'reg' returned from call to function 'fdt_getprop' may be NULL, will be passed to function and may be dereferenced there by passing argument 1 to function 'of_read_number'. So check pointer 'reg' first. Signed-off-by: NAlison Wang <alison.wang@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Scott Wood 提交于
Currently, using fdt_fixup_stdout() on a device tree that is missing the relevant alias results in this: WARNING: could not set linux,stdout-path FDT_ERR_NOTFOUND. ERROR: /chosen node create failed - must RESET the board to recover. FDT creation failed! hanging...### ERROR ### Please RESET the board ### There is no reason for this to be a fatal error rather than a warning, and removing this allows for a smooth transition on a platform where the device tree currently lacks the correct aliases but will have them in the future. Signed-off-by: NScott Wood <scottwood@freescale.com> Cc: Kumar Gala <galak@kernel.crashing.org> Cc: Simon Glass <sjg@chromium.org> Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
由 Scott Wood 提交于
This will allow OF-based earlycon to be used once the appropriate aliases are added to the device tree and kernel support is fixed. Signed-off-by: NScott Wood <scottwood@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
- 25 10月, 2015 22 次提交
-
-
由 Gong Qianyu 提交于
get_clocks() should not be limited by ESDHC. Signed-off-by: NGong Qianyu <Qianyu.Gong@freescale.com>
-
由 Masahiro Yamada 提交于
We have finished Generic Board conversion for ARM and PowerPC, i.e. all the boards have been converted except OpenRISC, SuperH, SPARC, which have not supported Generic Board framework yet. Select SYS_GENERIC_BOARD in arch/Kconfig and delete all the macro defines in include/configs/*.h. Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Simon Glass 提交于
This reverts commit 321f86e1. The original bug has been fixed. Signed-off-by: NSimon Glass <sjg@chromium.org> Tested-on: Zedboard and ZC706 board Tested-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Tested-on: zc702 Tested-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Simon Glass 提交于
We should not init the console this early since it precludes using driver model for the UART, since it is not set up at the start of board_init_f(). See the README for more information. The debug UART does not have this restriction. If we want to do early init with the console on it can be done in spl_board_init(). Move the preloader_console_init() call from board_init_f() to board_init_r(). Signed-off-by: NSimon Glass <sjg@chromium.org> Tested-by: NMasahiro Yamada <yamada.masahiro@socionext.com> Tested-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Simon Glass 提交于
This C function should be used to do the early memory layout and init. This is beyond my powers, so just add a TODO for the maintainer. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NMichal Simek <michal.simek@xilinx.com>
-
由 Simon Glass 提交于
There is quite a bit of assembler code that can be removed if we use the generic global_data setup. Less arch-specific code makes it easier to add new features and maintain the start-up code. Drop the unneeded code and adjust the hooks in board_f.c to cope. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
There is quite a bit of assembler code that can be removed if we use the generic global_data setup. Less arch-specific code makes it easier to add new features and maintain the start-up code. Drop the unneeded code and adjust the hooks in board_f.c to cope. Tested on LS2085ARDB and LS2085AQDS (armv8 SoC). Tested-by: NYork Sun <yorksun@freescale.com> Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Change the #ifdef so that the early malloc() area is not set up in SPL if CONFIG_SYS_SPL_MALLOC_START is defined. In that case it would never actually be used, and just chews up stack space. Signed-off-by: NSimon Glass <sjg@chromium.org> Tested-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Simon Glass 提交于
Unfortunately memset() is not always available, so provide a substitute when needed. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This function will be used by both SPL and U-Boot proper. So move it into a common place. Also change the #ifdef so that the early malloc() area is not set up in SPL if CONFIG_SYS_SPL_MALLOC_START is defined. In that case it would never actually be used, and just chews up stack space. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Stephen Warren 提交于
In the following snippet: if [ ! -x `which $prereq` ]; then When $prereq does not exist, `which $prereq` evaluates to the empty string, which results in *no* argument being passed to the -x operator, which then evaluates to true, which is the equivalent of the prereq having been found. In order for this to fail as expected, we must pass an empty argument, which then causes -x to fail. Do this by wrapping the `` in quotes so there's always an argument to -x, even if the value of the argument is zero-length. Signed-off-by: NStephen Warren <swarren@wwwdotorg.org> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Stephen Warren 提交于
In my patch series to replace fs/fat with "ff.c", I enhanced ff.c to optimize file reading, so that reads of contiguous clusters are submitted to the IO device as a single read. This test attempts to torture-test edge-cases of that enhancement. BTW, the only way I found to validate that this script actually does create non-contiguous files was to manually inspect the FAT bitmap in a hex dump of the FAT image. hdparm --fibmap doesn't work on loop-mounted filesystems. filefrag -v -e seems to lie about files being contiguous when they aren't. Signed-off-by: NStephen Warren <swarren@wwwdotorg.org> Reviewed-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Stephen Warren 提交于
itest accesses memory, and hence must map/unmap it. Without doing so, it accesses invalid addresses and crashes. Signed-off-by: NStephen Warren <swarren@wwwdotorg.org> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Roy Spliet 提交于
Under the assumptions of having a UBI volume called boot, containing a ubifs filesystem. Signed-off-by: NRoy Spliet <rspliet@eclipso.eu> Signed-off-by: NHans de Goede <hdegoede@redhat.com> Acked-by: NStephen Warren <swarren@nvidia.com>
-
由 Hans de Goede 提交于
Add generic fs support, so that commands like ls, load and test -e can be used on ubifs. Signed-off-by: NHans de Goede <hdegoede@redhat.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Hans de Goede 提交于
Implement the necessary functions for implementing generic fs support for ubifs. Signed-off-by: NHans de Goede <hdegoede@redhat.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Hans de Goede 提交于
Modify the ubifs u-boot wrapper function prototypes for generic fs use, and give them their own header file. This is a preparation patch for adding ubifs support to the generic fs code from fs/fs.c. Signed-off-by: NHans de Goede <hdegoede@redhat.com> Reviewed-by: NHeiko Schocher <hs@denx.de>
-
由 Hans de Goede 提交于
This is not necessary / useful when not building with CONFIG_SANDBOX and with the addition of ubifs support to the generic fs commands it actually gets in the way, since both operate on a fake / NULL blkdev. Signed-off-by: NHans de Goede <hdegoede@redhat.com> Acked-by: NStephen Warren <swarren@nvidia.com>
-
由 Pierre Aubert 提交于
Scripts are multi-file images, the imxtract command should handle them in the same manner. Signed-off-by: NPierre Aubert <p.aubert@staubli.com>
-
由 Thomas Huth 提交于
In the "Getting Started with Coccinelle - KVM edition" presentation that has been held by Julia Lawall at the KVM forum 2015 (see the slides at http://events.linuxfoundation.org/sites/events/files/slides/tutorial_kvm_0.pdf), she pointed out some bad return value checks in U-Boot that can be detected with Coccinelle by using the following config file: @@ identifier x,y; identifier f; statement S; @@ x = f(...); ( if (x < 0) S | if ( - y + x < 0) S ) This patch now fixes these issues. Signed-off-by: NThomas Huth <huth@tuxfamily.org>
-
由 Guillaume GARDET 提交于
Add CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG support and enable it to set 'board_rev' and 'board_name' envs. 'board_rev' can be used in scripts to determine what board we are running on and 'board_name' for pretty printing. Signed-off-by: NGuillaume GARDET <guillaume.gardet@free.fr> Cc: Stephen Warren <swarren@wwwdotorg.org> Acked-by: NStephen Warren <swarren@wwwdotorg.org>
-
由 Bernhard Nortmann 提交于
For current U-Boot to initialize status LEDs via status_led_init(), it is required to have both CONFIG_STATUS_LED and STATUS_LED_BOOT defined. This may be a particular concern with GPIO LEDs, where __led_init() is required to correctly set up the GPIO (gpio_request and gpio_direction_output). Without STATUS_LED_BOOT the initialization isn't called, which could leave the user with a non-functional "led" command - due to the fact that the LED routines in gpio_led.c use gpio_set_value() just fine, but the GPIO never got set up properly in the first place. I think having CONFIG_STATUS_LED is sufficient to justify a corresponding call to status_led_init(), even with no STATUS_LED_BOOT defined. To do so, common/board_r.c needs call that routine, so it now is exposed via status_led.h. Signed-off-by: NBernhard Nortmann <bernhard.nortmann@web.de> [trini: Add dummy __led_init to pca9551_led.c] Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 24 10月, 2015 1 次提交
-
-
由 Bernhard Nortmann 提交于
For boards that support LEDs driven via GPIO (CONFIG_GPIO_LED), it may be useful to have some generic stubs (wrapper functions) for the "colored" LEDs. This allows defining STATUS_LED_* values directly to GPIO numbers, e.g.: #define STATUS_LED_GREEN 248 /* = PH24 */ To keep those optional, it's probably best to introduce an additional configuration setting. I've chosen CONFIG_GPIO_LED_STUBS for that. Placing the code in drivers/misc/gpio_led.c also ensures that it automatically depends on CONFIG_GPIO_LED too. Signed-off-by: NBernhard Nortmann <bernhard.nortmann@web.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-