From: badguy development <badguydevelopment-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
To: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: LTC1760, ISR Questions
Date: Thu, 3 Apr 2008 23:04:02 +0000 [thread overview]
Message-ID: <BLU106-W40B1D2DF94BBAC071ED2E2B0F70@phx.gbl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2551 bytes --]
Hello,
I am developing a driver for the LTC1760 dual battery charger.
I have an interrupt occur and I get notification of that.
however I cannot seem to clear the interrupt from inside the ISR and thus I am ruined.
I have learned from the research and looking around I have done, that I cannot call just any code in an ISR.
the code I want to call will read the AlertResponse register of my LTC1760 chip and that will clear the interrupt.
but I get angry kernel response when I do, below is a brief dump of what I get:
BUG: scheduling while atomic: swapper/0x00010002/0
bad: scheduling from the idle thread!
Unable to handle kernel NULL pointer dereference at virtual address 00000000
pgd = c0004000
[00000000] *pgd=00000000
Internal error: Oops: 17 [#1]
Modules linked in: i2c_battery swcamera(PF) clcdc(PF) pvr(PF) gecko_devices
CPU: 0
PC is at dequeue_task+0xc/0xa8
LR is at deactivate_task+0x38/0x44
pc : [<c009b070>] lr : [<c009b218>] Tainted: PF
sp : c0331c6c ip : c0331c80 fp : c0331c7c
r10: 00000000 r9 : 00989642 r8 : b0e7aa00
r7 : c0335f98 r6 : c0331cd8 r5 : 00000001 r4 : c0335f98
r3 : 00000080 r2 : 00000000 r1 : 00000000 r0 : c0335f98
Flags: Nzcv IRQs off FIQs on Mode SVC_32 Segment kernel
Control: C5387F
Table: 868E8000 DAC: 00000017
Process swapper (pid: 0, stack limit = 0xc0330250)
All the example code I can find regarding ISR, have access to register offsets and can simply clear the interrupt that way.
I am new to this and am having a hard time finding direction with regards to how to handle linux interrupts.
I need to send a request command out i2c to this device to clear this interrupt.
I am not 100% sure about this, but it is what the data sheet has led me to believe.
I would appreciate any help on this, and perhaps even a reference to what material I should look at to find this answer.
Thanks ahead of time.
Please CC me at badguydevelopment-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org
I am still trying to join the list.
P.S.
I accidently clicked send before filling out the Subject, so I scanned the maillist and did not find my message.
I think perhaps it was rejected due to no subject, if it was not, and I submitted two of them please accept my apologies.
-Christian Hunt
_________________________________________________________________
Try Chicktionary, a game that tests how many words you can form from the letters given. Find this and more puzzles at Live Search Games!
http://g.msn.ca/ca55/207
[-- Attachment #1.2: Type: text/html, Size: 2959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next reply other threads:[~2008-04-03 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 23:04 badguy development [this message]
[not found] ` <BLU106-W40B1D2DF94BBAC071ED2E2B0F70-MsuGFMq8XAE@public.gmane.org>
2008-04-09 10:04 ` LTC1760, ISR Questions Jean Delvare
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=BLU106-W40B1D2DF94BBAC071ED2E2B0F70@phx.gbl \
--to=badguydevelopment-pkbjnfxxiarbdgjk7y7tuq@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
/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