1. 21 3月, 2016 2 次提交
  2. 11 3月, 2016 1 次提交
  3. 10 3月, 2016 2 次提交
  4. 09 3月, 2016 8 次提交
  5. 25 2月, 2016 6 次提交
  6. 19 2月, 2016 2 次提交
  7. 18 2月, 2016 6 次提交
  8. 17 2月, 2016 8 次提交
  9. 12 2月, 2016 1 次提交
    • A
      irqchip/gic-v3-its: Fix double ICC_EOIR write for LPI in EOImode==1 · 004fa08d
      Ashok Kumar 提交于
      When the GIC is using EOImode==1, the EOI is done immediately,
      leaving the deactivation to be performed when the EOI was
      previously done.
      
      Unfortunately, the ITS is not aware of the EOImode at all, and
      blindly EOIs the interrupt again. On most systems, this is ignored
      (despite being a programming error), but some others do raise a
      SError exception as there is no priority drop to perform for this
      interrupt.
      
      The fix is to stop trying to be clever, and always call into the
      underlying GIC to perform the right access, irrespective of the
      more we're in.
      
      [Marc: Reworked commit message]
      
      Fixes: 0b996fd3 ("irqchip/GICv3: Convert to EOImode == 1")
      Cc: stable@vger.kernel.org
      Acked-by: NMarc Zyngier <marc.zyngier@arm.com>
      Signed-off-by: NAshok Kumar <ashoks@broadcom.com>
      Signed-off-by: NMarc Zyngier <marc.zyngier@arm.com>
      004fa08d
  10. 11 2月, 2016 2 次提交
  11. 08 2月, 2016 2 次提交