2011/9/7 Barry Song <[email protected]>: >> - /* Enable or disable the internal pull-ups in the GPIO ASIC block */ >> - for (i = 0; i < U300_GPIO_MAX; i++) { >> - val = 0; >> - for (j = 0; j < 8; j++) >> - val |= (u32)((u300_gpio_config[i][j].pull_up == >> DISABLE_PULL_UP) << j); >> - local_irq_save(flags); >> - writel(val, virtbase + U300_GPIO_PXPER + i * >> U300_GPIO_PORTX_SPACING); >> - local_irq_restore(flags); > > this has used array/table to set the pull of gpio. so what's our plan > about api to config GPIO pull dynamically?
My plan is as follows: 1) Introduce the pin control subsystem, support pinmux in it to begin with 2) Add support for biasing and driving (etc) through pin control 3) Move the driver over to drivers/pinctrl, have it register both a pin control and a GPIO interface as well Sounds OK? Yours, Linus Walleij -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/caknu2mpkw5ynpqxziogsbqqitobbe51vcdbw-8aroervcte...@mail.gmail.com
