> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Premi, Sanjeev > Sent: Wednesday, March 04, 2009 9:12 PM > To: linux-omap@xxxxxxxxxxxxxxx > Subject: Setting individual GPIO registers > > I am trying to get the wakeup event from touchscreen on > omap3evm to bring the EVM out of suspend state. > > For my private testing, I have been updating individual > registers & bits in the GPIO registers from function > ads7846_dev_init(). > > Ideally, I should be using standard GPIO APIs. However, > most of the APIs are static within gpio.c > > How can I call functions like gpio_wake_enable(), gpio_unmask_irq() > OR > Is there a function to access interface registers for GPIO banks? > Did you mean waking up OMAP3 via touch screen from CORE OFF mode ? Please note that PER domain GPIOs will be not be active during OFF mode (GPIO2-6). Wakeup capability is limited for wakeup domain GPIOs as well. >From TRM "Only gpio_1, gpio_9, gpio_10, gpio_11, gpio_30 and gpio_31 can be used to generate a direct wakeup event. The other GPIO1 pins cannot be used to generate a direct wake-up event because they are connected to the device I/O pad logic in the CORE power domain (VDD2). When the CORE power domain is off, the VDD2-supplied I/O pins of the GPIO1 module cannot generate a wake-up event" Enable wakeup in I/O PAD corresponding to TS_IRQ line. On wakeup you will get a PRCM interrupt. Regards, Pratheesh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
