Grant Likely wrote: > Correct. IRQ2 can only be used as IRQ2. It cannot be used a GPIO. > (Well, I suppose you *could* try to hack into the interrupt controller > driver and fetch the pin state that way; but I don't know if you can > read the state of masked out IRQ pins, and it sure would be ugly.) >
Actually, I did think of a way you could do this. You could register an interrupt handler on the line, and set the irq type to level-low or level-high. Depending on whether the handler fires right away, you know what the state of the pin must be. And when the interrupt handler does fire, you switch the irq type to the opposite setting. I think that approach rates pretty high on the "ugly scale" too, but perhaps tolerably so. In fact, were I to actually need to interface one of the IRQ lines to gpiolib, I might attempt this... b.g. -- Bill Gatliff Embedded systems training and consulting http://billgatliff.com b...@billgatliff.com _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
