Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp722812pxb; Fri, 14 Jan 2022 15:02:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJxMypMiogyKgfe2KuWWywzDzybN2daFbA8JfjToXQq8nZwGKboG+bJTetRMvDAvtL6vJzKD X-Received: by 2002:a05:6402:2707:: with SMTP id y7mr10890371edd.409.1642201352101; Fri, 14 Jan 2022 15:02:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642201352; cv=none; d=google.com; s=arc-20160816; b=HY70WUWvQxeQ1aAgrl+ZN11UPkDdk4mtrxXKQuwKjwueKtMUzkRN+N/3gJfoWEmAao dfbQVUxuqQxseNyq9tRY1uvEyzJGEuSucDRPmtjN+awl+j5TGbQrukmWpRbHdnnLAdQ+ ak8iOxiOKxMbAyMzF8m/o301gMOcBga3RSuBD/2OHaxOWt9VeZ8G0JmO0HKlIshGvg2Z GCX3eLyLREe9omieTvrYHRjqxg1AzUAMXOAU+JPZLIl/rmlS2QO4NvUvBYqAj63TzY2B m8TUxrrceUoNxNbftPOT1CLQO8It4axAaWPANQkNJfBmFPIE6L7akIQlLJ+ueNKHGN3U nidw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:organization :from:references:cc:to:subject:dkim-filter; bh=zY3hm8Lvjkhit670qrcVFfVsXaejWa0lYkXt5tUde9w=; b=A5xNBeN9Rpj8Eb6nDGaBwGSxMFrxz+2Z3yImQQpJF/ZANXuJ8spTFEsULHEWOs5LVv gONkDZVtH0GZWD9+jzuaH2qaLM3+JOurudpOisTsj8xN2OVMGlGKYG+8SrS81bj3nQ/Y +OlSAYaBC+RTgXxYJFUfytMFKUKs1bJRej/ZVqkjnKlquUVeGl79k2RLpp/ZB/bkVcB5 wmDpwVHz4ColLwWsyV1/qiG+2sV5WrpAkIEWuNln7ddP0JYo4hi2PPfFEHaxePQ9zJKS 0NHekNVli0qveNAdss/m2bf6e9shy0IUJ/l5QJQVt7f6ke8q4yjy/Bc59Ft98FE2JZsu grYg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q4si813412ejr.44.2022.01.14.15.02.00; Fri, 14 Jan 2022 15:02:32 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243955AbiANRzW (ORCPT + 99 others); Fri, 14 Jan 2022 12:55:22 -0500 Received: from mxout02.lancloud.ru ([45.84.86.82]:37634 "EHLO mxout02.lancloud.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244005AbiANRzR (ORCPT ); Fri, 14 Jan 2022 12:55:17 -0500 Received: from LanCloud DKIM-Filter: OpenDKIM Filter v2.11.0 mxout02.lancloud.ru 02F2120606E9 Received: from LanCloud Received: from LanCloud Received: from LanCloud Subject: Re: [PATCH] driver core: platform: Rename platform_get_irq_optional() to platform_get_irq_silent() To: Florian Fainelli , =?UTF-8?Q?Uwe_Kleine-K=c3=b6nig?= , Mark Brown CC: Andrew Lunn , Ulf Hansson , Vignesh Raghavendra , KVM list , "Rafael J. Wysocki" , , "Linus Walleij" , Amit Kucheria , "ALSA Development Mailing List" , Andy Shevchenko , Jaroslav Kysela , Guenter Roeck , Thierry Reding , MTD Maling List , Linux I2C , Miquel Raynal , , Jiri Slaby , , "David S. Miller" , Khuong Dinh , Matthias Schiffer , Joakim Zhang , Kamal Dasu , Lee Jones , Bartosz Golaszewski , Daniel Lezcano , Kishon Vijay Abraham I , "Geert Uytterhoeven" , "open list:SERIAL DRIVERS" , Yoshihiro Shimoda , bcm-kernel-feedback-list , Zhang Rui , Linux PWM List , Robert Richter , Saravanan Sekar , Corey Minyard , Linux PM list , Liam Girdwood , Mauro Carvalho Chehab , John Garry , Peter Korsgaard , "William Breathitt Gray" , Mark Gross , Hans de Goede , Alex Williamson , Tony Luck , "Borislav Petkov" , Sebastian Reichel , Jakub Kicinski , Matthias Brugger , Takashi Iwai , , Benson Leung , Linux ARM , , Mun Yew Tham , "Eric Auger" , Greg Kroah-Hartman , "open list:GPIO SUBSYSTEM" , Cornelia Huck , "Linux MMC List" , Linux Kernel Mailing List , linux-spi , Linux-Renesas , Vinod Koul , James Morse , Zha Qipeng , Pengutronix Kernel Team , Richard Weinberger , =?UTF-8?Q?Niklas_S=c3=b6derlund?= , , "Brian Norris" , References: <20220110195449.12448-2-s.shtylyov@omp.ru> <20220110201014.mtajyrfcfznfhyqm@pengutronix.de> <20220112085009.dbasceh3obfok5dc@pengutronix.de> <20220112213121.5ruae5mxwj6t3qiy@pengutronix.de> <20220113110831.wvwbm75hbfysbn2d@pengutronix.de> <20220113194358.xnnbhsoyetihterb@pengutronix.de> <745c601f-c782-0904-f786-c9bfced8f11c@gmail.com> From: Sergey Shtylyov Organization: Open Mobile Platform Message-ID: Date: Fri, 14 Jan 2022 20:55:07 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <745c601f-c782-0904-f786-c9bfced8f11c@gmail.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 8bit X-Originating-IP: [192.168.11.198] X-ClientProxiedBy: LFEXT02.lancloud.ru (fd00:f066::142) To LFEX1907.lancloud.ru (fd00:f066::207) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/14/22 12:42 AM, Florian Fainelli wrote: >> The subsystems regulator, clk and gpio have the concept of a dummy >> resource. For regulator, clk and gpio there is a semantic difference >> between the regular _get() function and the _get_optional() variant. >> (One might return the dummy resource, the other won't. Unfortunately >> which one implements which isn't the same for these three.) The >> difference between platform_get_irq() and platform_get_irq_optional() is >> only that the former might emit an error message and the later won't. >> >> To prevent people's expectations that there is a semantic difference >> between these too, rename platform_get_irq_optional() to >> platform_get_irq_silent() to make the actual difference more obvious. >> >> The #define for the old name can and should be removed once all patches >> currently in flux still relying on platform_get_irq_optional() are >> fixed. >> >> Signed-off-by: Uwe Kleine-König [...] >>>> I think at least c) is easy to resolve because >>>> platform_get_irq_optional() isn't that old yet and mechanically >>>> replacing it by platform_get_irq_silent() should be easy and safe. >>>> And this is orthogonal to the discussion if -ENOXIO is a sensible return >>>> value and if it's as easy as it could be to work with errors on irq >>>> lookups. >>> >>> It'd certainly be good to name anything that doesn't correspond to one >>> of the existing semantics for the API (!) something different rather >>> than adding yet another potentially overloaded meaning. >> >> It seems we're (at least) three who agree about this. Here is a patch >> fixing the name. > > From an API naming perspective this does not make much sense anymore with the name chosen, > it is understood that whent he function is called platform_get_irq_optional(), optional applies > to the IRQ. An optional IRQ is something people can reason about because it makes sense. Right! :-) > What is a a "silent" IRQ however? It does not apply to the object it is trying to fetch to > anymore, but to the message that may not be printed in case the resource failed to be obtained, > because said resource is optional. Woah, that's quite a stretch. Right again! :-) > Following the discussion and original 2 patches set from Sergey, it is not entirely clear to me > anymore what is it that we are trying to fix. Andy and me tried to fix the platform_get_irq[_byname]_optional() value, corresponding to a missing (optional) IRQ resource from -ENXIO to 0, in order to keep the callers error code agnostic. This change completely aligns e.g. platform_get_irq_optional() with clk_get_optional() and gpiod_get_optional()... Unforunately, we can't "fix" request_irq() and company to treat 0 as missing IRQ -- they have to keep the ability to get called from the arch/ code (that doesn't use platform_get_irq(), etc. > I nearly forgot, I would paint it blue, sky blue, not navy blue, not light blue ;) :-) PS: Florian, something was wrong with your mail client -- I had to manually wrap your quotes, else there were super long unbroken paragraphs...