From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lixom.net (lixom.net [66.141.50.11]) by ozlabs.org (Postfix) with ESMTP id 84DAADE1F8 for ; Sat, 5 Apr 2008 06:29:50 +1100 (EST) Date: Fri, 4 Apr 2008 14:39:42 -0500 From: Olof Johansson To: Segher Boessenkool Subject: Re: [PATCH] PowerPC: MPIC ack interrupts at mpic_teardown_this_cpu() Message-ID: <20080404193942.GA27748@lixom.net> References: <20080403190943.GA16446@ru.mvista.com> <1207259436.10388.337.camel@pasglop> <20080404052955.GC11799@lixom.net> <9d19fecb0ef172995b7ce3a317ee3c0d@kernel.crashing.org> <20080404180333.GB26693@lixom.net> <63defd942bd57ca87cb17334832b615c@kernel.crashing.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <63defd942bd57ca87cb17334832b615c@kernel.crashing.org> Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Apr 04, 2008 at 08:55:01PM +0200, Segher Boessenkool wrote: >>> platforms/maple/setup.c and platforms/powermac/pic.c use >>> MPIC_WANTS_RESET. >>> Is there a reason why we don't do that on every MPIC? If there is >>> such >>> a reason, the default should be to reset, only pseries and chrp and >>> cell >>> and now pasemi do not use it. It's the only sane way to get an MPIC >>> into >>> a sane known state starting from state. >> >> I used to have the reset there on pasemi but due to some other issues I >> ended up taking it out. >> >> It's not like doing a final EOI is a big deal, I really don't see why >> there's hassle about this patch. > > The patch is fine, don't get me wrong. I'm just saying MPIC_WANTS_RESET > should be the default since pretty much everything wants it. The few > platforms that don't can document why; with the current code, we cannot > see if you just forgot it or not. It was documented in the changeset, see de0c74e7f98d8a06b784e120103eb388da8194f6. But yeah, that's hard to tell at some point later in time, a short comment by the call could be useful. I'll add one next time I touch that code. -Olof