From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:35709 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934591AbcKKTMe (ORCPT ); Fri, 11 Nov 2016 14:12:34 -0500 Received: from pps.filterd (m0098396.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id uABJ9CNf056731 for ; Fri, 11 Nov 2016 14:12:34 -0500 Received: from e23smtp04.au.ibm.com (e23smtp04.au.ibm.com [202.81.31.146]) by mx0a-001b2d01.pphosted.com with ESMTP id 26nk8b302d-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Fri, 11 Nov 2016 14:12:34 -0500 Received: from localhost by e23smtp04.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Sat, 12 Nov 2016 05:12:31 +1000 Subject: Re: [PATCH] of/irq: improve error message on irq discovery process failure From: Benjamin Herrenschmidt Reply-To: benh@au1.ibm.com To: Mark Rutland Cc: devicetree@vger.kernel.org, "Guilherme G. Piccoli" , marc.zyngier@arm.com, linux-pci@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, robh+dt@kernel.org, frowand.list@gmail.com Date: Sat, 12 Nov 2016 06:12:27 +1100 In-Reply-To: <20161111163241.GL11945@leverpostej> References: <1478700308-25481-1-git-send-email-gpiccoli@linux.vnet.ibm.com> <20161109190457.GC837@leverpostej> <1478813443.2592.2.camel@au1.ibm.com> <20161111163241.GL11945@leverpostej> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Message-Id: <1478891547.2592.13.camel@au1.ibm.com> Sender: linux-pci-owner@vger.kernel.org List-ID: On Fri, 2016-11-11 at 16:32 +0000, Mark Rutland wrote: > On Fri, Nov 11, 2016 at 08:30:43AM +1100, Benjamin Herrenschmidt > wrote: > > > > On Wed, 2016-11-09 at 19:04 +0000, Mark Rutland wrote: > > > > > > > > > If we don't have an interrupt-map on a PCI controller, why don't > > > we > > > instead log a message regarding that being missing, and give up > > > early? > > > > Why ? It's legit to not support LSIs. > > Sure; I had envisioned a message like: > > pr_info("%s: no interrupt-map, INTx interrupts not possible\n", > pci_controller_name); > > ... Which tells the user exaclty what we know, and doesn't imply > either > an error or the actual absence of HW support. Works for me. Cheers, Ben.