On Wed, May 13, 2015 at 4:25 AM, Feng Kan <fkan@xxxxxxx> wrote: > Marc: > > Sorry for top posting. It seems with GIC-400, the get_irqstate is not a reliable > way of accessing the GPIO status. In our case, the gpio interrupt status can > only be read correctly with the SPISR register. So it seems we have to go > back to the old way of mapping the SPISR portion of the GIC in our GPIO > driver. We wanted to ask you if that is acceptable since SPISR in not > standard in all GIC, perhaps we can treat it differently. As GPIO maintainer I am curious about what this is... Can you describe the scenario where your GPIO (!) driver needs to be poking around in the GIC SPISR? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
