On Thursday 25 September 2008, Kevin Hilman wrote: > > >> In that case, what is the proposed method for other kernel code to use > >> the debobs lines? > > > > Hmm, good point :) My idea was to use the gpiolib calls on GPIO12 - > > GPIO29, but then there is no way for a user to know if the GPIO was > > assigned to debobs or not... Maybe debobs should register as gpiolib > > 'chip' and reexport those lines ? Would that make sense ? > > I think debobs should simply 'gpio_export' each pin. It does not need > to hold them. Peter said the right abstraction here was pads (pins/balls?) not GPIOs, so I'm not sure this is relevant any more, but ... You can't gpio_export() to userspace, via sysfs, without having first done a gpio_request(). And then later a gpio_free() will release that export. So that won't work. - Dave -- 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
