21 Nov, 2014
1 commit
-
Enable i.MX thermal DM driver to mx6sabre_common.h file. Since the
thermal is used in init_sequence_f, so define the CONFIG_SYS_MALLOC_F_LEN
to support DM driver using in pre relocation phase.Additional, thermal driver depends on ocotp, make sure to enable
CONFIG_MXC_OCOTP when CONFIG_IMX6_THERMAL is selected.Signed-off-by: Ye.Li
Signed-off-by: Nitin Garg
13 Nov, 2014
1 commit
-
Set the CONFIG_ENV_OFFSET from 384KB to 512KB offset, so we will have larger space
for u-boot image.
When enabling NAND flash support feature, the u-boot image size has exceeded the
384KB, which causes overlay to the environment variables storage.Signed-off-by: Ye.Li
Acked-by: Fabio Estevam
21 Oct, 2014
1 commit
-
HDMI config options can be placed into the common mx6sabre_common.h file to
avoid duplication.Signed-off-by: Fabio Estevam
24 Sep, 2014
1 commit
-
MXC SPI driver has a feature whereas a GPIO line can be used to force CS high
across multiple transactions. This is set up by embedding the GPIO information
in the CS value:cs = (cs | gpio << 8)
This merge of cs and gpio data into one value breaks the sf probe command:
if the use of gpio is required, invoking "sf probe " will not work, because
the CS argument doesn't have the GPIO information in it. Instead, the user must
use "sf probe << 8>". For example, if bank 2 gpio 30 is used to force
cs high on cs 0, bus 0, then instead of typing "sf probe 0" the user now must
type "sf probe 15872".This is inconsistent with the description of the sf probe command, and forces
the user to be aware of implementaiton details.Fix this by introducing a new board function: board_spi_cs_gpio(), which will
accept a naked CS value, and provide the driver with the relevant GPIO, if one
is necessary.Cc: Eric Nelson
Cc: Eric Benard
Cc: Fabio Estevam
Cc: Tim Harvey
Cc: Stefano Babic
Cc: Tom Rini
Cc: Marek Vasut
Reviewed-by: Marek Vasut
Signed-off-by: Nikita Kiryanov
Reviewed-by: Jagannadha Sutradharudu Teki
28 Apr, 2014
1 commit
-
Enable CONFIG_SYS_GENERIC_BOARD, so that we get rid of the following warning on
boot:"Warning: Your board does not use generic board. Please read
doc/README.generic-board and take action. Boards not
upgraded by the late 2014 may break or be removed."Signed-off-by: Fabio Estevam
05 Mar, 2014
1 commit
-
Copied from Linux sources "include/linux/sizes.h" commit
413541dd66d51f791a0b169d9b9014e4f56be13cSigned-off-by: Alexey Brodkin
Cc: Vineet Gupta
Cc: Tom Rini
Cc: Stefan Roese
Cc: Albert Aribaud
Acked-by: Tom Rini
Acked-by: Stefan Roese
[trini: Add bcm Kona platforms to the patch]
Signed-off-by: Tom Rini
11 Feb, 2014
1 commit
-
Change the default environment to use zImage instead of uImage, this
requires changes to the default environment to load a file named
zImage instead of uImage, and to use the 'bootz' command instead of
'bootm' when booting the kernel.Signed-off-by: Otavio Salvador
13 Jan, 2014
1 commit
-
A new 'update_emmc_firmware' target is added to allow for easy U-Boot
update in the eMMC as it has secury boot partition and this needs
specific handling on how to program the specific partition.Signed-off-by: Otavio Salvador
03 Jan, 2014
2 commits
-
This patch fixes allow for the DeviceTree and initrd relocation fixing
the boot of FSL 3.10.9-1.0.0-alpha kernel.This changes following boards:
- mx6sabreauto
- mx6sabresd
- wandboard
- udoo
- nitrogen6x
- cgtqmx6evalThe reasoning, as explained by Hui Liu, is:
,----
| The FDT blob will be placed at DDR physical addr: 0x11000000. When Linux kernel
| Boot up, it will decompress the compressed kernel image and place the decompressed
| kernel image at the low end of the DDR memory and start running from it. If the
| decompressed kernel image is bigger for example than 16M, it may over written the
| fdt blob which u-boot loaded to the DDR memory @0x11000000 with fdt_addr=0x11000000
|
| To expand the fdt_addr from 0x11000000 to 0x18000000, which can avoid the override
| Since we will not likely have one kernel image larger than 128MB.
`----Signed-off-by: Otavio Salvador
Acked-by: Stefano Babic -
Add CONFIG_CMD_FUSE option, so that the fuse API can be used.
Signed-off-by: Fabio Estevam
Reviewed-by: Benoît Thébaudeau
28 Nov, 2013
1 commit
-
mx6sabre board has a m25p32 SPI NOR connected to ECSPI1 port.
Add support for it.
This patch allows the SPI NOR flash to be succesfully detected:
=> sf probe
SF: Detected M25P32 with page size 256 Bytes, erase size 64 KiB, total 4 MiBSigned-off-by: Fabio Estevam
13 Nov, 2013
1 commit
-
There is no real benefit in adding the board name into U-boot's prompt, so
remove the custom CONFIG_SYS_PROMPT definitions so that the standard "=> "
prompt is used across FSL boards.Signed-off-by: Fabio Estevam
05 Nov, 2013
1 commit
-
Remove platform CONFIG_SYS_HZ definition for configs a-z*.
Signed-off-by: Rob Herring
31 Jul, 2013
1 commit
-
Conflicts:
board/freescale/mx6qsabrelite/Makefile
board/freescale/mx6qsabrelite/mx6qsabrelite.c
include/configs/mx6qsabrelite.hSigned-off-by: Stefano Babic
27 Jul, 2013
1 commit
-
Signed-off-by: Pardeep Kumar Singla
24 Jul, 2013
1 commit
-
Signed-off-by: Wolfgang Denk
[trini: Fixup common/cmd_io.c]
Signed-off-by: Tom Rini
26 Jun, 2013
1 commit
-
The SabreSD platform is available with i.MX6Q or i.MX6DL. This patch adds the
support of the i.MX6DL. The config file and the board directory are renamed
to remove the reference to the MX6Q.Signed-off-by: Pierre Aubert
CC: Stefano Babic
Reviewed-by: Fabio Estevam