From: Stefan Wahren <stefan.wahren@i2se.com>
To: Eric Anholt <eric@anholt.net>, Florian Fainelli <f.fainelli@gmail.com>
Cc: Phil Elwell <phil@raspberrypi.org>,
Scott Branden <sbranden@broadcom.com>,
Ray Jui <rjui@broadcom.com>, Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: bcm2836: Send event when onlining other cores
Date: Mon, 14 Aug 2017 20:40:42 +0200 (CEST) [thread overview]
Message-ID: <399697756.271804.1502736043014@email.1und1.de> (raw)
In-Reply-To: <1168905996.270506.1502730695418@email.1und1.de>
Hi Eric,
> Stefan Wahren <stefan.wahren@i2se.com> hat am 14. August 2017 um 19:11 geschrieben:
>
>
> Hi Florian,
>
> > Florian Fainelli <f.fainelli@gmail.com> hat am 14. August 2017 um 18:25 geschrieben:
> >
> >
> >
> >
> > On 08/08/2017 04:04 AM, Phil Elwell wrote:
> > > Secondary cores should enter a low-power idle state when waiting to
> > > be started. The "wfe" instruction causes a core to wait until an event
> > > or interrupt arrives before continuing to the next instruction, and
> > > the "sev" instruction sends a wakeup event to the other cores.
> > >
> > > Add an "sev" (and a memory barrier) to bcm2836_boot_secondary, the
> > > function that wakes the waiting cores during booting. This is required
> > > if the secondary cores are sitting in "wfe", and harmless if not.
> >
> > Eric, should I just pick this up for the upcoming ARM SoC pull requests
> > that I am preparing, or do you have more changes aside from the two tags
> > I already merged?
>
> this patch depends on series "ARM: bcm2836: Move SMP startup code to arch/arm".
>
> I didn't had the time to test Phil's patch in all relevant cases. But i could at least prepare a branch with my changes with the acks.
i prepared the branches bcm2835-dt-next-v2 and bcm2835-soc-next.
Stefan
next prev parent reply other threads:[~2017-08-14 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 11:04 [PATCH 0/1] " Phil Elwell
2017-08-08 11:04 ` [PATCH] " Phil Elwell
2017-08-14 16:25 ` Florian Fainelli
2017-08-14 17:11 ` Stefan Wahren
2017-08-14 18:40 ` Stefan Wahren [this message]
2017-08-15 18:04 ` Eric Anholt
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=399697756.271804.1502736043014@email.1und1.de \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=phil@raspberrypi.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/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
all inboxes | Powered by JetHome®