On Mon, 2011-05-30 at 15:01 +0800, Mark Brown wrote: > On Sun, May 29, 2011 at 08:18:09PM -1000, Mitch Bradley wrote: > > > I'm currently dealing with an SoC that has over a hundred GPIOs. > > Whatever we choose, I think it should be able to handle an insane > > number of GPIOs without getting any more cumbersome that is > > necessary. > > This is *consumer* side GPIOs, not bindings for the device providing the > GPIOs. If a single device needs to use hundreds of GPIOs I'd expect > many of them will be block functions so you'd have a binding with an > array for things like "databus" and "addrbus". Yes. Agreed. The producer remains identified by phandle/gpio#, so it's just a naming thing on the consumer side. So what are the options ? - gpio-xxxx = < ... > properties - existing binding, along with an optional gpio-names string list - anything else ? Cheers, Ben. -- 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
