From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>,
"kyungmin.park" <kyungmin.park@samsung.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP: Fix ethernet IRQF_TRIGGER flag for apollon
Date: Thu, 21 Dec 2006 15:29:57 -0800 [thread overview]
Message-ID: <20061221232957.GL10399@atomide.com> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A5091AEA5B@dlee02.ent.ti.com>
* Woodruff, Richard <r-woodruff2@ti.com> [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
next prev parent reply other threads:[~2006-12-21 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 9:43 [PATCH] ARM: OMAP: Fix ethernet IRQF_TRIGGER flag for apollon Dirk Behme
2006-12-21 21:57 ` Tony Lindgren
2006-12-21 22:19 ` Syed Mohammed, Khasim
2006-12-21 22:24 ` Woodruff, Richard
2006-12-21 23:29 ` Tony Lindgren [this message]
2006-12-22 21:08 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 5:57 Kyungmin Park
2006-12-22 20:26 ` Tony Lindgren
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=20061221232957.GL10399@atomide.com \
--to=tony@atomide.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@ti.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