- 07 Nov, 2016 1 commit
-
-
Caesar Wang authored
The CA53 and CM0 WDT clock gating in rk3399 SGRF, and ATF is in charge of it because the kernel can't touch SGRF. Basically the WDT didn't stop at suspend time, it just switched from the 24M to the 32k clock. That meant that the WDT would fire if you slept for long enough. In other word, the watchdog timer over count will increase to 750 (24*1000/32) times. The RK3399 HW watchdog interval is 21 seconds. When machine enters the suspend, the watchdog will reset the system after 35.7 (750/21) hours. BUG=chrome-os-partner:59257 TEST=daisydog checked and set value, powerd_dbus_suspend to verify. Change-Id: I88bb2a05b7d67d5ffd292f9d05d033ae9a6a3593 Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
- 03 Nov, 2016 7 commits
-
-
danh-arm authored
Porting guide: Improve bl1_plat_mem_check() doc
-
danh-arm authored
BL31 runtime instrumentation fixes and documentation update
-
Sandrine Bailleux authored
This patch fixes the type of the return value of bl1_plat_mem_check() in the porting guide. It also specifies the expected return value. Change-Id: I7c437342b8bfb1e621d74b2edf0aaf97b913216a Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
-
dp-arm authored
Without an explicit cache flush, the next timestamp captured might have a bogus value. This can happen if the following operations happen in order, on a CPU that's being powered down. 1) ENTER PSCI timestamp is captured with caches enabled. 2) The next timestamp (ENTER_HW_LOW_PWR) is captured with caches disabled. 3) On a system that uses a write-back cache configuration, the cache line that holds the PMF timestamps is evicted. After step 1), the ENTER_PSCI timestamp is cached and not in main memory. After step 2), the ENTER_HW_LOW_PWR timestamp is stored in main memory. Before the CPU power down happens, the hardware evicts the cache line that contains the PMF timestamps for this service. As a result, the timestamp captured in step 2) is overwritten with a bogus value. Change-Id: Ic1bd816498d1a6d4dc16540208ed3a5efe43f529 Signed-off-by: dp-arm <dimitris.papastamos@arm.com>
-
dp-arm authored
Change-Id: I8e50df67e860b9589834445761a7b9927690fdce Signed-off-by: dp-arm <dimitris.papastamos@arm.com>
-
danh-arm authored
Support rk3399 dram
-
danh-arm authored
Fix format of patches passed to checkpatch
-
- 31 Oct, 2016 1 commit
-
-
davidcunado-arm authored
Comment fixes and .gitignore update
-
- 28 Oct, 2016 1 commit
-
-
davidcunado-arm authored
fiptool: fix Segmentation fault when only --verbose option is given
-
- 27 Oct, 2016 3 commits
-
-
Antonio Nino Diaz authored
Checkpatch is a script developed to verify the style of Linux kernel patches. As Kernel developers use emails to send patches for review, checkpatch is prepared for that specific format. This change adapts the Makefile to use said format. As a result, indentation in the commit message has been removed, thus fixing the warnings about Signed-off-by lines being preceded by whitespace. Fixes ARM-software/tf-issues#432 Change-Id: I00cb86365fe15f7e2c3a99a306c8eb51cf02fe86 Signed-off-by: Antonio Nino Diaz <antonio.ninodiaz@arm.com>
-
davidcunado-arm authored
Mandate 'Signed-off-by' line in commit messages
-
davidcunado-arm authored
fiptool: Link `toc_entry` and `image` structures via UUID
-
- 26 Oct, 2016 8 commits
-
-
Caesar Wang authored
The RK3399 supports close the center logic enter power mode, so we can close PD_CENTER to save more power during suspend. Therefore, we need to support save/restore the DDR PHY and controller registers during suspend/resume. Also, need CL (http://crosreview.com/397399 ) to check disabling center logic. Change-Id: I288defd8e9caa3846d9fa663a33e4d51df1aaa5d Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> Signed-off-by: Derek Basehore <dbasehore@chromium.org> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Caesar Wang authored
This patch intend to support save the registers of the DDR controller and PHY before suspend, and restore them after resume. Change-Id: Ia10b476c0b837628ac0f365416a7118292753e96 Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> Signed-off-by: Derek Basehore <dbasehore@chromium.org> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Caesar Wang authored
This changes the style of dmc register accesses to be a read/write on a base address plus a register offset instead of reinterpretting a base address as a struct and accessing members within that struct. Change-Id: Iead097cd6afdb830d8bc193608cd39d01ce5a6bc Signed-off-by: Derek Basehore <dbasehore@chromium.org> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Caesar Wang authored
This renames dram.c and dram.h to dfs.c and dfs.h respectively. This is to make room for common functionality between frequency scaling and suspend code for the DRAM in a pair of common files named dram.c and dram.h. It also removes a duplicate enum definition from dram_spec_timing.h Change-Id: Ibfa1041f8781401f9d27901fe8c61862bcb05562 Signed-off-by: Derek Basehore <dbasehore@chromium.org> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Caesar Wang authored
This moves the PMU register definitions into another file for use in later patches. Change-Id: I8b5f1e7938b63ada6a743cf9661c3e474e96e4e4 Signed-off-by: Derek Basehore <dbasehore@chromium.org> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Masahiro Yamada authored
Fix the following bug: $ tools/fiptool/fiptool -v Segmentation fault (core dumped) Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
-
davidcunado-arm authored
rockchip: optimize the link mechanism for SRAM code
-
davidcunado-arm authored
rockchip: fix A72 L2CTLR_DATA_RAM_LATENCY to 5
-
- 24 Oct, 2016 9 commits
-
-
Caesar Wang authored
The default value of L2CTLR_DATA_RAM_LATENCY is 2, depends to the test result on rk3399, the A72 will need lower voltage for high frequency if it's set to be 5, and almost no effect on performance. Change-Id: I99a6a43edcc0c58f7775c10f4b85669dc3eff66d Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Caesar Wang authored
Due to the PMU design, the PMU may not clear the WAKEUP bit after wakeup, therefore, the state machine at the power mode may enter the infinite loop during WFI. There is a solution that we can use the M0 to monitor the WAKEUP bit and clear it during power mode, then the state machine will be recovered immediately. Then, the DUT can exit the WFI normally. Change-Id: I303628553b728c214bf2d436bd3122032b5e669c Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Caesar Wang authored
This CL supports add M0 source code to built into the bl31.bin, the goal is that we can load the M0 code binary into SRAM and execute it. We need the M0 help us to clean the power_mode_en bit during the AP PMU enter the state machine with interrupt, and avoid to the AP can not exit the loop forever. Change-Id: I844582c54a1f0d44ca41290d44618df58679f341 Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> Signed-off-by: Patrick Georgi <pgeorgi@google.com> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Caesar Wang authored
Add the common extra.ld.S and customized rk3399.ld.S to extend to more features for different platforms. For example, we can add SRAM section and specific address to load there if we need it, and the common bl31.ld.S not need to be modified. Therefore, we can remove the unused codes which copying explicitly from the function pmusram_prepare(). It looks like more clear. Change-Id: Ibffa2da5e8e3d1d2fca80085ebb296ceb967fce8 Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
-
Masahiro Yamada authored
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
As described in the Porting Guide, plat_reset_handler should preserve x19 to x29. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
Do not double the phrase "called with the". Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
-
Sandrine Bailleux authored
This patch updates the configuration file for the checkpatch.pl script to check for the presence of a 'Signed-off-by' line in the commit message. This is now required by TF contribution process. Change-Id: I8bcd6d39a5dcd85547244d60c10a7cd2148c404f Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com>
-
davidcunado-arm authored
rockchip: fixes the wrong CLKSEL_CON count for CRU
-
- 21 Oct, 2016 1 commit
-
-
Caesar Wang authored
The CRU_CLKSEL_COUNT value is 108, not 0x108. Signed-off-by: Caesar Wang <wxt@rock-chips.com> Change-Id: Ib9db066b8b3ecafcee7f645dd5633b55a808e3d7
-
- 18 Oct, 2016 2 commits
-
-
danh-arm authored
partition: check GPT partition table
-
dp-arm authored
The `toc_entry` and `image` data structures had a cyclic relationship. This patch removes the explicit dependencies and introduces functions to link them via the UUID. This change highlights the intent of the code better and makes it more flexible for future enhancements. Change-Id: I0c3dd7bfda2a631a3827c8ba4831849c500affe9 Signed-off-by: dp-arm <dimitris.papastamos@arm.com>
-
- 17 Oct, 2016 4 commits
- 14 Oct, 2016 2 commits
-
-
davidcunado-arm authored
rockchip: fixes the clock select and divide register for rk3399
-
Soby Mathew authored
The values of CP15BEN, nTWI & nTWE bits in SCTLR_EL1 are architecturally unknown if EL3 is AARCH64 whereas they reset to 1 if EL3 is AArch32. This might be a compatibility break for legacy AArch32 normal world software if these bits are not set to 1 when EL3 is AArch64. This patch enables the CP15BEN, nTWI and nTWE bits in the SCTLR_EL1 if the lower non-secure EL is AArch32. This unifies the SCTLR settings for lower non-secure EL in AArch32 mode for both AArch64 and AArch32 builds of Trusted Firmware. Fixes ARM-software/tf-issues#428 Change-Id: I3152d1580e4869c0ea745c5bd9da765f9c254947 Signed-off-by: Soby Mathew <soby.mathew@arm.com>
-
- 13 Oct, 2016 1 commit
-
-
davidcunado-arm authored
Final updates for v1.3 release
-