| 18f705fa | 11-May-2017 |
Derek Basehore <dbasehore@chromium.org> |
rockchip/rk3399: Remove unneeded register sets
This removes the mmio_... function calls to set the multicast bit for the PHY registers when overriding the write leveling values. These are not needed
rockchip/rk3399: Remove unneeded register sets
This removes the mmio_... function calls to set the multicast bit for the PHY registers when overriding the write leveling values. These are not needed since multicast is set by default when calling the function, and it's also better not to leave the side effect of disabling multicast when exiting the function.
Change-Id: I83e089a2a2d55268b3832f36724c3b2c4be81082 Signed-off-by: Derek Basehore <dbasehore@chromium.org>
show more ...
|
| 7d1b3f5a | 07-May-2017 |
Derek Basehore <dbasehore@chromium.org> |
rockchip/rk3399: remove unneeded DDR restore function
This removes the phy_dll_bypass_set function as it is unneeded. The values that function sets are saved during suspend, so the proper values wil
rockchip/rk3399: remove unneeded DDR restore function
This removes the phy_dll_bypass_set function as it is unneeded. The values that function sets are saved during suspend, so the proper values will be restored on resume.
Change-Id: I17542206c56e639ce8cb6375233145167441d4e2 Signed-off-by: Derek Basehore <dbasehore@chromium.org>
show more ...
|
| 60400fc8 | 06-May-2017 |
Derek Basehore <dbasehore@chromium.org> |
rockchip/rk3399: Save space for DRAM suspend data
This removes the space allocation for the unused PHY register space. For instance in PHY registers 0-127, only 0-90 are used, so don't save the 91-1
rockchip/rk3399: Save space for DRAM suspend data
This removes the space allocation for the unused PHY register space. For instance in PHY registers 0-127, only 0-90 are used, so don't save the 91-127 registers. This saves about 1.6KB of space.
Change-Id: I0c9f6d9bed8f0c1f3b8b805dfb10cf0c06208919 Signed-off-by: Derek Basehore <dbasehore@chromium.org>
show more ...
|
| bc5c3007 | 04-May-2017 |
Lin Huang <hl@rock-chips.com> |
rockchip: add pmusram section
the function pmu_cpuon_entrypoint() need to run in the pmusram, we just copy bin file to pmusram before, now we add pmusram section and link pmu_cpuon_entrypoint() to p
rockchip: add pmusram section
the function pmu_cpuon_entrypoint() need to run in the pmusram, we just copy bin file to pmusram before, now we add pmusram section and link pmu_cpuon_entrypoint() to pmusram directly
Change-Id: Iae31e4c01c480c8e6f565a8f588332b478efdb16 Signed-off-by: Lin Huang <hl@rock-chips.com> Signed-off-by: Caesar Wang <wxt@rock-chips.com>
show more ...
|
| ccdc044a | 14-Feb-2017 |
Xing Zheng <zhengxing@rock-chips.com> |
rockchip: rk3399: enable secure accessing for SRAM
Sorry to miss the security configuration for SRAM, if we don't support it, somebody may modify the comment of SRAM in the non-secure space. Let's f
rockchip: rk3399: enable secure accessing for SRAM
Sorry to miss the security configuration for SRAM, if we don't support it, somebody may modify the comment of SRAM in the non-secure space. Let's fix this issue.
Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
show more ...
|
| 5a5dc617 | 10-Feb-2017 |
Derek Basehore <dbasehore@chromium.org> |
rockchip: rk3399: Fix CAS latency setting
The F1 CAS latency setting was not bit shifted, which resulted in setting the DRAM additive latency value instead.
Signed-off-by: Derek Basehore <dbasehore
rockchip: rk3399: Fix CAS latency setting
The F1 CAS latency setting was not bit shifted, which resulted in setting the DRAM additive latency value instead.
Signed-off-by: Derek Basehore <dbasehore@chromium.org>
show more ...
|
| 43f52e92 | 09-Feb-2017 |
Xing Zheng <zhengxing@rock-chips.com> |
rockchip: rk3399: disable training modules after DDR DFS
On resume, we use the DFS hardware to switch frequency index, followed by a full training sequence on that index. Leaving the DFS training mo
rockchip: rk3399: disable training modules after DDR DFS
On resume, we use the DFS hardware to switch frequency index, followed by a full training sequence on that index. Leaving the DFS training modules enabled causes issues with the full training done at resume. We also only needs these enabled during a call to ddr_set_rate during runtime, so there's no issue disabling them at the end of ddr_set_rate.
Signed-off-by: Derek Basehore <dbasehore@chromium.org> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
show more ...
|
| 50bde47f | 02-Feb-2017 |
Derek Basehore <dbasehore@chromium.org> |
rockchip: rk3399: Move DQS drive strength setting to M0
This moves the setting of the DQS drive strength to the M0 to minimize the impact on DDR transactions. We need to have the DQS drive strength
rockchip: rk3399: Move DQS drive strength setting to M0
This moves the setting of the DQS drive strength to the M0 to minimize the impact on DDR transactions. We need to have the DQS drive strength changed for data training, which is triggered by the M0, but it also needs to be changed back when data training is finished.
Signed-off-by: Derek Basehore <dbasehore@chromium.org>
show more ...
|