On 06/02/2014 02:35 PM, Bartlomiej Zolnierkiewicz wrote:
* Use do_idle firmware method instead of cpu_do_idle() on boards with
secure firmware enabled.
* Use sysram_ns_base_addr + 0x24 address for exynos_boot_vector_addr()
and sysram_ns_base_addr + 0x20 one for exynos_boot_vector_flag() on
On Monday, June 02, 2014 03:15:07 PM Tomasz Figa wrote:
> Hi,
>
> On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> > * Use do_idle firmware method instead of cpu_do_idle() on boards with
> > secure firmware enabled.
> >
> > * Use sysram_ns_base_addr + 0x24 address for exynos_boot_vector_
Hi,
On 02.06.2014 14:35, Bartlomiej Zolnierkiewicz wrote:
> * Use do_idle firmware method instead of cpu_do_idle() on boards with
> secure firmware enabled.
>
> * Use sysram_ns_base_addr + 0x24 address for exynos_boot_vector_addr()
> and sysram_ns_base_addr + 0x20 one for exynos_boot_vector_f
* Use do_idle firmware method instead of cpu_do_idle() on boards with
secure firmware enabled.
* Use sysram_ns_base_addr + 0x24 address for exynos_boot_vector_addr()
and sysram_ns_base_addr + 0x20 one for exynos_boot_vector_flag() on
boards with secure firmware enabled.
This patch fixes han