• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 556 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

GPIO problem

kiran babu
Intellectual 265 points

Other Parts Discussed in Thread: 4460

Hi ,

          I am  using omap 4460 custom board with android ics kernel ( version 3.0.8) running on it. I want to use the NFC chip pn544. I was interfacing with the chip using i2c  bus. I had build the kernel image with PN544 enabled as module and run on target. I got the following errors :

[1] I got issue with the Regulator_bulk_get section in kernel

[2] the slave address for pn544 was having dependency on two address selection gpio pins. I had enabled them as gpio , direction input and PULL down mode.

    but the gpio enabling failed.

please find the error logs for the above two issues

[1]

[   47.546630] pn544 3-0051: Failed to get supply 'Vdd_IO': -19

[2]

omap_mux_init_gpio: Multiple gpio paths (2) for gpio104
[    0.592895] omap_mux_init_gpio: Could not set gpio104

Also in uboot prompt when i do probe for i2c bus i could not get my device listed in i2c bus.

From the error no -19 it appears that the kernel could not find any such device. But i am not sure what is the reason for that.

can any one tell me what could have went wrong and how to power up the pn544 device.

Thanks in advance,

Kiran.

_omap_mux_init_gpio: Multiple gpio paths (2) for gpio104

  • 0
    TI__Expert 6655 points

    Hi Kiran,

    The error you are seeing because the same gpio_104 functionality can be configured from multiple pins

    Better use omap_mux_init_signal() function instead of omap_mux_init_gpio()

    Ex: omap_mux_init_signal("gpmc_ncs7.gpio_104", OMAP_PIN_INPUT_PULLDOWN);  or other gpio_104 pin

    Regards

    AnilKumar

    Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!

  • 0 in reply to Anil
    Intellectual 265 points

    Hai Anil,

    Thanks for the reply. Changing the function to omap_mux_init_signal() has worked for me.

    Thanks a lot dude.