Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753263AbbF3OO1 (ORCPT ); Tue, 30 Jun 2015 10:14:27 -0400 Received: from mail-wi0-f173.google.com ([209.85.212.173]:34037 "EHLO mail-wi0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751447AbbF3OOT (ORCPT ); Tue, 30 Jun 2015 10:14:19 -0400 From: Robert Richter To: Marc Zygnier Cc: Tirumalesh Chalamarla , Thomas Gleixner , Jason Cooper , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Robert Richter Subject: [PATCH 0/4] irqchip, gicv3: Implement Cavium ThunderX errata Date: Tue, 30 Jun 2015 16:13:59 +0200 Message-Id: <1435673643-31676-1-git-send-email-rric@kernel.org> X-Mailer: git-send-email 2.1.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1268 Lines: 31 From: Robert Richter This patch series implements workarounds for HW errata in Cavium's ThunderX GICV3. The first one is a gicv3 code update I sent a while ago and is a prerequisit for patch #4. Patch #2 adds generic code to parse the hw revision provided by an IIDR register value and runs specific code if hw matches. This is used to implement the actual errata fixes in patch #3 (gicv3) and #4 (gicv3-its). Robert Richter (4): irqchip, gicv3-its: Read typer register outside the loop irqchip, gicv3: Add HW revision detection and configuration irqchip, gicv3: Implement Cavium ThunderX erratum 23154 irqchip, gicv3-its: Implement Cavium ThunderX errata 22375, 24313 drivers/irqchip/irq-gic-common.c | 11 +++++++++ drivers/irqchip/irq-gic-common.h | 9 +++++++ drivers/irqchip/irq-gic-v3-its.c | 51 ++++++++++++++++++++++++++++++++++++---- drivers/irqchip/irq-gic-v3.c | 51 +++++++++++++++++++++++++++++++++++++++- 4 files changed, 116 insertions(+), 6 deletions(-) -- 2.1.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/