Re: [Xen-devel] [PATCH v4 1/1] Support Odroid-XU board (Exynos 5410)

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Tue, 2014-08-19 at 16:19 -0700, Suriyan Ramasami wrote:
> +static int __init exynos5250_smp_init(void)
> +{
> +    return exynos_smp_init(EXYNOS5250_PA_SYSRAM);
> +}
> +
> +static int __init exynos5_smp_init(void)
> +{
> +    struct dt_device_node *node;
> +    u64 sysram_ns_base_addr;
> +    u64 size;
> +    int rc;
> +
> +    node = dt_find_compatible_node(NULL, NULL, 
> "samsung,exynos4210-sysram-ns");


Looking at Documentation/devicetree/bindings/arm/exynos/smp-sysram.txt
in the Linx tree it seems that this node is supposed to be present on
all systems, including 5250 and it seems to be present in all the DTBs I
can see.

IOW I think exynos5_smp_init and exynos5250_smp_init can just be
exynos5_smp_init (perhaps even folding in exynos_smp_init too).

I'm unsure whether we should fallback to the existing PA_SYSRAM value,
but my initial feeling is that we can get away without.

My only concern is that right now EXYNOS5250_PA_SYSRAM == 0x02020000 but
the DTB contains:

        sysram@02020000 {
[...]
                smp-sysram@0 {
[...]
                smp-sysram@2f000 {
                        compatible = "samsung,exynos4210-sysram-ns";
                        reg = <0x2f000 0x1000>;
                };
        };

IOW I think the final address for the NS sysram will be 0x204f000 and
not 0x2020000. I'm confused how this work{s,ed}. since the DT seem to
suggest that the sysram at 0x2020000 is secure mode, so we can't be
using it.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel