All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cantu Castillo, Arturo" <x0052731@ti.com>
To: Ram <vshrirama@gmail.com>, linux-omap-open-source@linux.omap.com
Subject: RE: I2C TWL4030 Keypad
Date: Mon, 26 Feb 2007 11:38:20 -0600	[thread overview]
Message-ID: <92E11BE23103564EAC7068F3C9EAEE7C056FF268@dlee05.ent.ti.com> (raw)
In-Reply-To: <8bf247760702160325m6624817bpbced2b76db9ae30a@mail.gmail.com>

Hi Ram,
It might be happening that when the driver is initialized the i2c
writing to TWL4030_MODULE_KEYPAD register that is done to enable
interrupts is failing (since you are saying that i2c readings/writings
are failing randomly it is likely), you can try to read this register
and find out if the interrupts are enable.

Also you can check that all the registers that are set in the
initialization routine have the proper value, if i2c writings are
failing randomly, some of them might not be initialized correctly.

Regards,
Arturo
-----Original Message-----
From: linux-omap-open-source-bounces+x0052731=ti.com@linux.omap.com
[mailto:linux-omap-open-source-bounces+x0052731=ti.com@linux.omap.com]
On Behalf Of Ram
Sent: Friday, February 16, 2007 5:25 AM
To: linux-omap-open-source@linux.omap.com
Subject: I2C TWL4030 Keypad

Hi,
   Im using omap2430 SDP.
   Im trying to get TWL4030 Keypad to work on 2.6.19. Im using 2.6.14
for
omap2430 as a reference.

   Im using the following files:
        1) i2c-omap.c which exists on 2.6.19
        2) twl4030_core.c
        3) twl4030_gpio.c (taken from 2.6.14)
        4) omap-twl4030keypad.c (taken from 2.6.14)

   made  changes  to support generic interrupts in 2.6.19.

   Im able to read the value of registers using  twl4030_kpread_u8
    TWL4030_MODULE_KEYPAD, REG_KEYP_EDR, REG_LK_PTV_REG,
REG_KEY_DEB_REG,
REG_LONG_KEY_REG1, REG_KEYP_SIH_CTRL, REG_KEYP_IMR1

  However, im not able to recieve interrupts. upon pressing keys in
keypad.
i dont observe
  any change in interrupts count. when i do a cat /proc/interrupts.

Im not sure if im missing something.


  I also observe randomly (say 3 out of 10 times), my i2c bus times out
and
im unable to read or write TWL4030 registers. i get an return value of
-110.

i2c_omap i2c_omap.2: timeout waiting for bus ready

Please Advice,

Regards,
sriram
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source

  parent reply	other threads:[~2007-02-26 17:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 11:25 I2C TWL4030 Keypad Ram
2007-02-16 14:31 ` G, Manjunath Kondaiah
     [not found]   ` <8bf247760702160650s62d2b401lad8746881aedd2aa@mail.gmail.com>
2007-02-16 15:08     ` Ram
2007-02-16 15:38       ` Syed Mohammed, Khasim
2007-02-17 13:45 ` Nishanth Menon
     [not found]   ` <8bf247760702170604h5b2e210cibe4de58d4f898d74@mail.gmail.com>
2007-02-17 14:08     ` Nishanth Menon
2007-02-18  8:00       ` Setting the default state (high or low) of a pin zil iram
2007-02-26 17:38 ` Cantu Castillo, Arturo [this message]
2007-02-27  6:20   ` I2C TWL4030 Keypad Ram
2007-02-27 15:09     ` Syed Mohammed, Khasim
2007-02-28  1:00     ` Syed Mohammed, Khasim
2007-02-28  1:02 Syed Mohammed, Khasim
2007-02-28  1:05 Syed Mohammed, Khasim

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=92E11BE23103564EAC7068F3C9EAEE7C056FF268@dlee05.ent.ti.com \
    --to=x0052731@ti.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=vshrirama@gmail.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.