- 02 Jun, 2021 1 commit
-
-
Pali Rohár authored
The UART code for the A3K platform assumes that UART parent clock rate is always 25 MHz. This is incorrect, because the xtal clock can also run at 40 MHz (this is board specific). The frequency of the xtal clock is determined by a value on a strapping pin during SOC reset. The code to determine this frequency is already in A3K's comphy driver. Move the get_ref_clk() function from the comphy driver to a separate file and use it for UART parent clock rate determination. Signed-off-by: Pali Rohár <pali@kernel.org> Change-Id: I8bb18a2d020ef18fe65aa06ffa4ab205c71be92e
-
- 01 Jun, 2021 3 commits
-
-
Pali Rohár authored
Macros PLAT_MARVELL_BOOT_UART* and PLAT_MARVELL_CRASH_UART* are defined to same values. De-duplicate them into PLAT_MARVELL_UART* macros. Signed-off-by: Pali Rohár <pali@kernel.org> Change-Id: Iae5daf7cad6a971e6f3dbe561df3d0174106ca7f
-
Pali Rohár authored
Macros PLAT_MARVELL_BL31_RUN_UART* are not used since commit d7c4420c ("plat/marvell: Migrate to multi-console API"). Remove them. Signed-off-by: Pali Rohár <pali@kernel.org> Change-Id: I5ec959ef4de87dcfb332c017ad2599bf8af6ffc3
-
Pali Rohár authored
When configuring the UART_BAUD_REG register, the function console_a3700_core_init() currently only changes the baud divisor field, leaving other fields to their previous value. This is incorrect, because the baud divisor is computed with the assumption that the parent clock rate is 25 MHz, and since the other fields in this register configure the parent clock, which could have been changed by U-Boot or Linux. Fix this function to also configure the other fields so that the UART parent clock is selected to be the xtal clock. For example without this change TF-A prints only ERROR: a3700_system_off needs to be implemented followed by garbage after plat_crash_console_init() is called. After applying this change instead of garbage it also print crash info: PANIC at PC : 0x0000000004023800 Signed-off-by: Pali Rohár <pali@kernel.org> Change-Id: I72f338355cc60d939b8bb978d9c7fdd576416b81
-
- 28 May, 2021 1 commit
-
-
Pali Rohár authored
UART parent clock is by default the platform's xtal clock, which is 25 MHz. The value defined in the driver, though, is 25.8048 MHz. This is a hack for the suboptimal divisor calculation Divisor = UART clock / (16 * baudrate) which does not use rounding division, resulting in a suboptimal value for divisor if the correct parent clock rate was used. Change the code for divisor calculation to Divisor = Round(UART clock / (16 * baudrate)) and change the parent clock rate value to 25 MHz. The final UART divisor for default baudrate 115200 is not affected by this change. (Note that the parent clock rate should not be defined via a macro, since the xtal clock can also be 40 MHz. This is outside of the scope of this fix, though.) Signed-off-by: Pali Rohár <pali@kernel.org> Change-Id: Iaa401173df87aec94f2dd1b38a90fb6ed0bf0ec6
-
- 17 May, 2021 3 commits
-
-
Madhukar Pappireddy authored
* changes: docs(prerequisites): add `--no-save` to `npm install` fix(hooks): downgrade `package-lock.json` version
-
Chris Kay authored
To avoid the mistake fixed by the previous commit, ensure users install the Node.js dependencies without polluting the lock file by passing `--no-save` to the `npm install` line. Change-Id: I10b5cc17b9001fc2e26deee02bf99ce033a949c1 Signed-off-by: Chris Kay <chris.kay@arm.com>
-
Chris Kay authored
The NPM lock file was accidentally updated using a later version of Node.js than required by the prerequisites. This upgraded the lock file to the v2 format, which causes a warning on Node.js 14 (the prerequisites version). This moves the lock file back to v1 by installing the dependencies with Node.js 14. Change-Id: I382d599fd2b67b07eb9234d14e7b631db6b11453 Signed-off-by: Chris Kay <chris.kay@arm.com>
-
- 14 May, 2021 3 commits
-
-
Madhukar Pappireddy authored
-
bipin.ravi authored
-
Olivier Deprez authored
-
- 13 May, 2021 3 commits
-
-
Joanna Farley authored
-
Madhukar Pappireddy authored
-
Zelalem authored
Clean up instructions for building/running TF-A on the Juno platform and add correct link to SCP binaries. Signed-off-by: Zelalem Aweke <zelalem.aweke@arm.com> Change-Id: I536f98082e167edbf45f29ca23cc0db44687bb3b
-
- 12 May, 2021 3 commits
-
-
Madhukar Pappireddy authored
Updated the minor version in the makefile Change-Id: Ie2b3ce5b36a105a0e2fff52c3740cc9702ca3108 Signed-off-by: Madhukar Pappireddy <madhukar.pappireddy@arm.com>
-
Chris Kay authored
An indirect dependency of Commitizen (`merge`) is currently failing the NPM.js auditor due to vulnerability CVE-2020-28499. This commit moves the minimum version of Commitizen to 4.2.4, which has resolved this vulnerability. Change-Id: Ia9455bdbe02f7406c1a106f173c4095943a201ed Signed-off-by: Chris Kay <chris.kay@arm.com>
-
Olivier Deprez authored
General refresh of the SPM document. Change-Id: I2f8e37c3f34bc8511b115f00b9a53b6a6ff41bea Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
-
- 07 May, 2021 2 commits
-
-
Madhukar Pappireddy authored
Change log for trusted-firmware-a v2.5 release Change-Id: I6ffc8a40d2cc3a18145b87f895acdc1400db485a Signed-off-by: Madhukar Pappireddy <madhukar.pappireddy@arm.com>
-
Mark Dykes authored
-
- 05 May, 2021 3 commits
-
-
Mark Dykes authored
-
laurenw-arm authored
Removing the "Upcoming" change log due to the change in change log processing. Signed-off-by: Lauren Wehrmeister <lauren.wehrmeister@arm.com> Change-Id: I6d2cc095dca3e654bd7e6fec2077c58bfbc48bb5
-
Andre Przywara authored
In the comment in the ARM FPGA DT we promise a generous 100 MB initrd, but actually describe only a size of 20 MB. As initrds are the most common and easy userland option for the boards, let's increase the maximum size to the advertised 100 MB, to avoid unpacking errors when an initrd exceeds the current limit of 20 MB. Change-Id: If08ba3fabdad27b2c2aff93b18c3f664728b4348 Signed-off-by: Andre Przywara <andre.przywara@arm.com>
-
- 04 May, 2021 2 commits
-
-
Mark Dykes authored
-
laurenw-arm authored
Reverting FVP versions to previous version 11.12.38 for Cortex-A32x4 and Neoverse-N2x4. Change-Id: I81e8ad24794dd425a9e9a66dc8bb02b42191abf1 Signed-off-by: Lauren Wehrmeister <lauren.wehrmeister@arm.com>
-
- 30 Apr, 2021 14 commits
-
-
Lauren Wehrmeister authored
-
bipin.ravi authored
-
Zelalem authored
This is the first release of the public Trusted Firmware A class threat model. This release provides the baseline for future updates to be applied as required by developments to the TF-A code base. Signed-off-by: Zelalem Aweke <zelalem.aweke@arm.com> Change-Id: I3c9aadc46196837679f0b1377bec9ed4fc42ff11
-
laurenw-arm authored
Updated the list of supported FVP platforms as per the latest FVP release. Change-Id: I1abd0a7885b1133715062ee1b176733556a4820e Signed-off-by: Lauren Wehrmeister <lauren.wehrmeister@arm.com>
-
Manish Pandey authored
-
Manish Pandey authored
* changes: plat: imx8mp: change the bl31 physical load address plat: imx8m: Fix the macro define error
-
Jacky Bai authored
on i.MX8MP A1 silicon, the OCRAM space is extended to 512K + 64K, currently, OCRAM @0x960000-0x980000 is reserved for BL31, it will leave the last 64KB in non-continuous space. To provide a continuous 384KB + 64KB space for generic use, so move the BL31 space to 0x970000-0x990000 range. Signed-off-by: Jacky Bai <ping.bai@nxp.com> Change-Id: I96d572fc0f87f05a60f55e0552a68b6e70f8e7f4
-
Jacky Bai authored
the 'always_on' member should be initialized from 'on'. Signed-off-by: Jacky Bai <ping.bai@nxp.com> Change-Id: I5746ff40075b4fcda2ac7d04a8d7f1269af17e91
-
Manish Pandey authored
* changes: plat: ti: k3: board: Let explicitly map our SEC_SRAM_BASE to 0x0 plat: ti: k3: board: Lets cast our macros plat: ti: k3: common: bl31_setup: Use BL31_SIZE instead of computing plat: ti: k3: platform_def.h: Define the correct number of max table entries plat: ti: k3: board: lite: Increase SRAM size to account for additional table
-
Olivier Deprez authored
-
Usama Arif authored
This allows the the Matterhorn ELP Arm core to operate at its designated OPP. Signed-off-by: Usama Arif <usama.arif@arm.com> Change-Id: I7ccef0cfd079d630c3cfe7874590bf42789a1dca
-
Olivier Deprez authored
-
Olivier Deprez authored
-
Olivier Deprez authored
PSA wording is not longer associated with FF-A. Change-Id: Id7c53b9c6c8f383543f6a32a15eb15b7749d8658 Signed-off-by: Olivier Deprez <olivier.deprez@arm.com>
-
- 29 Apr, 2021 2 commits
-
-
Yann Gautier authored
To compare the "okay" string of a property, strncmp is used but with the length given by fdt_getprop. This len value is reported as tainted by Coverity [1]. We just can use strlen("okay") which is a known value to compare the 2 strings. [1] https://scan4.coverity.com/reports.htm#v51972/p11439/fileInstanceId=96515154&defectInstanceId=14219121&mergedDefectId=342997 Signed-off-by: Yann Gautier <yann.gautier@foss.st.com> Change-Id: Ic8fb6ccf3126a37df615e433eb028861812015da
-
Olivier Deprez authored
* changes: docs: add build options for GPT support enablement feat(plat/arm): add GPT parser support
-