On Tue, Aug 9, 2011 at 3:24 AM, Grant Likely<grant.likely@xxxxxxxxxxxx> wrote:If we add this API - the remaining gpio controls like drive strength and function select could also be added, which eats into the pinmux domain.On Mon, Aug 8, 2011 at 2:15 AM, Paul Mundt<lethal@xxxxxxxxxxxx> wrote:If gpiolib accept the pullup control. gpiolib is better place toOn Sun, Aug 07, 2011 at 10:19:33PM -0700, Barry Song wrote:I think I'm okay with this API change. Linus, what say you? How doesNow there are many different implementations for GPIO pull configuration, forFor arch/arm/mach-shmobile we also have gpio_pull_up() for board-g4evm.c
example:
s3c_gpio_setpull()
tegra_pinmux_set_pullupdown()
chipcHw_setPinPullup()
gpio_pullup()
s3c2410_gpio_pullup()
This patch adds a new generic gpio_set_pull API so that all SoCs can have unified
codes.
Signed-off-by: Barry Song<Baohua.Song@xxxxxxx>
and gpio_pull_down() for board-mackerel.c. Both of these would benefit
from this sort of an API addition.
this interact with your plans for pinctrl?
control gpio config.
then remains are the gpio driver strength, and power down mode
control. powerdown pull-up/down, powerdown in/out at samsung gpios.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/