From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751286AbcHAIZj (ORCPT ); Mon, 1 Aug 2016 04:25:39 -0400 Received: from foss.arm.com ([217.140.101.70]:60610 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750777AbcHAIZ3 (ORCPT ); Mon, 1 Aug 2016 04:25:29 -0400 Subject: Re: [Urgent PATCH] arm64: dts: uniphier: fix IRQ trigger type of ARMv8 timer To: Masahiro Yamada , arm@kernel.org References: <1470039140-3801-1-git-send-email-yamada.masahiro@socionext.com> Cc: Mark Rutland , devicetree@vger.kernel.org, Catalin Marinas , Will Deacon , linux-kernel@vger.kernel.org, Rob Herring , linux-arm-kernel@lists.infradead.org From: Marc Zyngier Organization: ARM Ltd Message-ID: <579F05E1.9020300@arm.com> Date: Mon, 1 Aug 2016 09:18:41 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.0 MIME-Version: 1.0 In-Reply-To: <1470039140-3801-1-git-send-email-yamada.masahiro@socionext.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Please keep me cc-ed on this. On 01/08/16 09:12, Masahiro Yamada wrote: > Since commit 1e2a7d78499e ("irqdomain: Don't set type when mapping > an IRQ"), the interrupt type is strictly checked. Without this > patch, this board would not boot any more. > > Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.txt > says that the 3rd cell should be either 1 (edge) or 4 (level) > depending on the trigger type. As the CA72 Generic Timer provides > active-low interrupts, the value of the 3rd cell should be 4. > > Signed-off-by: Masahiro Yamada > Suggested-by: Marc Zyngier > --- > Arnd, Olof, > > I guess you are about to send pull-reqs for v4.8 cycle. > Could you include this one in them? > After IRQ updates for 4.8 were merged, my board would not > boot at all. I consulted experts and looks like my DT > was wrong. > > I could do this after -rc1 is out because it is apparently a > bug fix, but in that case the for-next branch in ASOC will be > broken for me, which would make bisect-ability difficult for me. I have a patch that addresses all platforms in one go (there is really no point in fixing one at a time for a bug that is so widespread). I'll repost it later today. Thanks, M. -- Jazz is not dead. It just smells funny...