From: Andrii Anisov <andrii.anisov@globallogic.com>
To: Chen Baozi <baozich@gmail.com>
Cc: Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Xen Developer List <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 2/3] xen/arm: Support kick_cpus for OMAP5
Date: Thu, 15 Aug 2013 17:12:51 +0300 [thread overview]
Message-ID: <CAGQvs6h2Aj5HDoajcB7SijSODVAeGS==G-xx-waXZtx=FTUTig@mail.gmail.com> (raw)
In-Reply-To: <1376572790-27724-3-git-send-email-baozich@gmail.com>
> +kick_cpus_omap5:
> + /* write start paddr to AuxCoreBoot1 where ROM code will jump */
> + ldr r0, =(OMAP_AUX_CORE_BOOT_1)
> + ldr r2, =start
> + add r2, r2, r10
> + str r2, [r0]
> + ldr r0, =(OMAP_AUX_CORE_BOOT_0)
> + mov r2, #0x20
> + str r2, [r0]
> + dsb
> + sev
You don't need following call of kick_cpus_sgi:
> + ldr r2, =OMAP5_GIC_BASE_ADDRESS /* r2 := OMAP5 gic base address */
> + b kick_cpus_sgi
> kick_cpus_sgi:
Once CPU1 get an event it will check OMAP_AUX_CORE_BOOT_0 and, if it
is ok, jump to OMAP_AUX_CORE_BOOT_1 address.
Sincerely,
Andrii Anisov.
next prev parent reply other threads:[~2013-08-15 14:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 13:19 [PATCH v2 0/3] Specific mapping for dom0, smp kick cpus and hyp mode switch for OMAP5 Chen Baozi
2013-08-15 13:19 ` [PATCH v2 1/3] xen/arm: Specific mapping for dom0 on OMAP5 platform Chen Baozi
2013-08-22 10:21 ` Ian Campbell
2013-08-22 12:54 ` Ian Campbell
2013-08-23 0:04 ` Chen Baozi
2013-08-15 13:19 ` [PATCH v2 2/3] xen/arm: Support kick_cpus for OMAP5 Chen Baozi
2013-08-15 14:12 ` Andrii Anisov [this message]
2013-08-16 2:04 ` Chen Baozi
2013-08-15 13:19 ` [PATCH v2 3/3] xen/arm: Enable switch to hyp mode for OMAP5432 Chen Baozi
2013-08-15 14:09 ` Andrii Anisov
2013-08-15 14:25 ` Andrii Anisov
2013-08-15 14:27 ` Andrii Anisov
2013-08-15 14:51 ` Andrii Anisov
2013-08-15 14:37 ` Chen Baozi
2013-08-15 14:42 ` Andrii Anisov
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='CAGQvs6h2Aj5HDoajcB7SijSODVAeGS==G-xx-waXZtx=FTUTig@mail.gmail.com' \
--to=andrii.anisov@globallogic.com \
--cc=Ian.Campbell@citrix.com \
--cc=baozich@gmail.com \
--cc=julien.grall@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).