linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/3] POWERPC] cpm2: CPM2 interrupt controller fix
Date: Wed, 24 Jan 2007 15:56:42 -0600	[thread overview]
Message-ID: <75A90F7F-60B5-45CC-ACEB-109672475283@kernel.crashing.org> (raw)
In-Reply-To: <20070124191927.3033.60973.stgit@localhost.localdomain>


On Jan 24, 2007, at 1:19 PM, Vitaly Bordug wrote:

>
> This contains important fixes for the CPM2 PIC code. Eliminated
> CPM_IRQ_OFFSET, pulling the respective interrupt numbers from the  
> interrupt
> mapping. Updated devicetree files to reflect that. Changed direct
> IC-related IO accesses to the IO accessors. Fixed all the sense  
> values to
> keep coherency with ipic. In the current code, CPM2 stuff will have  
> no IRQs
> and hence could be hardly usable.
>
> Signed-off-by: Vitaly Bordug <vbordug@ru.mvista.com>
> ---
>
>  arch/powerpc/boot/dts/mpc8272ads.dts |   47 +++++++-----
>  arch/powerpc/boot/dts/mpc8560ads.dts |   10 +-
>  arch/powerpc/sysdev/cpm2_pic.c       |  138 ++++++++++++++++++ 
> +---------------
>  arch/powerpc/sysdev/cpm2_pic.h       |    9 ++
>  include/asm-powerpc/mpc8260.h        |   24 ++++++
>  5 files changed, 142 insertions(+), 86 deletions(-)

[snip]

> diff --git a/arch/powerpc/sysdev/cpm2_pic.h b/arch/powerpc/sysdev/ 
> cpm2_pic.h
> index 2840616..643a857 100644
> --- a/arch/powerpc/sysdev/cpm2_pic.h
> +++ b/arch/powerpc/sysdev/cpm2_pic.h
> @@ -1,6 +1,15 @@
>  #ifndef _PPC_KERNEL_CPM2_H
>  #define _PPC_KERNEL_CPM2_H
>
> +
> +/* External IRQS */
> +#define CPM2_IRQ_EXT1		19
> +#define CPM2_IRQ_EXT7		25
> +
> +/* Port C IRQS */
> +#define CPM2_IRQ_PORTC15	48
> +#define CPM2_IRQ_PORTC0		63
> +

Let's just add these defines in the .c since they aren't needed by  
anyone else.

>  extern intctl_cpm2_t *cpm2_intctl;

Can you explain the logic here with cpm2_intctl?  It seems like  
cpm2_reset sets this pointer and that's it.  Would it make more sense  
to just have cpm2_pic_init use cpm2_immr and keep cpm2_intctl static  
to cpm2_pic.c?

>  extern unsigned int cpm2_get_irq(void);

Also, we should think about moving cpm2_cascade() from 85xx into  
cpm2_pic.c/h

- kumar

  reply	other threads:[~2007-01-24 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 19:19 [PATCH 0/3] 8560 && 8272 CPM-related fixes resubmit Vitaly Bordug
2007-01-24 19:19 ` [PATCH 1/3] POWERPC] cpm2: CPM2 interrupt controller fix Vitaly Bordug
2007-01-24 21:56   ` Kumar Gala [this message]
2007-01-24 19:19 ` [PATCH 2/3] [POWERPC] Fix kernel build errors for mpc8272ads and mpc8560ads Vitaly Bordug
2007-01-24 19:19 ` [PATCH 3/3] [POWERPC] mpc8272ads: defconfig Vitaly Bordug
  -- strict thread matches above, loose matches on Subject: below --
2007-01-30 23:08 [PATCH 0/3] 8560 && 8272 fixes resubmit Vitaly Bordug
2007-01-30 23:08 ` [PATCH 1/3] POWERPC] cpm2: CPM2 interrupt controller fix Vitaly Bordug
2007-01-31  4:50 Vitaly Bordug

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=75A90F7F-60B5-45CC-ACEB-109672475283@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=vbordug@ru.mvista.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;
as well as URLs for NNTP newsgroup(s).