- Jul 26, 2015
-
-
Otavio Salvador authored
There is no need to use multiple lines when they fit into a single line. Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Otavio Salvador authored
Perfoming an OR operation on the error is not a good approach. Return the error immediately for each ESDHC instance instead. Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Otavio Salvador authored
Declare 'static' when possible. Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Otavio Salvador authored
Entering the maximum number of characters defined by CONFIG_SYS_CBSIZE into the console and hitting enter afterwards, causes a hang in the system because CONFIG_SYS_PBSIZE is not capable of storing the extra characters of the error message: "Unknown command '' - try 'help'". Use the default CONFIG_SYS_PBSIZE definition from config_fallbacks.h to solve this problem. Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Otavio Salvador authored
Remove the custom prompt and use the default instead. Signed-off-by:
Otavio Salvador <otavio@ossystems.com.br>
-
Peng Fan authored
DCIMVAC is upgraded to DCCIMVAC for the individual processor (Cortex-A7) that the DCIMVAC is executed on. We should follow the linux dma follow. Before DMA read, first invalidate dcache then after DMA read, invalidate dcache again. With the DMA direction DMA_FROM_DEVICE, the dcache need be invalidated again after the DMA completion. The reason is that we need explicity make sure the dcache been invalidated thus to get the DMA'ed memory correctly from the physical memory. Any cache-line fill during the DMA operations such as the pre-fetching can cause the DMA coherency issue, thus CPU get the stale data. Signed-off-by:
Peng Fan <Peng.Fan@freescale.com> Signed-off-by:
Ye.Li <B37916@freescale.com> Signed-off-by:
Nitin Garg <nitin.garg@freescale.com> Signed-off-by:
Jason Liu <r64343@freescale.com> Reviewed-by:
Stefano Babic <sbabic@denx.de>
-
Fabio Estevam authored
The variable 'ret' is used to store the value returned by pfuze_mode_init(), so it should be of type 'int' instead of 'unsigned int' in order to correctly handle negative numbers. Fix the variable type. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com>
-
Fabio Estevam authored
The variable 'ret' is used to store the value returned by pfuze_mode_init(), so it should of type 'int' instead of 'unsigned int' in order to correctly handle negative numbers. Fix the variable type. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com>
-
Fabio Estevam authored
Warp has a MAX77696 PMIC connected via I2C1 bus. Add support for it. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com>
-
Fabio Estevam authored
Add support for MAX77696 PMIC. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com>
-
Fabio Estevam authored
It seems that many comments were copied from the I2C uclass, so adjust the comments for the thermal class. Reported-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Acked-by:
Otavio Salvador <otavio@ossystems.com.br> Acked-by:
Simon Glass <sjg@chromium.org>
-
Adrian Alonso authored
* Extend imximage DCD version 2 to support DCD commands CMD_WRITE_CLR_BIT 4 [address] [mask bit] means: while ((*address & ~mask) != 0); CMD_CHECK_BITS_SET 4 [address] [mask bit] means: while ((*address & mask) != mask); CMD_CHECK_BITS_CLR 4 [address] [mask bit] means: *address = *address & ~mask; * Add set_dcd_param_v2 helper function to set DCD command parameters Signed-off-by:
Adrian Alonso <aalonso@freescale.com> Signed-off-by:
Peng Fan <Peng.Fan@freescale.com>
-
Stefan Roese authored
This patch adds support for the "OHB System AG" baseboard with is equipped with the TQMa6S SoM. Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Markus Niebel <Markus.Niebel@tq-group.com> Cc: Stefano Babic <sbabic@denx.de>
-
- Jul 17, 2015
-
-
git://git.denx.de/u-bootStefano Babic authored
-
- Jul 15, 2015
-
-
git://git.denx.de/u-boot-x86Tom Rini authored
-
Bin Meng authored
We should not leave the expansion ROM address window open when there is not a valid ROM. Suggested-by:
Matt Porter <mporter@konsulko.com> Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Tested-by:
Simon Glass <sjg@chromium.org> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
Currently PCI expansion ROM address is assigned by a call to pciauto_setup_rom() outside of the pci auto config process. This does not work when expansion ROM is on a device behind PCI bridge where bridge's memory limit register was already programmed to a value that does not cover the newly assigned expansion ROM address. To fix this, we should configure the ROM address during the auto config process. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Tested-by:
Simon Glass <sjg@chromium.org> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
This driver was originally added to support the native IDE mode for Intel chipset, however it has some bugs like not supporting ATAPI devices, endianness issue, or even broken build when CONFIG_LAB48. Given no board is using this driver as of today, rather than fixing all these issues we just remove it from the source tree. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
Update crownbay_defconfig and minnowmax_defconfig with 'savedefconfig' result so that the config option order matches Kconfig. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
On 32-bit machine strtol() returns LONG_MAX which is 0x7fffffff, which is wrong for u-boot.rom components like u-boot-x86-16bit.bin. Change to use strtoll() so that it works on both 32-bit and 64-bit machines. Reported-by:
Fei Wang <wangfei.jimei@gmail.com> Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
To try to reduce the pain of confusion of binary blobs, add MD5 checksums for the current versions. This may worsen the situation as new versions appear, but it should still be possible to obtain these versions, and thus get a working setup. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
Simon Glass authored
Commit afbbd413 fixed this for non-driver-model. Make sure that the driver model code handles this also. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
Simon Glass authored
Adjust minnowmax to use driver model for PCI. This requires adding a device tree node to specify the ranges, removing the board-specific PCI code and ensuring that the host bridge is configured. Reviewed-by:
Bin Meng <bmeng.cn@gmail.com> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This driver should use the x86 PCI configuration functions. Also adjust its compatible string to something generic (i.e. without a vendor name). Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
Simon Glass authored
The layout of the ROM is a bit hard to discover by reading the code. Add a table to make it easier. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com>
-
Simon Glass authored
Enable a SPI environment and store it in a suitable place. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Jagan Teki <jteki@openedev.com>
-
Simon Glass authored
The logic is incorrect and currently has no effect. Fix it so that we can write to SPI flash, since by default it is write-protected. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com> Tested-by:
Andrew Bradford <andrew.bradford@kodakalaris.com>
-
Simon Glass authored
The status register on ICH9 is a single byte, so use byte access when writing to it, to avoid updating the control register also. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Bin Meng <bmeng.cn@gmail.com> Reviewed-by:
Jagan Teki <jteki@openedev.com>
-
Bin Meng authored
Store VESA parameters to Linux setup header so that vesafb driver in the kernel could work. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org> Tested-by:
Jian Luo <jian.luo4@boschrexroth.de>
-
Bin Meng authored
Enable graphics support on Intel Crown Bay board With the help of vgabios for Intel TunnelCreek IGD. Tested with an external LVDS panel connected to X4 connector and SDVO adapter connected to X9 connector on the board. Signed-off-by:
Jian Luo <jian.luo4@boschrexroth.de> Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
MARK_GRAPHICS_MEM_WRCOMB is not referenced anywhere in the code, hence remove it. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
Move X86_OPTION_ROM_FILE & X86_OPTION_ROM_ADDR to arch/x86/Kconfig and rename them to VGA_BIOS_FILE & VGA_BIOS_ADDR which depend on HAVE_VGA_BIOS. The new names are consistent with other x86 binary blob options like HAVE_FSP/FSP_FILE/FSP_ADDR. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
Print the meaningful base address and mask of an MTRR range without showing the memory type encoding or valid bit. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
Per CPUID:80000008h result, the maximum physical address bits of TunnelCreek processor is 32 instead of default 36. This will fix the incorrect decoding of MTRR range mask. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
We should setup fixed range MTRRs for some legacy regions like VGA RAM and PCI ROM areas as uncacheable. Note FSP may setup these to other cache settings, but we can override this in x86_cpu_init_f(). Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Jian Luo authored
The TunnelCreek IGD VBE reports 32-bit color depth regardless 24-bit color depth is configured. Since 24-bit mode already uses 4 bytes internally, it should be OK to just add this option in switch case. Signed-off-by:
Jian Luo <jian.luo4@boschrexroth.de> Acked-by:
Simon Glass <sjg@chromium.org> Tested-by:
Bin Meng <bmeng.cn@gmail.com>
-
Jian Luo authored
We should allow pci config read/write to host bridge (b.d.f = 0.0.0) in the int1a_handler() which is a valid pci device. Signed-off-by:
Jian Luo <jian.luo4@boschrexroth.de> Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Jian Luo authored
PCI option rom may use different SS during its execution, so it is not safe to assume esp pointed to the same location in the protected mode. Signed-off-by:
Jian Luo <jian.luo4@boschrexroth.de> Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Bin Meng authored
Per PCI spec, VGA device reports its class as standard 030000h in its configuration space, so we can use it to determine if we need run option rom instead of testing the supported vendor/device ids. Signed-off-by:
Bin Meng <bmeng.cn@gmail.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
The sub-bus passed to pciauto_prescan_setup_bridge() is incorrect. Fix it so that sub-buses are numbered correctly. Signed-off-by:
Simon Glass <sjg@chromium.org>
-