Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933936Ab3JOUjg (ORCPT ); Tue, 15 Oct 2013 16:39:36 -0400 Received: from mail-wi0-f179.google.com ([209.85.212.179]:62691 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933181Ab3JOUjd (ORCPT ); Tue, 15 Oct 2013 16:39:33 -0400 From: Grant Likely To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [RFC 0/9] of: refactor IRQ parsing and add interrupts-extended implementation Date: Tue, 15 Oct 2013 21:39:14 +0100 Message-Id: <1381869563-16083-1-git-send-email-grant.likely@linaro.org> X-Mailer: git-send-email 1.8.1.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1093 Lines: 24 Hi everyone. This series is mostly a set of cleanup to the interrupt parsing code. Some of it merely clarification, like the renames of of_irq_map_*, some to tighten up the API by using of_phandle_args, and some to prepare for the last patch in the series. Of all these patches, the last one is probably the only one likely to be controversial. It adds a new way of specifying interrupts. If a device gets wired up to multiple interrupt controllers, the interrupts-extended property allows the device to specify multiple connections without redirecting through an interrupt-map node which can be rather difficult to understand. In a lot of cases, an interrupts-extended property is a whole lot easier to use. Please take a look and comment. We'll probably discuss the interrupts-extended binding in Edinburgh at the DT workshop in a few weeks. -- 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/