From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH] ARM: OMAP: Fix ethernet IRQF_TRIGGER flag for apollon Date: Thu, 21 Dec 2006 15:29:57 -0800 Message-ID: <20061221232957.GL10399@atomide.com> References: <20061221215755.GE10399@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces@linux.omap.com Errors-To: linux-omap-open-source-bounces@linux.omap.com To: "Woodruff, Richard" , "kyungmin.park" Cc: linux-omap-open-source@linux.omap.com List-Id: linux-omap@vger.kernel.org * Woodruff, Richard [061221 14:25]: > > > > AFAIK we _should_ be able to use level GPIO interrupts on all omap2 > > systems. I wonder why that does not work on apollon? Is there some > > difference in hardware, or maybe some GPIO lines don't support level > > interrupts on omap2? > > The OMAP GPIOs can trigger on edges or levels. > > That seems likely a board level issue. The Ethernet interrupt from the > raw SMC chip is level assertive. Depending on the SMC bus hook up mode > its either active high or low through a smc-push-pull output buffer. > > On the TI-SDP platforms this signal goes into an FPGA which depending on > the SDP may or may not invert the signal. It seems over time depending > on the SDP a pull-up may have been necessary on the FPGA to OMAP-GPIO > side when hooked to an open drain fpga output. > > At any rate omap-gpios should be ok. The issue is likely with the smc > to omap path at the board level. Yeah, I believe the omap level gpios should work fine too. Kyungmin, do you have some special interrupt routing for your smc91x? Or do you see this only with the RT patches applied? Regards, Tony