On Fri, 2018-06-22 at 12:04 +1000, Benjamin Herrenschmidt wrote: > On the Aspeed chip, the GPIOs can be under control of the ARM > chip or of the ColdFire coprocessor. (There's a third command > source, the LPC bus, which we don't use or support yet). At the risk of offending people even more, I'm going to respin this with another extra Aspeed specific interface to retrieve a given GPIO registers and bit number. So far, I've made the corprocessor code system specific, effectively hard wiring in the binary the above. But I found a way to make it more flexible without losing too much performance, thus drastically simplifying deployment for us since every machine out there seems to be wiring these things differently. However, for that to work, after "grabbing" the GPIOs, the coprocessor driver will need to give the data and write data latch registers and bit numbers to the microcode. I'll respin a v4 with that added interface in the form of a separate patch at the end of the series. Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html