Messages in this thread | | | Date | Mon, 9 Jun 2008 17:54:42 +0100 | From | Mark Brown <> | Subject | Re: [RFC] generic GPIO parameter API |
| |
On Mon, Jun 09, 2008 at 06:23:50PM +0200, Guennadi Liakhovetski wrote: > On Thu, 5 Jun 2008, David Brownell wrote: > > On Monday 02 June 2008, Guennadi Liakhovetski wrote:
> > > as far as I understand, the current GPIO API only presents very basic GPIO > > > functionality: direction and level reading and writing. Whereas many GPIO > > > controllers have many further configurable parameters: pull-ups and > > > pull-downs, drive strength, slew rate, etc.
> > Not at all how I'd describe it. Those omitted mechanisms are part > > of pin configuration, in the same way as function multiplexing is. > > (That is, assigning a given pin for use as a GPIO, vs hooking it up > > to an I2C, MMC, SPI, LCD, I2S, or memory controller.)
> Yes, on the one hand you're right, this belongs to pin-configuration. But, > otoh, will anyone ever want to change these parameters on non-generic > pins? And should this be allowed? Whereas for GPIOs it clearly makes a
They do get configured like that - for example, most I2S devices are able to operate as both clock masters and clock slaves. Often this accomplished (at least in part) by configuring the relevant pins as inputs or outputs.
| |