Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2017387rwd; Sun, 21 May 2023 11:02:02 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5kg7Dmpt3nr5fRMCiszTe7sIo+M4setnjW/sLs7Y/y3yO/bv2DdI8dKM1P+qqwteqAfs4n X-Received: by 2002:a17:902:8f98:b0:1ae:f37:c1b1 with SMTP id z24-20020a1709028f9800b001ae0f37c1b1mr8013317plo.8.1684692122347; Sun, 21 May 2023 11:02:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684692122; cv=none; d=google.com; s=arc-20160816; b=rXXO0LRGW6raj0lYZ9UoC92AfYXBFOPeeqc5Vm1UHdAdh0BVAG6daXFnB+oq45bUGg AstoKAfn9IRavsL4qZS98NEG84VosZ355ydj39Go8Yc9m3UNAEw3o5CeRjdhfnLBat+r i5oT7YWE9rS+LiXxL27V8L1jDqkXijomLwhPICMvZ03z1fKck+Gq975kb+6zk8r4Ia8U CQsaAjdK5UNhQCZvLipFQ7tPPDZ9EV/LKBOuhK6ksMBEFcSV21agxLIrXa0zZSN4+lpd EzbA+m1j3hLNo3WC5IQjSaiC1Tpjm7To3QrkIiiNAli3uG/JiG5svXyFcA+aF5GLPqJZ /TOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:date:from; bh=uYqJsq9pTLz+ljQ6H7RUnkhYpIl+ruccfYp+5eSINSs=; b=QhAorWf8T5lEN6qSMTh9Eit4HjNfFAi9CeH+EPCL/KvMz9ZgYTjVD8C9vDt47QdMhX XJVlUzlHLDCAiTkNVSZWMthkOdbTw8CdNTUXUV08GIEd0KcfLUfrqyUHK63+QVisZ3M1 eisnbQQUjU9VPO6MR1pfs1dtz6xMgkfUZjYSwVF8r4+2pVWwcKUKuWpEwsGycYIG5OA0 JJYvjzN0+5LGLCxn7QD0sb83/cVOkJvyBKmDR9VcMk5zMqGay8T3KHsdi+pn2rZn/pkl tOwEe2ZczyCG/hjZ/BKs61chb36ywCeVoSWDN2ac+pb858OkN7FklbTfZkLbguJIAjpd oXFQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i12-20020a17090332cc00b001ae485ed19dsi3493050plr.511.2023.05.21.11.01.49; Sun, 21 May 2023 11:02:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231528AbjEURnI (ORCPT + 99 others); Sun, 21 May 2023 13:43:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44258 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231400AbjEURmy (ORCPT ); Sun, 21 May 2023 13:42:54 -0400 Received: from fgw23-7.mail.saunalahti.fi (fgw23-7.mail.saunalahti.fi [62.142.5.84]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 93E00110 for ; Sun, 21 May 2023 10:21:03 -0700 (PDT) Received: from localhost (88-113-26-95.elisa-laajakaista.fi [88.113.26.95]) by fgw23.mail.saunalahti.fi (Halon) with ESMTP id dacd9c49-f7fb-11ed-b972-005056bdfda7; Sun, 21 May 2023 20:21:00 +0300 (EEST) From: andy.shevchenko@gmail.com Date: Sun, 21 May 2023 20:20:59 +0300 To: Matti Vaittinen Cc: Matti Vaittinen , Andy Shevchenko , Daniel Scally , Heikki Krogerus , Sakari Ailus , Greg Kroah-Hartman , "Rafael J. Wysocki" , Wolfram Sang , Lars-Peter Clausen , Michael Hennerich , Jonathan Cameron , Andreas Klinger , Marcin Wojtas , Russell King , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Jonathan =?iso-8859-1?Q?Neusch=E4fer?= , Linus Walleij , Paul Cercueil , Akhil R , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org, linux-iio@vger.kernel.org, netdev@vger.kernel.org, openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org, linux-mips@vger.kernel.org Subject: Re: [PATCH v5 4/8] pinctrl: wpcm450: relax return value check for IRQ get Message-ID: References: <42264f1b12a91e415ffa47ff9adb53f02a6aa3ea.1684493615.git.mazziesaccount@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42264f1b12a91e415ffa47ff9adb53f02a6aa3ea.1684493615.git.mazziesaccount@gmail.com> X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, FORGED_GMAIL_RCVD,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED,SPF_HELO_NONE, SPF_SOFTFAIL,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Fri, May 19, 2023 at 02:02:16PM +0300, Matti Vaittinen kirjoitti: > fwnode_irq_get[_byname]() were changed to not return 0 anymore. The > special error case where device-tree based IRQ mapping fails can't no > longer be reliably detected from this return value. This yields a > functional change in the driver where the mapping failure is treated as > an error. > > The mapping failure can occur for example when the device-tree IRQ > information translation call-back(s) (xlate) fail, IRQ domain is not > found, IRQ type conflicts, etc. In most cases this indicates an error in > the device-tree and special handling is not really required. > > One more thing to note is that ACPI APIs do not return zero for any > failures so this special handling did only apply on device-tree based > systems. > > Drop the special (no error, just skip the IRQ) handling for DT mapping > failures as these can no longer be separated from other errors at driver > side. ... > The commit message does not mention if choosing not to abort the probe > on device-tree mapping failure (as is done on other errors) was chosen > because: a) Abort would have broken some existing setup. b) Because skipping > an IRQ on failure is "the right thing to do", or c) because it sounded like > a way to minimize risk of breaking something. > > If the reason is a) - then I'd appreciate receiving some more > information and a suggestion how to proceed (if possible). If the reason > is b), then it might be best to just skip the IRQ instead of aborting > the probe for all errors on IRQ getting. Finally, in case of c), well, > by acking this change you will now accept the risk :) No need to repeat this. As I answered the case c) was in my mind when I made that change. -- With Best Regards, Andy Shevchenko