From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: berlin: add SMP support
Date: Mon, 2 Jun 2014 12:03:32 +0200 [thread overview]
Message-ID: <20140602100332.GH28090@lunn.ch> (raw)
In-Reply-To: <20140602100048.GA12162@kwain>
On Mon, Jun 02, 2014 at 12:00:48PM +0200, Antoine T?nart wrote:
> Hi Andrew,
>
> On Mon, Jun 02, 2014 at 11:47:15AM +0200, Andrew Lunn wrote:
> > On Mon, Jun 02, 2014 at 11:21:02AM +0200, Antoine T?nart wrote:
> > > +
> > > +static inline void berlin_reset_cpu(unsigned int cpu)
> > > +{
> > > + u32 val;
> > > +
> > > + val = readl(cpu_ctrl + CPU_RESET);
> > > + val |= BIT(cpu_logical_map(cpu));
> > > + writel(val, cpu_ctrl + CPU_RESET);
> > > +}
> >
> > Is this performing a reset on the CPU, or is it taking it out of reset?
> >
> > If you are going to implement CPU hotplug at some point, you are going
> > to want to be able to put the CPU into reset, i.e. power it off, and
> > take it out of reset, i.e. power it on and getting it running. So it
> > might help if we get these function names clear now.
>
> It is performing a reset on the CPU. berlin_perform_reset_cpu() then?
Yes, that would be better.
What happens if the CPU is powered off? Will a reset power it on? Or
are you assuming the boot loader has powered it on?
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: "Antoine Ténart" <antoine.tenart@free-electrons.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
sebastian.hesselbarth@gmail.com,
thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alexandre.belloni@free-electrons.com, jszhang@marvell.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/5] ARM: berlin: add SMP support
Date: Mon, 2 Jun 2014 12:03:32 +0200 [thread overview]
Message-ID: <20140602100332.GH28090@lunn.ch> (raw)
In-Reply-To: <20140602100048.GA12162@kwain>
On Mon, Jun 02, 2014 at 12:00:48PM +0200, Antoine Ténart wrote:
> Hi Andrew,
>
> On Mon, Jun 02, 2014 at 11:47:15AM +0200, Andrew Lunn wrote:
> > On Mon, Jun 02, 2014 at 11:21:02AM +0200, Antoine Ténart wrote:
> > > +
> > > +static inline void berlin_reset_cpu(unsigned int cpu)
> > > +{
> > > + u32 val;
> > > +
> > > + val = readl(cpu_ctrl + CPU_RESET);
> > > + val |= BIT(cpu_logical_map(cpu));
> > > + writel(val, cpu_ctrl + CPU_RESET);
> > > +}
> >
> > Is this performing a reset on the CPU, or is it taking it out of reset?
> >
> > If you are going to implement CPU hotplug at some point, you are going
> > to want to be able to put the CPU into reset, i.e. power it off, and
> > take it out of reset, i.e. power it on and getting it running. So it
> > might help if we get these function names clear now.
>
> It is performing a reset on the CPU. berlin_perform_reset_cpu() then?
Yes, that would be better.
What happens if the CPU is powered off? Will a reset power it on? Or
are you assuming the boot loader has powered it on?
Andrew
next prev parent reply other threads:[~2014-06-02 10:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 9:21 [PATCH 0/5] ARM: Berlin: SMP support Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 9:21 ` [PATCH 1/5] ARM: berlin: add " Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 9:29 ` Russell King - ARM Linux
2014-06-02 9:29 ` Russell King - ARM Linux
2014-06-02 9:35 ` Antoine Ténart
2014-06-02 9:35 ` Antoine Ténart
2014-06-02 9:35 ` Antoine Ténart
2014-06-02 9:47 ` Andrew Lunn
2014-06-02 9:47 ` Andrew Lunn
2014-06-02 9:47 ` Andrew Lunn
2014-06-02 10:00 ` Antoine Ténart
2014-06-02 10:00 ` Antoine Ténart
2014-06-02 10:03 ` Andrew Lunn [this message]
2014-06-02 10:03 ` Andrew Lunn
2014-06-02 10:27 ` Antoine Ténart
2014-06-02 10:27 ` Antoine Ténart
2014-06-02 10:27 ` Antoine Ténart
2014-06-03 6:19 ` Jisheng Zhang
2014-06-03 6:19 ` Jisheng Zhang
2014-06-03 7:50 ` Andrew Lunn
2014-06-03 7:50 ` Andrew Lunn
2014-06-03 7:50 ` Andrew Lunn
2014-06-03 8:02 ` Jisheng Zhang
2014-06-03 8:02 ` Jisheng Zhang
2014-06-03 8:02 ` Jisheng Zhang
2014-06-03 6:31 ` Jisheng Zhang
2014-06-03 6:31 ` Jisheng Zhang
2014-06-03 6:31 ` Jisheng Zhang
2014-06-03 7:10 ` Antoine Ténart
2014-06-03 7:10 ` Antoine Ténart
2014-06-03 7:10 ` Antoine Ténart
2014-06-03 7:18 ` Jisheng Zhang
2014-06-03 7:18 ` Jisheng Zhang
2014-06-03 7:18 ` Jisheng Zhang
2014-06-02 9:21 ` [PATCH 2/5] Documentation: bindings: document the Marvell Berlin enable-method Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 10:44 ` Mark Rutland
2014-06-02 10:44 ` Mark Rutland
2014-06-02 10:44 ` Mark Rutland
2014-06-02 9:21 ` [PATCH 3/5] Documentation: bindings: add the Berlin CPU control doc Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 9:21 ` [PATCH 4/5] ARM: dts: berlin: add SMP related nodes and properties for BG2 Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 9:21 ` [PATCH 5/5] ARM: dts: berlin: add SMP related nodes and properties for BG2Q Antoine Ténart
2014-06-02 9:21 ` Antoine Ténart
2014-06-02 9:35 ` [PATCH 0/5] ARM: Berlin: SMP support Andrew Lunn
2014-06-02 9:35 ` Andrew Lunn
2014-06-02 9:44 ` Antoine Ténart
2014-06-02 9:44 ` Antoine Ténart
2014-06-02 9:44 ` Antoine Ténart
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=20140602100332.GH28090@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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.