mirror of
https://github.com/torvalds/linux.git
synced 2024-12-27 13:22:23 +00:00
cf9d052aa6
In Linux, if a driver does disable_irq() and later does enable_irq() on its interrupt, I believe it's expecting these properties: * If an interrupt was pending when the driver disabled then it will still be pending after the driver re-enables. * If an edge-triggered interrupt comes in while an interrupt is disabled it should assert when the interrupt is re-enabled. If you think that the above sounds a lot like the disable_irq() and enable_irq() are supposed to be masking/unmasking the interrupt instead of disabling/enabling it then you've made an astute observation. Specifically when talking about interrupts, "mask" usually means to stop posting interrupts but keep tracking them and "disable" means to fully shut off interrupt detection. It's unfortunate that this is so confusing, but presumably this is all the way it is for historical reasons. Perhaps more confusing than the above is that, even though clients of IRQs themselves don't have a way to request mask/unmask vs. disable/enable calls, IRQ chips themselves can implement both. ...and yet more confusing is that if an IRQ chip implements disable/enable then they will be called when a client driver calls disable_irq() / enable_irq(). It does feel like some of the above could be cleared up. However, without any other core interrupt changes it should be clear that when an IRQ chip gets a request to "disable" an IRQ that it has to treat it like a mask of that IRQ. In any case, after that long interlude you can see that the "unmask and clear" can break things. Maulik tried to fix it so that we no longer did "unmask and clear" in commit |
||
|---|---|---|
| .. | ||
| actions | ||
| aspeed | ||
| bcm | ||
| berlin | ||
| cirrus | ||
| freescale | ||
| intel | ||
| mediatek | ||
| meson | ||
| mvebu | ||
| nomadik | ||
| nuvoton | ||
| pxa | ||
| qcom | ||
| ralink | ||
| renesas | ||
| samsung | ||
| sirf | ||
| spear | ||
| sprd | ||
| stm32 | ||
| sunxi | ||
| tegra | ||
| ti | ||
| uniphier | ||
| visconti | ||
| vt8500 | ||
| zte | ||
| core.c | ||
| core.h | ||
| devicetree.c | ||
| devicetree.h | ||
| Kconfig | ||
| Makefile | ||
| pinconf-generic.c | ||
| pinconf.c | ||
| pinconf.h | ||
| pinctrl-amd.c | ||
| pinctrl-amd.h | ||
| pinctrl-artpec6.c | ||
| pinctrl-as3722.c | ||
| pinctrl-at91-pio4.c | ||
| pinctrl-at91.c | ||
| pinctrl-at91.h | ||
| pinctrl-axp209.c | ||
| pinctrl-bm1880.c | ||
| pinctrl-coh901.c | ||
| pinctrl-coh901.h | ||
| pinctrl-da850-pupd.c | ||
| pinctrl-da9062.c | ||
| pinctrl-digicolor.c | ||
| pinctrl-equilibrium.c | ||
| pinctrl-equilibrium.h | ||
| pinctrl-falcon.c | ||
| pinctrl-gemini.c | ||
| pinctrl-ingenic.c | ||
| pinctrl-lantiq.c | ||
| pinctrl-lantiq.h | ||
| pinctrl-lpc18xx.c | ||
| pinctrl-max77620.c | ||
| pinctrl-mcp23s08_i2c.c | ||
| pinctrl-mcp23s08_spi.c | ||
| pinctrl-mcp23s08.c | ||
| pinctrl-mcp23s08.h | ||
| pinctrl-microchip-sgpio.c | ||
| pinctrl-ocelot.c | ||
| pinctrl-oxnas.c | ||
| pinctrl-palmas.c | ||
| pinctrl-pic32.c | ||
| pinctrl-pic32.h | ||
| pinctrl-pistachio.c | ||
| pinctrl-rk805.c | ||
| pinctrl-rockchip.c | ||
| pinctrl-single.c | ||
| pinctrl-st.c | ||
| pinctrl-stmfx.c | ||
| pinctrl-sx150x.c | ||
| pinctrl-tb10x.c | ||
| pinctrl-u300.c | ||
| pinctrl-utils.c | ||
| pinctrl-utils.h | ||
| pinctrl-xway.c | ||
| pinctrl-zynq.c | ||
| pinmux.c | ||
| pinmux.h | ||