From: Kumar Gala <galak@kernel.crashing.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Fix e500 v2 core reboot bug
Date: Wed, 7 Mar 2007 12:34:53 -0600 [thread overview]
Message-ID: <3CF6D7AF-D5E0-4325-8015-FE048C63E8B6@kernel.crashing.org> (raw)
In-Reply-To: <1173291755.23776.121.camel@ld0161-tx32>
On Mar 7, 2007, at 12:22 PM, Jon Loeliger wrote:
> From: Roy Zang <tie-fei.zang@freescale.com>
>
> For e500 v2 core, a new reset control register is added.
>
> Signed-off-by: Roy Zang <tie-fei.zang@freescale.com>
> Acked-by: Jon Loeliger <jdl@freescale.com>
Nack. See comments below.
- k
> ---
> arch/powerpc/platforms/85xx/misc.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/platforms/85xx/misc.c b/arch/powerpc/
> platforms/85xx/misc.c
> index 3e62fcb..9fcbf56 100644
> --- a/arch/powerpc/platforms/85xx/misc.c
> +++ b/arch/powerpc/platforms/85xx/misc.c
> @@ -13,11 +13,21 @@
> #include <linux/irq.h>
> #include <linux/module.h>
> #include <asm/irq.h>
> +#include <asm/io.h>
> +#include <sysdev/fsl_soc.h>
>
> extern void abort(void);
>
> void mpc85xx_restart(char *cmd)
> {
> + unsigned int pvr;
> +
> + pvr = mfspr(SPRN_PVR);
> + if ((pvr >> 16) & 0x1){
Testing the PVR isn't proper.. you are using a system feature that
has nothing to do with the core revision.
Maybe add an attribute in the soc node for this?
> + u32 __iomem *rstcr;
> + rstcr = ioremap(get_immrbase() + 0xE00B0, 0x100);
You can't do the ioremap here, this my get called from interrupt
context.. See 83xx/misc.c for a slightly better example. The
unprotected arch_initcall is still an issue on 83xx.
> + *rstcr = 0x2; /* HRESET_REQ */
we should be using out_be32()
> + }
> local_irq_disable();
> abort();
> }
prev parent reply other threads:[~2007-03-07 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 18:22 [PATCH] Fix e500 v2 core reboot bug Jon Loeliger
2007-03-07 18:34 ` Kumar Gala [this message]
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=3CF6D7AF-D5E0-4325-8015-FE048C63E8B6@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=jdl@freescale.com \
--cc=linuxppc-dev@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