On Wed 31 Dec 2008 13:05, Jaya Kumar pondered: > On Thu, Jan 1, 2009 at 1:38 AM, Robin Getz <rgetz@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Tue 30 Dec 2008 23:58, Jaya Kumar pondered: > >> On Tue, Dec 30, 2008 at 11:55 PM, Robin Getz <rgetz@xxxxxxxxxxxxxxxxxxxx> wrote: > >> > Yeah, I hadn't thought about spanning more than one gpio_chip. That's a good > >> > point. > >> > >> The currently posted code already supports spanning more than one gpio_chip. > >> > > > > But doesn't do all the other things that David suggested/requested. > > Hi Robin, > > Yes, you are right. My implementation does not support a driver that > needs to set/get more than 32-bits of gpio in a single call. I'm okay > with that restriction as I don't see a concrete use case for that. It's not the more than 32-bits that I'm concerned about - it is spanning more than one register. (if all the GPIOs that are left on the board are 2, 64, and 128, where 2, and 64 are part of the SOC's GPIO, and 128 is on a GPIO expander - which is a common use case - is this handled?) -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
