From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Ethernet issue in most recent git?
Date: Thu, 19 Jan 2006 15:21:24 -0800 [thread overview]
Message-ID: <20060119232124.GQ4425@atomide.com> (raw)
In-Reply-To: <20060119215802.GN4425@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 478 bytes --]
* Tony Lindgren <tony@atomide.com> [060119 14:08]:
> * Dirk Behme <dirk.behme@de.bosch.com> [060119 12:13]:
> >
> > the meaning of __IRQT_RISEDGE and __IRQT_FALEDGE was inverted :( So I
> > think we have to exchange _all_ places in OMAP code where these are used?
>
> We should be able to just remap them in gpio.c. I believe there's a note
> there somewhere saying that by coincidence the bits are the same in omap
> hw as in irq.h...
I'll push the following patch today:
[-- Attachment #2: patch-gpio-irqtype --]
[-- Type: text/plain, Size: 697 bytes --]
diff --git a/arch/arm/plat-omap/gpio.c b/arch/arm/plat-omap/gpio.c
index efba093..cf5ad29 100644
--- a/arch/arm/plat-omap/gpio.c
+++ b/arch/arm/plat-omap/gpio.c
@@ -448,11 +448,14 @@ static int _set_gpio_triggering(struct g
/* We allow only edge triggering, i.e. two lowest bits */
if (trigger & ~IRQT_BOTHEDGE)
BUG();
- /* NOTE: knows __IRQT_{FAL,RIS}EDGE match OMAP hardware */
- trigger &= 0x03;
l = __raw_readl(reg);
l &= ~(3 << (gpio << 1));
- l |= trigger << (gpio << 1);
+ if (trigger == IRQT_RISING)
+ l |= 2 << gpio;
+ else if (trigger == IRQT_FALLING)
+ l |= 1 << gpio;
+ else
+ goto bad;
break;
case METHOD_GPIO_730:
reg += OMAP730_GPIO_INT_CONTROL;
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2006-01-19 23:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 17:49 Ethernet issue in most recent git? Dirk Behme
2006-01-19 18:11 ` Anderson Briglia
2006-01-19 19:48 ` Tony Lindgren
2006-01-19 18:12 ` Tony Lindgren
2006-01-19 20:12 ` Dirk Behme
2006-01-19 21:58 ` Tony Lindgren
2006-01-19 23:21 ` Tony Lindgren [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=20060119232124.GQ4425@atomide.com \
--to=tony@atomide.com \
--cc=dirk.behme@de.bosch.com \
--cc=linux-omap-open-source@linux.omap.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.