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>
Call board_flash_protect only if the primary/secondary boot
type of the board is mmc.
Change-Id: Ib6f1251a7435a08d647909202c6570c383a64311
Signed-off-by: Balaji Jagadeesan <bjagadee@codeaurora.org>
Extended SoC major and minor version fixup
to kernel device-tree on IPQ8064 and IPQ4019.
Also includes cpu_type fixup for IPQ4019.
Find two new entries in the root-node:
soc_version_major, soc_version_minor
Change-Id: I99210aefdc578890b62779d253764b82fe47c543
Signed-off-by: Gokul Sriram Palanisamy <gokulsri@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>
UBIFS has add_node function and FDT dynamic patch has
add_node global variable which generates link error.
Change-Id: I5e1350c6280a0ecb0906743fc93563cf5b106d42
Signed-off-by: Abhishek Sahu <absahu@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>
'forever' (Infinite while loop) function gets called in dump
collection path. 'ak_secondary_cpu_init' function gets called
in runmulticore path.
Change-Id: Ie7bcf618fd6da5ce968954db538ae345c4f43d92
Signed-off-by: Vinoth Gnanasekaran <vgnana@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>
When SPI NOR is treated as psudo-nand,
SPI-NOR gets stuck in 3-byte mode
causing reads at incorrect offssets.
Change-Id: I062bce4755ee1b7be0d8dcc88ae9d5412143b6e1
Signed-off-by: Gokul Sriram Palanisamy <gokulsri@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>
This change adds the two new command secure_authenticate, is_sec_boot_enabled.
command secure_authenticate, helps to authenticate the given image before
writing into the flash. This command takes three arguments, which are sw_id,
img_addr and img_size. Each image has its own sw_id.
command is_sec_boot_enabled, helps to check if the secure fuse is enabled or
not.
Change-Id: I7c388cc7a25e66f2c5d16ff6439d143193ca305b
Signed-off-by: Kathiravan T <kathirav@codeaurora.org>
When SPI nor initialization happens before SPI Nand, SPI nor gets
registered as the current nand device in nor+nand flash. This
results in ECC fail at uboot. Hence this patch changes the
initialization sequence .
Change-Id: I968f364b7dfa91571f24230f16f8d51a0971b254
Signed-off-by: Sasirekaa Madhesu <smadhesu@codeaurora.org>
Handling stack corruption in bootipq path. Due stack corruption
after sysupgrade the kernel is not booting it is stoping at
uboot. This stack corruption is happening due to invalid address
assignement while updating boot argument in uboot.
Change-Id: Ic2ff9f2218b0d577ed36947cd7dc021a764b0c03
Signed-off-by: Md Sadre Alam <mdalam@codeaurora.org>
In case of NOR boot mount the rootfs based on device
name not based on UUID. Check the flash type based on rootfs
offset. In case of NOR plus eMMC the rootfs offset will be 0xBAD0FF5E.
This is bad offset. In NOR only boot rootfs have proper offset.
Change-Id: I7a7ecf0c1d0f2dcec13c71561568d1e16686316b
Signed-off-by: Md Sadre Alam <mdalam@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>
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>
Added support to boot the kernel from alternate partition
Change-Id: I90e09e61293581347f48b6bd4d00982c81d7d9a8
Signed-off-by: Rajkumar Ayyasamy <arajkuma@codeaurora.org>
1. Added emmc clk reset during mmc deinitialization to
avoid the mmc init failure in kernal bootup.
2. Clock has been configured to 192 Mhz for SDHCI mode
3. Proper register is used for disabling emmc clock
Change-Id: Id21e294380ee904027e5d6d2b2929acbd7bac672
Signed-off-by: Rajkumar Ayyasamy <arajkuma@codeaurora.org>
