This patch adds support in the pack_v2 script to limit
the wifi firmwares which packed into the single images
based on the profiles.
Add corresponding profile entry under each RDP
config in config.xml to restrict wifi fw images
packed into the single image.
Eg:
<profiles>256</profiles>
<profiles>512</profiles>
<profiles>512,256</profiles>
Note: No need add default profile in profiles tag.
Change-Id: I06667ec7ba31a2bbcb742fbd5319f0e30be193fc
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
This patch adds support to flash the bootconfig based on the
RDPs.
1. To flash bootconfig based on Multi-RDP add entry like
below in all flash partition xmls
for non-mmc flash partition:
<img_name type="string" bootconfig_type="1">file1_name</img_name>
<img_name type="string" bootconfig_type="2">file2_name</img_name>
<img_name type="string" bootconfig_type="3">file3_name</img_name>
for mmc flash partition:
bootconfig_type_max="2"
filename_img1="file1_name"
filename_img2="file2_name"
and specify which bootconfig to flash on each RDP by adding
entry like below, in config xml under each RDP nodes.
<bootconfig_type>1</bootconfig_type>
2. for single bootconfig case, there is no change.
just add single entry like below in all flash partition xmls
<img_name type="string">file_name</img_name>
Change-Id: Id68c4f6f6c4cced493ac5130378897711e8cb9e4
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
This patch add an conditional size boundary check to
make sure that the collected minidumps is within the
reserved memory region. If not, it throws failure
message and do reset.
Change-Id: I97c721f792350e83463f5dcff412785b8263bb4c
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
Skip reset in crash dump path which give access to user
to perform secure authentication.
in crash path,
bootipq cmd only authenticate kernel/rootfs.
booting to kernel is restircted.
Enable CONFIG_SKIP_RESET to skip reset in crashdump path.
Change-Id: I28fdd4dc6475d4d26b20a87aa039cef165db1375
Signed-off-by: Gurumoorthy Santhakumar <quic_gsanthak@quicinc.com>
A new SCM has been added in TZ to support AES 128 byte context length.
Updated aes driver to add the same. Added new command as mentioned
below for 128 byte context length.
derive_aes_256_max_ctxt_key 0x2 0x20 0x41000000 0x80
Note: This new SCM call has been introduced since initial SCM call does not
derive keys the same way as Linux Fscrypt feature (128 byte context length)
Signed-off-by: Poovendhan Selvaraj <quic_poovendh@quicinc.com>
Change-Id: Ie71fc0e9b3c0b0d01995745bb61cd2d82f07eb85
This patch enable the uboot to collec the minidump
by parsing the TLVs exposed by the kernel and store it
into the nvmem (Non volatile memory) either NAND / eMMC
To enable this feature,
setenv dump_minimal 1
setenv dump_to_nvmem "<partition_name>"
Change-Id: I2f2ed2ad2e8506957288052edaf5d6290ae787b7
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
Instead of updating the config_names in fdt_blob,
the config_names are maintained locally this avoids
the fdt_blob resizing
Change-Id: Ib1d6fecd973394363012564a8fc9e84d36fc7462
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>
Add support to increase context length if tz supports
128 bytes context length else fall back to old method.
Signed-off-by: Poovendhan Selvaraj <quic_poovendh@quicinc.com>
Change-Id: Ieded2c0139152e82011f792e91b875548fd29251
The missing calibrace leads to an in-valid hardware access,
it in-turn causes silent reboot. So, added the calibrace to
define the scope for the loop statement.
Change-Id: I0c719798af35eb21a824ee6f570501dab720e241
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
This patch enables support to do minidump on DDR.
Enable this support by setting respective reserved mem address
in the env "dump_to_mem"
setenv dump_minimal 1
setenv dump_to_mem "<addr> <size>"
addr & size param should matches with respect to the kernel
reserved memory region.
setenv dump_to_mem "0x44000000 0x500000"
Change-Id: I3f98269d42eed1e6301ed76eb9d1bcdd82046d41
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
This change adds MI01.3-C3 (RDP486) which is a derivative of RDP442
Change-Id: Ia19d7bf94962a52b76cc4556969c4ed1cd3706b6
Signed-off-by: Saahil Tomar <quic_saahtoma@quicinc.com>
ipq5332 is a TME-L based platform in which before
encrypt/decrypt, we are required to derive a key
handle.
This patch adds support for the same.
Change-Id: I28b327611b62381542086d6d599c4a0195525aca
Signed-off-by: Poovendhan Selvaraj <quic_poovendh@quicinc.com>
Here we are adding support to fix several warnings and
NPD.FUNC.MUST, ABV.GENERAL, INCORRECT.ALLOC_SIZE KW issues
in sysupgrade source code.
Change-Id: If8053878696494c1425ebd20840d17d9c6a74524
Signed-off-by: Vijay Balaji <quic_vijbal@quicinc.com>
In Q6, we are seeing rare PCIe enumeration failure and suspecting
U-boot PCIe enumeration (Gen1) could impact. Hence skipping the PCIe
enumeration during the board_init based on CONFIG_IPQ_PCI_INIT_DEFER
config and added it after autoboot is stopped.
Change-Id: I79d0d0aef2eeea9bf49157f405a29f23b3c2239d
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>
Updating the config_name parameter to
support openwrt backwards compatibility.
Change-Id: I129aad5df7e14bcf39d9f971a860b5884cde2667
Signed-off-by: Hariharan K <quic_harihk@quicinc.com>
During rootfs authentication, this following patch makes
the uboot will load rootfs at the load address mentioned
in the rootfs elf hdr which is present at the end of
kernel image.
Change-Id: Iba9d31c72d01449b858b3866f38f369b67011cae
Signed-off-by: Ram Kumar D <quic_ramd@quicinc.com>
Changing the CONFIG_IPQ_FDT_HIGH address for ipq807x
platform to avoid the DT blob load address from
overlapping with the tzapp_data(0x4A300000) region.
The kernel created a 2MB readonly mapping of the
DT blob. Due to this the mapping will also extend
into the tzapp(0x4A400000) region, which is TZ
protected.
Hence changing the FDT high address to from 0x4a400000
to 0x4a200000 to avoid access violation issues.
Change-Id: I3283c0afdec8ab126ea109c7ca9184a9ea577f16
Signed-off-by: Hariharan K <quic_harihk@quicinc.com>
Fix pci_find_ipq_devices(), which is checking all the PCIe hose from
the given ID and if searching device is not present, it moves till
the last PCIe hose and finds the device. This leads to duplicate
entries if unknown devices are also present. Instead it should
check only the selected PCIe hose and return success or failure.
Add QCN6432 in PCI device list so that list_pci command can show it.
Change-Id: I1fd1af9a760354f558680889dd5804abd6145dea
Signed-off-by: Praveenkumar I <quic_ipkumar@quicinc.com>
If usec >= 224000 usec, then:
usec * GPT_FREQ_KHZ = 224000 * 19200 >= 0x100590000,
which is a 33 bits value
To fix this usec is typecasted to 64 bit
(unsigned long long)usec * GPT_FREQ_KHZ
Change-Id: Ib1642d39b0581d2c04c62e415a1fd2dfed47fff1
Signed-off-by: Timple Raj M <quic_timple@quicinc.com>