From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751807Ab3JaBT6 (ORCPT ); Wed, 30 Oct 2013 21:19:58 -0400 Received: from mail-vb0-f42.google.com ([209.85.212.42]:35418 "EHLO mail-vb0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751408Ab3JaBTq (ORCPT ); Wed, 30 Oct 2013 21:19:46 -0400 MIME-Version: 1.0 In-Reply-To: References: <1381869563-16083-1-git-send-email-grant.likely@linaro.org> <1381869563-16083-5-git-send-email-grant.likely@linaro.org> Date: Thu, 31 Oct 2013 09:19:44 +0800 Message-ID: Subject: Re: [RFC 4/9] of/irq: Refactor interrupt-map parsing From: Ming Lei To: Olof Johansson Cc: Grant Likely , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Benjamin Herrenschmidt , Kevin Hilman Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 30, 2013 at 12:23 AM, Olof Johansson wrote: > Hi, > > On Tue, Oct 15, 2013 at 1:39 PM, Grant Likely wrote: >> All the users of of_irq_parse_raw pass in a raw interrupt specifier from >> the device tree and expect it to be returned (possibly modified) in an >> of_phandle_args structure. However, the primary function of >> of_irq_parse_raw() is to check for translations due to the presence of >> one or more interrupt-map properties. The actual placing of the data >> into an of_phandle_args structure is trivial. If it is refactored to >> accept an of_phandle_args structure directly, then it becomes possible >> to consume of_phandle_args from other sources. This is important for an >> upcoming patch that allows a device to be connected to more than one >> interrupt parent. It also simplifies the code a bit. >> >> The biggest complication with this patch is that the old version works >> on the interrupt specifiers in __be32 form, but the of_phandle_args >> structure is intended to carry it in the cpu-native version. A bit of >> churn was required to make this work. In the end it results in tighter >> code, so the churn is worth it. >> >> Signed-off-by: Grant Likely >> Cc: Benjamin Herrenschmidt > > This patch stopped exynos/arndale from booting when it hit next (i.e. > last night). I bisected down to this commit. +1, :-) > > It seems that the platform is getting stuck calibrating delay loop, > i.e. it is not getting interrupts. Let me know if you want me to > collect more data of some sort. Thanks, -- Ming Lei