linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Miao <eric.y.miao@gmail.com>
To: Jebediah Huang <jebediah.huang@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-input@vger.kernel.org
Subject: Re: Using PXA arm board with MAX7319 GPIO expander input
Date: Mon, 8 Feb 2010 14:02:20 +0800	[thread overview]
Message-ID: <f17812d71002072202x2fb620c3hf4c3bbf6dc78aa78@mail.gmail.com> (raw)
In-Reply-To: <bf0eec9a1002072144n461e5894m8993bfd4e8f49e9b@mail.gmail.com>

On Mon, Feb 8, 2010 at 1:44 PM, Jebediah Huang <jebediah.huang@gmail.com> wrote:
> Hello ,
>
> I have PXA166 board with MAX7319 GPIO expander connected with 8
> buttons. When any button is pressed, I want to get input event. Can
> this be done?
>
> I have read the littleton and aspenite code to try. The SDA is 105,
> SCL is 106. I use MAX732x driver. It is set as I2C slave at 0x6C. So I
> set up:
>
> static struct i2c_pxa_platform_data pwri2c_info __initdata = {
>        .use_pio                = 1,
> };
>
> static unsigned long peony_pin_config[] __initdata = {
>        /* i2c bus */
>        GPIO105_CI2C_SDA,
>        GPIO106_CI2C_SCL,
> }
>
> static struct max732x_platform_data max7319_data[] = {
>        [0] = {
>                .gpio_base      = GPIO_EXT0(0),
>        },
> };
>
> static struct i2c_board_info i2c_board_info[] =
> {
>        {
>                .type           = "max7319",
>                .addr           = 0x6C,
>                .irq            = IRQ_GPIO(105),

This doesn't look correct, if max7319 is ever able to interrupt the host
CPU, this should be something other than SDA.

However, this isn't supposed to be the reason for the failure. The
failure looks like an I2C communication issue to me, which means:

1. the i2c host driver isn't setup correctly
2. pin setup
3. max7319 power supply and chip select
4. i2c bus (incorrect pull-up/down etc)
5. i2c device address

I'd recommend an oscilloscope/LA for the I2C protocol on the lines
to identify the real issue.

>                .platform_data  = &max7319_data[0],
>        },
> };
>
> when bootup I see;
> <6>[    0.290770] I2C: i2c-0: PXA I2C adapter
> <6>[    0.307118] I2C: i2c-1: PXA I2C adapter
> <6>[    0.821709] hello pony_init
> <3>[    0.838559] platform_driver_register
> <6>[    0.868069] max732x_read: read g 1
> <6>[    0.881893] max732x_read: read g 0
> <4>[    0.898895] i2c: error: exhausted retries
> <4>[    0.911947] i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
> <4>[    0.927509] i2c: ICR: 000007e0 ISR: 00000002
> <4>[    0.927526] i2c: log: [00000006:00000000] [00000006:00000000]
> [00000006:00000000] [00000006:00000000] [00000006:00000000]
> [00000006:00000000] [0000000
> <3>[    1.167890] dummy 0-005d: failed reading
> <5>[    1.182585] SCSI subsystem initialized
>
> Maybe max732x driver is not getting correct data from my setup? No
> event when pressing button. If any ideas?
>
> Thank you very much!
> Jeb
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-02-08  6:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-08  5:44 Using PXA arm board with MAX7319 GPIO expander input Jebediah Huang
2010-02-08  6:02 ` Eric Miao [this message]
2010-02-08  7:02   ` Jebediah Huang
2010-02-08  7:36     ` Daniel Mack
2010-02-08  7:56       ` Jebediah Huang
2010-02-08 11:08     ` Jebediah Huang
2010-02-08 11:33       ` Daniel Mack
2010-02-08 12:32         ` Marc Zyngier
2010-02-08 13:04           ` Daniel Mack
2010-02-09  1:05           ` Eric Miao
2010-02-09  7:39             ` Marc Zyngier
2010-02-09  8:19               ` Eric Miao
2010-02-09 10:22                 ` Marc Zyngier
2010-02-09  1:07 ` Eric Miao

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=f17812d71002072202x2fb620c3hf4c3bbf6dc78aa78@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=jebediah.huang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).