Currently, we search for "sdhci" node and continue with
mmc_init if it is present. We never check for status of
the sdhci node. As sdhci node is present in all the
board variants, mmc_init happens in all boards.
So, added a check to see if the status of sdhci node is
"okay" and continue with initialization, else return.
fdtdec_get_is_enabled library function checks only for
string "okay" which is the correct usage for status
variable. So, changed the status string in the
dts files accordingly.
Change-Id: I26ac5d9930b9e91e3d9d2436eff0cf02b8977b2e
Signed-off-by: Balaji Jagadeesan <bjagadee@codeaurora.org>
In DK06, there is no h/w support for mmc and sd.
In DK07, there is no h/w support for mmc and no support
for sd in uboot.
So, removing the sdhci entries from dts.
Change-Id: I39ac2fa56745d1ee3c23be5d8acd3ce5c355a135
Signed-off-by: Balaji Jagadeesan <bjagadee@codeaurora.org>
-Device IO commands are not supported
-CPU down is supported by waiting in loop
-Need reboot to execute bootipq command
Change-Id: Id10eef0c8e5feb636716461c58ba1640dfe46658
Signed-off-by: Santan Kumar <santank@codeaurora.org>
This change enables u-boot support for AP.DK07.1-C4 configuration.
AP.DK07.1-C4 enables QCA402x IOT support
Change-Id: I5982b8f8783755b03d11c878f8108d71e6ace6d1
Signed-off-by: Gitanjali Krishna <gitanjal@codeaurora.org>
This patch enables the support to authenticate the signed images
before flashing through the 'secure_authenticate' command.
Also, changes have been done for compatibility with the 64Bit TZ variants.
Change-Id: I0972b481b826c9594367eda31a2e9c87566db705
Signed-off-by: Kathiravan T <kathirav@codeaurora.org>
Adding device tree support for HK08 in u-boot-2016.
Change-Id: I30d653e0dcb5a0f2da453360f7255edd153c6606
Signed-off-by: Nikhil Prakash V <nprakash@codeaurora.org>
To use u-boot-2016 in DK04-C5 (Spi nor + Spi nand),
dk04-c5.dtb can be added
Change-Id: Id61a0d4d03b5e1482eca5572e73ed42fca175bc9
Signed-off-by: Rajkumar Ayyasamy <arajkuma@codeaurora.org>
This change increases Drive strength of nand-controller
GPIO pins from 2 MA to 8 MA to support all NAND flash.
Change-Id: I250deb47f0ddc770fe5c22dad1be32eb1a8f129d
Signed-off-by: Pavithra Palanisamy <pavip@codeaurora.org>
Add environment variable in uboot and device-tree node
in kernel as "flash_type" to expose current boot mode.
Change-Id: I15d4547f135f187a157dd7b303fc31f2df77cec2
Signed-off-by: Pavithra Palanisamy <pavip@codeaurora.org>
Get flash device ID based on partition to
extend grow partition support to NAND devices.
Change-Id: I332e4bb88d7506184ec0194cba34a1f69a80c76c
Signed-off-by: Gokul Sriram Palanisamy <gokulsri@codeaurora.org>
-Device IO commands are not supported
-CPU down is temporary supported by WFE instruction
-Need reboot to execute bootipq command
Change-Id: Ic7f1dece29e29f75b984018bcf1fc5f724282567
Signed-off-by: Santan Kumar <santank@codeaurora.org>
The ONFI NAND device specifies the required ECC correction in its
param page but for non ONFI device, we don't have such info.
The QPIC NAND contoller can use 8 bit ECC if the chip has required
number of spare bytes. This patch calculates the minimum required
spare bytes for using 8 bit ECC and select the same, if non ONFI
device has required number of spare bytes otherwise 4 bit ECC
will be used.
Change-Id: If7c718f4288eee16857171335897e3209a05fd0b
Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
This change is for mounting the rootfs partition in kernel based
on UUID(Universally Unique IDentifier). In embedded system it is
common to store rootfs on SD card or eMMC. Typically the kernel
command line has like: root=/dev/mmcblk0p20 to tell the kernel
where to look for rootfs partition. The problem in this approach
is the eMMC device number can vary based on wether the SD card
present or not in the SD card slot. Also depending on kernel version
the eMMC device number can vary. This means passing the eMMC device
for specifying the rootfs location is not robust approach.
If SD card first get detected then the base minor 0 is assigned to
SD card and kernel will try to mount rootfs from SD card and if
there is no rootfs present on SD card then kernel fail to mount the
rootfs.
Change-Id: Ia9e6dded61292bed8a10a40fd3cb86f4026393eb
Signed-off-by: Md Sadre Alam <mdalam@codeaurora.org>
Using of Dcache invalidate all resulted in stack which
was dirty being invalidated. Hence the return address stored
in stack wasn't flushed and this caused issues. Reverting to
invalidate_dcache_range.
Change-Id: I382e07a3a81885ab02c9eae38196d3aa3ba8b086
Signed-off-by: Manoharan Vijaya Raghavan <mraghava@codeaurora.org>
U-Boot now has dcache turned on. This requires cache flushing to
be performed before executing smc instrution. There are calls which
are made to TZ with huge buffer (such as kernel image for authentication).
Flushing and invalidating by address for such huge buffer will have
a performance impact, as the size of buffer is vastly bigger than
the cache size itself. Hence performing a flush of the entire cache
as opposed to performing cache flush with a start and end address.
Change-Id: If90a49d240ecf021ac9714025b6de0cce3fb9fc8
Signed-off-by: Manoharan Vijaya Raghavan <mraghava@codeaurora.org>
In case of AP148 , the S17C switch has to be additionally reset using
GPIO 63. This is done for soft reboot cases.
This change is ported based on commit e1c6cd2c07
Change-Id: I31ce8a34797ae353035a7b3fa05ad2783f78aece
Signed-off-by: Kathiravan T <kathirav@codeaurora.org>
Invokes TZ (via scm call) to pull Core-1 out of reset if
crash magic is set. TZ saves the register contents in the
NSS TCM, which is saved from U-Boot as CPU1_REG.BIN as part
of the crash dump saving procedure.
Change-Id: I8e1404fb354a47ae69d70d13a79f45bd4eb1c450
Signed-off-by: Antony Arun T <antothom@codeaurora.org>
Removing I2C and PCIe nodes from HK07 Uboot
DTS as these are not used.
Change-Id: I6ad642fe574b7cd1bd1369cd8baa92d6ccdcad00
Signed-off-by: Nikhil Prakash V <nprakash@codeaurora.org>
