Following this are four patches matching $SUBJECT:
- remove omap_set_gpio_dataout() and omap_get_gpio_datain()
... same call syntax, different name, minor code shrink
- use gpio_direction_input()
... minor call syntax change, otherwise not interesting
- use gpio_direction_output(), remove omap_set_gpio_direction()
... different call syntax and initialization model
- use gpio_to_irq()
... at least, outside of static initializers
The third patch might conceivably make trouble; see the patch
comments. Ditto the fourth, but IMO that's less likely.
I did test builds for OMAP1, OMAP2420, OMAP2430, and OMAP3430,
and tried to make sure all the files affected by this patch
got rebuilt. The build breakage was mostly related to McBSP
and iomem pointers; nothing affected by these patches.
Two remaining OMAP GPIO calls can be removed a bit later:
int omap_request_gpio(int gpio);
void omap_free_gpio(int gpio);
Once that's done, I think it'll be time to move the GPIO
code into mach-omap1/mach-omap2 ... the OMAP2/OMAP3 stuff
in particular should become a LOT simpler.
- Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
