Openmoko Bug #2185: AUX button makes interrupt storm
Openmoko Public Trac
bugs at docs.openmoko.org
Mon Dec 22 19:26:21 CET 2008
#2185: AUX button makes interrupt storm
---------------------+------------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.9-dev
Severity: normal | Keywords: AUX button interrupts
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
---------------------+------------------------------------------------------
Comment(by arhuaco):
Replying to [comment:10 vnevoa]:
> Oops, sorry, I only looked at the /proc/interrupts output.
Yes, you will still get the IRQ storm there... the idea is to filter it.
> Now I'm looking at the kernel messages.
>
> When I press the AUX button, I get only 1 message:
> "IRQ press:0"
> When I release the button, I get 2 messages:
> "IRQ press:0"
> "IRQ press:1"
Ok. This device is asking for a state. I will program something better
now... I think it is not hard to solve this.
In the mean time it will help us a lot if you test another image. It will
print
every IRQ. I didn't make 2 images but one image and 2 modules. You will
get a warning
when you remove the modules, I haven't researched that issue yet (it is
not fatal but it needs to be fixed).
You will need to disable suspend in your distro (using the GUI I guess).
This time we want to know the timings of the interrupts in order to tune
the filter. I'm sending 2 modules. One of them has the pulldown, let's see
if it makes a noticeable difference for you.
The idea is that for each module, you try this:
1) insert module.
2) press and release the button fast
3) wait about 1 second
please repeat 2 and 3 about 10 times.
4) remove the module
5) Do a "dmesg > module1" or "dmesg > module2"....
Then send us the dumps...
Please download from: http://wiki.emqbit.com/tmp/test2.tar
MD5SUMS:
840672c60dbd29cb98b58653aac75d6f module1.ko
224406385ed557181a6da4bfca152a49 module2.ko
0d4bec316e8c70d6bb9f561239ea0fcc uImage-moredrivers-GTA02_andy-
tracking_1c16df7be9a83288.bin
> Now I see the Power button also behaves strangely, I think.
> I press Power, and I get 3 kernel messages:
> "INT1=0x80 INT2=0x02 INT3=0x00 INT4=0x00 INT5=0x00"
> "INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00"
> "INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00"
> I release it, and I get another 3:
> "INT1=0x00 INT2=0x01 INT3=0x00 INT4=0x00 INT5=0x00"
> "INT1=0x00 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00"
> "INT1=0x80 INT2=0x00 INT3=0x00 INT4=0x00 INT5=0x00"
> Is this supposed to happen?
I do not know... I will focus on the problem of the ticket first...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2185#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list