From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752672AbcG2Ibx (ORCPT ); Fri, 29 Jul 2016 04:31:53 -0400 Received: from hqemgate16.nvidia.com ([216.228.121.65]:19361 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751586AbcG2Ibt (ORCPT ); Fri, 29 Jul 2016 04:31:49 -0400 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Fri, 29 Jul 2016 01:29:06 -0700 Subject: Re: [PATCH V6 3/9] irqdomain: Don't set type when mapping an IRQ To: Masahiro Yamada References: <1465312354-27778-1-git-send-email-jonathanh@nvidia.com> <1465312354-27778-4-git-send-email-jonathanh@nvidia.com> CC: Thomas Gleixner , Jason Cooper , Marc Zyngier , Rob Herring , "Pawel Moll" , Mark Rutland , Ian Campbell , Kumar Gala , "Stephen Warren" , Thierry Reding , Kevin Hilman , Geert Uytterhoeven , Grygorii Strashko , Lars-Peter Clausen , Linus Walleij , , , "Linux Kernel Mailing List" From: Jon Hunter Message-ID: Date: Fri, 29 Jul 2016 09:31:40 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [10.26.11.170] X-ClientProxiedBy: UKMAIL101.nvidia.com (10.26.138.13) To UKMAIL101.nvidia.com (10.26.138.13) Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29/07/16 04:53, Masahiro Yamada wrote: > Hi. > > I noticed my board would not work any more > when pulling recent updates. > > I did "git-bisect" and I found the following commit is it. > > commit 1e2a7d78499ec8859d2b469051b7b80bad3b08aa > Author: Jon Hunter > Date: Tue Jun 7 16:12:28 2016 +0100 > > irqdomain: Don't set type when mapping an IRQ > > With reverting it, everything works fine for me. > > My board is arch/arm64/boot/dts/socionext/uniphier-ph1-ld20-ref.dts > > Is anything wrong with IRQ settings in my Device Tree? Most likely. > If 1e2a7d784 is really a buggy commit, > could you do something please? Before this commit bad IRQ type settings in device-tree were not getting reported and so that's why most likely it is bad IRQ type settings. As Marc mentioned without any more details (which IRQ for which device is failing) we cannot confirm. So I would look at the failing IRQ which is now failing when being requested and see if the type in device-tree is correct. Cheers Jon -- nvpublic