| c33473d5 | 19-Mar-2018 |
Varun Wadekar <vwadekar@nvidia.com> |
Tegra210: skip past sc7entry-fw signature header
This patch skips past the signature header added to the sc7entry-fw binary by the previous level bootloader. Currently, the size of the header is 1KB
Tegra210: skip past sc7entry-fw signature header
This patch skips past the signature header added to the sc7entry-fw binary by the previous level bootloader. Currently, the size of the header is 1KB, so adjust the start address and the binary size at the time of copy.
Change-Id: Id0494548009749035846d54df417a960c640c8f9 Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
show more ...
|
| 3ca3c27c | 27-Feb-2018 |
Varun Wadekar <vwadekar@nvidia.com> |
Tegra: support for System Suspend using sc7entry-fw binary
This patch adds support to enter System Suspend on Tegra210 platforms without the traditional BPMP firmware. The BPMP firmware will no long
Tegra: support for System Suspend using sc7entry-fw binary
This patch adds support to enter System Suspend on Tegra210 platforms without the traditional BPMP firmware. The BPMP firmware will no longer be supported on Tegra210 platforms and its functionality will be divided across the CPU and sc7entry-fw.
The sc7entry-fw takes care of performing the hardware sequence required to enter System Suspend (SC7 power state) from the COP. The CPU is required to load this firmware to the internal RAM of the COP and start the sequence. The CPU also make sure that the COP is off after cold boot and is only powered on when we want to start the actual System Suspend sequence.
The previous bootloader loads the firmware to TZDRAM and passes its base and size as part of the boot parameters. The EL3 layer is supposed to sanitize the parameters before touching the firmware blob.
To assist the warmboot code with the PMIC discovery, EL3 is also supposed to program PMC's scratch register #210, with appropriate values. Without these settings the warmboot code wont be able to get the device out of System Suspend.
Change-Id: I5a7b868512dbfd6cfefd55acf3978a1fd7ebf1e2 Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
show more ...
|
| 7db077f2 | 14-Feb-2018 |
Varun Wadekar <vwadekar@nvidia.com> |
Tegra210: support for cluster idle from the CPU
This patch adds support to enter/exit to/from cluster idle power state on Tegra210 platforms that do not load BPMP firmware.
The CPU initates the clu
Tegra210: support for cluster idle from the CPU
This patch adds support to enter/exit to/from cluster idle power state on Tegra210 platforms that do not load BPMP firmware.
The CPU initates the cluster idle sequence on the last standing CPU, by following these steps:
Entry ----- * stop other CPUs from waking up * program the PWM pinmux to tristate for OVR PMIC * program the flow controller to enter CC6 state * skip L1 $ flush during cluster power down, as L2 $ is inclusive of L1 $ on Cortex-A57 CPUs
Exit ---- * program the PWM pinmux to un-tristate for OVR PMIC * allow other CPUs to wake up
This patch also makes sure that cluster idle state entry is not enabled until CL-DVFS is ready.
Change-Id: I54cf31bf72b4a09d9bf9d2baaed6ee5a963c7808 Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
show more ...
|
| 620b2233 | 16-Jun-2017 |
Samuel Payne <spayne@nvidia.com> |
Tegra210_B01: SC7: Select RNG mode based on ECID
If ECID is valid, we can use force instantiation otherwise, we should use reseed for random data generation for RNG operations in SE context save DNI
Tegra210_B01: SC7: Select RNG mode based on ECID
If ECID is valid, we can use force instantiation otherwise, we should use reseed for random data generation for RNG operations in SE context save DNI because we are not keeping software save sequence in main.
Change-Id: I73d650e6f45db17b780834b8de4c10501e05c8f3 Signed-off-by: Samuel Payne <spayne@nvidia.com>
show more ...
|