diff options
author | Luka Perkov <luka@openwrt.org> | 2014-06-29 23:29:57 +0000 |
---|---|---|
committer | Luka Perkov <luka@openwrt.org> | 2014-06-29 23:29:57 +0000 |
commit | 2397978836e003e55cd5a66d4025efc262467a79 (patch) | |
tree | b3616bb4a167d8e900e0b04f44eab8f1760a6815 /target/linux/mvebu/patches-3.10/0086-irqchip-armada-370-xp-fix-MSI-race-condition.patch | |
parent | ba967cd842e5d7425d6cc4e7e1584b7f000a5d86 (diff) | |
download | master-187ad058-2397978836e003e55cd5a66d4025efc262467a79.tar.gz master-187ad058-2397978836e003e55cd5a66d4025efc262467a79.tar.bz2 master-187ad058-2397978836e003e55cd5a66d4025efc262467a79.zip |
mvebu: drop 3.10 support
Signed-off-by: Luka Perkov <luka@openwrt.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@41406 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/mvebu/patches-3.10/0086-irqchip-armada-370-xp-fix-MSI-race-condition.patch')
-rw-r--r-- | target/linux/mvebu/patches-3.10/0086-irqchip-armada-370-xp-fix-MSI-race-condition.patch | 44 |
1 files changed, 0 insertions, 44 deletions
diff --git a/target/linux/mvebu/patches-3.10/0086-irqchip-armada-370-xp-fix-MSI-race-condition.patch b/target/linux/mvebu/patches-3.10/0086-irqchip-armada-370-xp-fix-MSI-race-condition.patch deleted file mode 100644 index ebbc532391..0000000000 --- a/target/linux/mvebu/patches-3.10/0086-irqchip-armada-370-xp-fix-MSI-race-condition.patch +++ /dev/null @@ -1,44 +0,0 @@ -From ddda6fa410b6e50ee67d4a628187e76b4a6c9b28 Mon Sep 17 00:00:00 2001 -From: Lior Amsalem <alior@marvell.com> -Date: Mon, 25 Nov 2013 17:26:45 +0100 -Subject: [PATCH 086/203] irqchip: armada-370-xp: fix MSI race condition - -In the Armada 370/XP driver, when we receive an IRQ 1, we read the -list of doorbells that caused the interrupt from register -ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS. This gives the list of MSIs that -were generated. However, instead of acknowledging only the MSIs that -were generated, we acknowledge *all* the MSIs, by writing -~MSI_DOORBELL_MASK in the ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS register. - -This creates a race condition: if a new MSI that isn't part of the -ones read into the temporary "msimask" variable is fired before we -acknowledge all MSIs, then we will simply loose it. - -It is important to mention that this ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS -register has the following behavior: "A CPU write of 0 clears the bits -in this field. A CPU write of 1 has no effect". This is what allows us -to simply write ~msimask to acknoledge the handled MSIs. - -Notice that the same problem is present in the IPI implementation, but -it is fixed as a separate patch, so that this IPI fix can be pushed to -older stable versions as appropriate (all the way to 3.8), while the -MSI code only appeared in 3.13. - -Signed-off-by: Lior Amsalem <alior@marvell.com> -Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> -Cc: Thomas Gleixner <tglx@linutronix.de> ---- - drivers/irqchip/irq-armada-370-xp.c | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - ---- a/drivers/irqchip/irq-armada-370-xp.c -+++ b/drivers/irqchip/irq-armada-370-xp.c -@@ -381,7 +381,7 @@ armada_370_xp_handle_irq(struct pt_regs - ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS) - & PCI_MSI_DOORBELL_MASK; - -- writel(~PCI_MSI_DOORBELL_MASK, per_cpu_int_base + -+ writel(~msimask, per_cpu_int_base + - ARMADA_370_XP_IN_DRBEL_CAUSE_OFFS); - - for (msinr = PCI_MSI_DOORBELL_START; |