linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/pasemi, cbe: Do not process decremeter or external wakeup from powersave
Date: Sat, 18 Mar 2017 22:46:50 +1000	[thread overview]
Message-ID: <20170318224650.4f69a31f@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <b17775f4-a2c5-ede6-33e3-6f6722a31d6e@xenosoft.de>

On Fri, 17 Mar 2017 15:43:22 +0100
Christian Zigotzky <chzigotzky@xenosoft.de> wrote:

> Nicholas Piggin <npiggin at gmail.com> writes:
> 
>  > Hi,
>  >
>  > I would like to start using a dedicated stack for system reset interrupt
>  > and treat it as a Linux nmi, which makes it tricky to call complex
>  > interrupt handlers directly from the system reset trap handler.
>  >
>  > So I would like to remove the decrementer and external handler calls from
>  > Cell and Pasemi platforms' system reset handler. I think we can just
>  > remove them if they can be handled when they re-fire as normal   
> interrupts?
>  > At the moment I don't have environments set up to test if this works.  
> 
> 
> It works fine with my AmigaOne X1000. (Nemo board with a P.A. Semi  
> PA6T-1682M CPU)

Thanks for testing, that's very useful. I will add your tested-by line
for the pasemi part of the patch.

Thanks,
Nick

  reply	other threads:[~2017-03-18 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 14:43 [PATCH] powerpc/pasemi, cbe: Do not process decremeter or external wakeup from powersave Christian Zigotzky
2017-03-18 12:46 ` Nicholas Piggin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-15 15:43 Nicholas Piggin
2017-03-16 10:31 ` Michael Ellerman
2017-03-17  6:12   ` Michael Ellerman
2017-03-17  7:48     ` [PATCH] powerpc/pasemi,cbe: " Nicholas Piggin
2017-03-17 10:17       ` [PATCH] powerpc/pasemi, cbe: " Michael Ellerman

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=20170318224650.4f69a31f@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=chzigotzky@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.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).