Mark Brown wrote: > On Tue, Jan 18, 2011 at 04:37:36PM -0700, Stephen Warren wrote: > > > a) Is this the right way to expose GPIO APIs from a codec? The tlv320aic3 > > seems to do it this way, but wm8962.c uses the generic GPIO API. I shied > > away from the latter, since I wasn't sure how to name the WM8903's GPIOs > > in the gpio_* calls. I suppose it'd need a bunch of GPIO driver platform > > data to hook it all together and name GPIOs from a mach-tegra/include > > header file, but if this is the way to go, I need to read up on that more. > > What naming is required for the GPIOs? GPIOs are referred to by number > in Linux. Naming/numbering mean the same thing to me; I have to pass a number to gpio_request/gpio_set_value, either by hard-coded number or name (i.e. #define referring to some number). I'll go read up on gpiolib some more to see how those API-level numbers get mapped to a specific controller and GPIO number. -- nvpublic -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
