linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv1 0/2] ARM: socfpga: Soft reset, hotplug and device tree clocks
Date: Mon, 18 Mar 2013 08:01:58 -0500	[thread overview]
Message-ID: <51471046.1010102@gmail.com> (raw)
In-Reply-To: <20130317181343.GB4394@amd.pavel.ucw.cz>

On 03/17/2013 01:13 PM, Pavel Machek wrote:
> Hi!
> 
>>> From: Dinh Nguyen <dinguyen@altera.com>
>>>
>>> Hi Arnd/Olof,
>>>
>>> Just 2 patches for mach-socfpga:
>>>
>>> 0001: ARM: socfpga: Enable hotplug and soft reset
>>> 	- Able to hotplug CPU1 by putting it into reset and bringing back online.
>>>
>>
>> Have you seen the discussion on PSCI? There's an ARM doc on it and
>> Linaro session from last week. Is there a possibility you can use that?
>> You would need to be able to run in non-secure mode and implement
>> smc calls.
> 
> What would be the advantage?

It gets rid of some platform code. If you do an A15 part, it abstracts
out the differences between the cores on entering/exiting coherency. It
should also save you from writing suspend/resume and cpuidle support for
your platform.

Once you do go to an A15, you will have to run in non-secure world. Once
you run in non-secure mode, you cannot do everything within the kernel.
So either you create custom smc calls or you use PSCI. If you really
support secure mode too, then the SOC design should prevent non-secure
accesses to anything that would affect the secure world like powergating
a core or cache.

> We do not have suitable hypervisor at the moment. Nor I see why it
> would be good to push power management into it.

It's not a hypervisor. A minimal implementation is only about 100 lines
of assembly.

> (Plus, the implementation seems pretty incomplete for arm32.).

That's the point. The linux side is simple. The secure monitor side is
also simplified somewhat. When you enter secure monitor mode, you are
automatically running with the cache and mmu off. This avoids the side
effects of cache allocations while trying to flush the caches.

Rob

> 
> 									Pavel
> 

  reply	other threads:[~2013-03-18 13:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 21:55 [PATCHv1 0/2] ARM: socfpga: Soft reset, hotplug and device tree clocks dinguyen at altera.com
2013-03-13 21:55 ` [PATCHv1 1/2] ARM: socfpga: Enable hotplug and soft reset dinguyen at altera.com
2013-03-17 18:18   ` Pavel Machek
2013-03-13 21:55 ` [PATCHv1 2/2] ARM: socfpga: Add clock entries into device tree dinguyen at altera.com
2013-03-17 18:35   ` Pavel Machek
2013-03-14  1:04 ` [PATCHv1 0/2] ARM: socfpga: Soft reset, hotplug and device tree clocks Rob Herring
2013-03-14 11:03   ` Pavel Machek
2013-03-14 13:26     ` Arnd Bergmann
2013-03-14 13:39   ` Dinh Nguyen
2013-03-17 18:13   ` Pavel Machek
2013-03-18 13:01     ` Rob Herring [this message]
2013-03-18 14:24       ` Pavel Machek
2013-03-18 14:39         ` Dinh Nguyen

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=51471046.1010102@gmail.com \
    --to=robherring2@gmail.com \
    --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 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).