From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752473AbbEOEH5 (ORCPT ); Fri, 15 May 2015 00:07:57 -0400 Received: from e23smtp08.au.ibm.com ([202.81.31.141]:34304 "EHLO e23smtp08.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751468AbbEOEHv (ORCPT ); Fri, 15 May 2015 00:07:51 -0400 From: Alistair Popple To: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au Cc: linux-kernel@vger.kernel.org, Alistair Popple , Corey Minyard , openipmi-developer@lists.sourceforge.net Subject: [PATCH v4 0/9] Convert OPAL notifier events to an irqchip Date: Fri, 15 May 2015 14:06:35 +1000 Message-Id: <1431662804-16851-1-git-send-email-alistair@popple.id.au> X-Mailer: git-send-email 1.8.3.2 X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15051504-0029-0000-0000-0000018CC328 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Whenever an interrupt is received for opal the linux kernel gets a bitfield indicating certain events that have occurred and need handling by the various device drivers. Currently this is handled using a notifier interface where we call every device driver that has registered to receive opal events. This approach has several drawbacks. For example each driver has to do its own checking to see if the event is relevant as well as event masking. There is also no easy method of recording the number of times we receive particular events. This series solves these issues by exposing opal events via the standard interrupt APIs by adding a new interrupt chip and domain. Drivers can then register for the appropriate events using standard kernel calls such as irq_of_parse_and_map(). Patches 2-8 of this series are the same as for v3. Changes from v3: - Changed initialisation sequence to solve the following errors on some machines: irq: XICS didn't like hwirq-0xb to VIRQ17 mapping (rc=-22) opal: opal_message_init: Can't register OPAL event irq (0) - Added a poller to the OPAL heartbeat to support machines where OPAL can't generate an interrupt for the host (eg. mambo) Changes from v2: - Addressed comments by Neelesh Gupta - Fixed soft-lockup bug reported by Neelesh in the opal-dump driver - Rebased on v4.1-rc1 Alistair Popple (9): powerpc/powernv: Reorder OPAL subsystem initialisation powerpc/powernv: Add a virtual irqchip for opal events ipmi/powernv: Convert to irq event interface hvc: Convert to using interrupts instead of opal events powernv/eeh: Update the EEH code to use the opal irq domain powernv/opal: Convert opal message events to opal irq domain powernv/elog: Convert elog to opal irq domain powernv/opal-dump: Convert to irq domain opal: Remove events notifier arch/powerpc/include/asm/opal.h | 6 + arch/powerpc/platforms/powernv/Makefile | 2 +- arch/powerpc/platforms/powernv/eeh-powernv.c | 58 ++--- arch/powerpc/platforms/powernv/opal-async.c | 3 +- arch/powerpc/platforms/powernv/opal-dump.c | 56 ++--- arch/powerpc/platforms/powernv/opal-elog.c | 32 +-- arch/powerpc/platforms/powernv/opal-hmi.c | 3 +- arch/powerpc/platforms/powernv/opal-irqchip.c | 249 +++++++++++++++++++++ .../powerpc/platforms/powernv/opal-memory-errors.c | 2 +- arch/powerpc/platforms/powernv/opal-sensor.c | 3 +- arch/powerpc/platforms/powernv/opal.c | 196 +++------------- arch/powerpc/platforms/powernv/powernv.h | 3 + arch/powerpc/platforms/powernv/setup.c | 2 +- drivers/char/ipmi/ipmi_powernv.c | 39 ++-- drivers/tty/hvc/hvc_opal.c | 33 +-- 15 files changed, 396 insertions(+), 291 deletions(-) create mode 100644 arch/powerpc/platforms/powernv/opal-irqchip.c -- 1.8.3.2