[...] > From this patch it seems that the GPIO module is kept active as long as > one of its GPIOs is requested. This is not optimal. Yes, but... > > The GPIO needs to be active only when accessing its registers e.g. > during gpio_get or gpio_set. The rest of the time it can be suspended. A GPIO module would typically be used by multiple client drivers. However, the clock control is common for all GPIO pins within the module. So clocks can't be turned-off/on without negatively impacting present users. Instead, client drivers have to ensure that they free GPIO pin(s) after use. This would make power savings optimal. -- Tarun > > cheers, > -roger [...] -- 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
