[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [XEN/ARM: Patch v4 1/1] Add support for the Exynos secure firmware

On Mon, 2014-09-22 at 11:33 -0700, Suriyan Ramasami wrote:
> The existence of secure firmware is dictated by the presence of
> "samsung,secure-firmware" in the DT.
> The Arndale board does not have that entry, and uses the address as defined
> in "samsung,exynos4210-sysram", offset 0 as the smp init address. This is
> possibly true for all SoCs without secure firmware.
> For other boards which do have a "secure-firmware" node, use sysram-ns
> at offset +0x1c as the smp init address.
> The "secure-firmware" MMIO range contains ways to idle the CPU. As this gets
> mapped to DOM0 because of its presence in the DT, we blacklist it.
> Have tested this on the Odroid XU. I have also tested the other code path
> on the Odroid XU by removing "secure-firmware" from its DT. I could see
> that the other code path was exercised with correct smp init address
> values.
> Signed-off-by: Suriyan Ramasami <suriyan.r@xxxxxxxxx>

Booted (and rebooted!) on an Arndale, thanks.

Tested-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

and applied. I prefixed the subject with "xen: arm: ", you did this but
it was inside the [] so it gets stripped, the correct format for subject
is something like:
        [Patch v4 1/1] xen: arm: Add support for the Exynos secure
Then "git am" will remove the [.*] and the commit ends up with "xen:
arm: ..." which is what you should have had locally too.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.