| ddd70f19 | 04-Nov-2024 |
Quentin Schulz <quentin.schulz@cherry.de> |
fix(rk3399): fix unquoted .incbin for clang
While GCC doesn't complain about anything for .incbin, clang does: """ <instantiation>:6:10: error: expected string in '.incbin' directive .incbin /build
fix(rk3399): fix unquoted .incbin for clang
While GCC doesn't complain about anything for .incbin, clang does: """ <instantiation>:6:10: error: expected string in '.incbin' directive .incbin /build/rk3399/release/m0/rk3399m0.bin ^ plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:20:1: note: while in macro instantiation INCBIN """/build/rk3399/release/m0/rk3399m0.bin""", "rk3399m0_bin", ".sram.incbin" ^ <instantiation>:6:10: error: expected string in '.incbin' directive .incbin /build/rk3399/release/m0/rk3399m0pmu.bin ^ plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:21:1: note: while in macro instantiation INCBIN """/build/rk3399/release/m0/rk3399m0pmu.bin""", "rk3399m0pmu_bin", ".pmusram.incbin" ^ """
Adding quotes around \file in .incbin fixes the clang issue but GCC now complains: """ plat/rockchip/rk3399/drivers/pmu/pmu_fw.S: Assembler messages: plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:14: Error: junk at end of line, first unrecognized character is `/' plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:20: Info: macro invoked from here plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:14: Error: unable to include `./' plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:20: Info: macro invoked from here plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:14: Error: junk at end of line, first unrecognized character is `/' plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:21: Info: macro invoked from here plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:14: Error: unable to include `./' plat/rockchip/rk3399/drivers/pmu/pmu_fw.S:21: Info: macro invoked from here """
Considering that the symbol is defined with escaped quotes, it is probably safe to remove the double quotes around the INBCIN macro parameter, so let's do that to make both compilers happy.
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Change-Id: Id18b0341353ffc00e44e2d3c643ccdd05cc20c4f
show more ...
|
| 5b886432 | 23-Apr-2018 |
Derek Basehore <dbasehore@chromium.org> |
rockchip/rk3399: Add watchdog support in pmusram
To catch early hangs in resume, this sets up the watchdog before anything else in the pmusram code (ignoring setting up the stack...). This uses hard
rockchip/rk3399: Add watchdog support in pmusram
To catch early hangs in resume, this sets up the watchdog before anything else in the pmusram code (ignoring setting up the stack...). This uses hard coded settings for the watchdog until the proper watchdog restore later on in the firmware/kernel.
This also restores the old watchdog register values before the PLLs are restored to make sure we don't temporarily switch over to a 1/3s timeout on the watchdog when the pclk_wdt goes from 4MHz to 100MHz.
Change-Id: I8f7652089a88783271b17482117b4609330abe80 Signed-off-by: Derek Basehore <dbasehore@chromium.org>
show more ...
|
| ff4735cf | 20-Apr-2018 |
Lin Huang <hl@rock-chips.com> |
rockchip/rk3399: Split M0 binary into two
All the m0 code run in SRAM before, but we need to watch PMU_POWER_ST when SOC enter into FSM, and SRAM will shutdown during this time, so this code need ru
rockchip/rk3399: Split M0 binary into two
All the m0 code run in SRAM before, but we need to watch PMU_POWER_ST when SOC enter into FSM, and SRAM will shutdown during this time, so this code need run in PMUSRAM. But PMUSRAM only 8K space, we can not put all the m0 binary into PMUSRAM, Split the M0 binary into two, dram part still run in SRAM, and suspend part run in PMUSRAM.
Change-Id: Ie08bdf3e2b8838f12b9297fe60ab0aad219684b1 Signed-off-by: Lin Huang <hl@rock-chips.com>
show more ...
|
| 8c1e78af | 24-Jan-2018 |
Derek Basehore <dbasehore@chromium.org> |
rockchip/rk3399: Add udelay to wait loops
We were looping for MAX_WAIT_COUNT in several places without any delays, so this adds the delays to make those loops more predictable.
Signed-off-by: Derek
rockchip/rk3399: Add udelay to wait loops
We were looping for MAX_WAIT_COUNT in several places without any delays, so this adds the delays to make those loops more predictable.
Signed-off-by: Derek Basehore <dbasehore@chromium.org>
show more ...
|