All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suriyan Ramasami <suriyan.r@gmail.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: keir@xen.org, Ian Campbell <Ian.Campbell@citrix.com>,
	Tim Deegan <tim@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Jan Beulich <jbeulich@suse.com>,
	ian.jackson@citrix.com, Julien Grall <julien.grall@linaro.com>
Subject: Re: [XEN/ARM PATCH v6 1/1] Add OdroidXU board (Exynos 5410)
Date: Wed, 10 Sep 2014 17:51:31 -0700	[thread overview]
Message-ID: <CANoR_OCXow=7aUXR+0ZWd+2HZ4UP2-g7P8vK6eZS_C1-MiWjzg@mail.gmail.com> (raw)
In-Reply-To: <5410CF05.9070403@linaro.org>

On Wed, Sep 10, 2014 at 3:21 PM, Julien Grall <julien.grall@linaro.org> wrote:
> Hi Suriyan,
>
> On 08/09/14 10:26, Suriyan Ramasami wrote:
>>
>> As can be seen, the secondary CPUs check _hotplug_addr for a non zero
>> value on first being powered on, or after woken up from a wfe. This
>> _hotplug_addr happens to be at offset +0x1c from NS_RAM_BASE.
>> Linux mainline too has this hardcoded +0x1c.
>
>
> You half read the Linux code... This offset is only add when there is a
> secure firmware (detected by "samsung,secure-firmware" node in the device
> tree).
>
> On the Arndale the node doesn't exist.
>
Thanks for digging there Julien. Previously, I must have gone through
the linux code with only exynos5410 in mind. Nonetheless, looks like I
have left out the code which handles the arndale and possibly 5420 and
the 5800 (if they do not have "samsung,secure-firmware" defined). But
on the other hand, I do see arndale-octa has the "secure-firmware"
entry which is a 5420 (so does the 5800). This adds to the confusion.
This is from looking at the linux-3.16.y source.

Nonetheless, I think to handle arndale for now, I should add the
"samsung,secure-firmware" logic in the code which will then use
sysram_base_addr instead without any offset.

So, how do I go about this? Should I roll out another patch with these
cumulative changes and also add the BUG_ON change?

Thanks!
- Suriyan
> Regards,
>
> --
> Julien Grall

  reply	other threads:[~2014-09-11  0:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 22:57 [XEN/ARM PATCH v6 1/1] Add OdroidXU board (Exynos 5410) Suriyan Ramasami
2014-09-08 10:20 ` Ian Campbell
2014-09-08 17:26   ` Suriyan Ramasami
2014-09-09  9:15     ` Ian Campbell
2014-09-09 15:34       ` Suriyan Ramasami
2014-09-10 22:21     ` Julien Grall
2014-09-11  0:51       ` Suriyan Ramasami [this message]
2014-09-11  1:03         ` Julien Grall
2014-09-11  3:35           ` Suriyan Ramasami
2014-09-11 12:58             ` Ian Campbell
2014-09-11 13:30               ` Suriyan Ramasami
2014-09-11 13:35                 ` Ian Campbell
2014-09-11 18:36               ` Julien Grall
2014-09-12 10:19                 ` Ian Campbell
2014-09-10 14:07 ` Ian Campbell
2014-09-10 17:05   ` Suriyan Ramasami
2014-09-11  9:03     ` Ian Campbell
2014-09-10 21:08 ` Julien Grall
2014-09-11  8:53   ` Ian Campbell
2014-09-11 12:53     ` Ian Campbell
2014-09-11 18:27       ` Julien Grall
2014-09-12 10:21         ` Ian Campbell
2014-09-12 18:54           ` Julien Grall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANoR_OCXow=7aUXR+0ZWd+2HZ4UP2-g7P8vK6eZS_C1-MiWjzg@mail.gmail.com' \
    --to=suriyan.r@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@linaro.com \
    --cc=julien.grall@linaro.org \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.