Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp724139pxb; Fri, 14 Jan 2022 15:04:07 -0800 (PST) X-Google-Smtp-Source: ABdhPJxLRetF2uEWOeXaArdf6It4buBLmsfpGkn80f4vmZ62rgchXwCyYgI5nYuOR052LDt0ZARe X-Received: by 2002:a63:754d:: with SMTP id f13mr9850890pgn.268.1642201446844; Fri, 14 Jan 2022 15:04:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642201446; cv=none; d=google.com; s=arc-20160816; b=w208XLj0hxiYsvVTqOAS4ux7Si0cra3gtlxhxg9s6VpEMxenz0Wf2bQpQhYtU04LU5 vWUGkh8KUX6d4L9meAiRgnh/0dQODg0LLW9OyYZjjr7bUaSybiZ/Dv+xwGbaSLx9ZNB0 L/Z7AUn5eQ56KG7o7U+RAK1h60pZWvlgUMUjPB/514SHbUgS1Ole5gIvuIPeCLFu102m 9606U9ilFzPqd4jU9vAEKCHJQNPJaYDWCzWUO1m8NvGczZ6RzJFZKN4VQf7JxUuyK/qd dhYqXmERomS54eKv+cnnn8rej/71LpPl96Vn5gR6G68LpBkO8i26VLhEdsanHMJnqHbe EJXw== 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=Qr9NNuqQz2HAy2TmOk0nwNl14JDRA5KZrvUlE7FnOu4=; b=slvb5f3E+KiaP+KVKtK6rYVFCe3al3uuhQc3E3A5r+YaiQR5Ue3dPLEkjXrHm6UrK4 blHCD8WMvjYE+KtTDHyTEmTwEvDx7Z1JW/a2iJIGK7xggRQ0CXdStC/9HQHP8oyfro+E Vsi9uZtHbKsZdqA0/T8OQcL7gCoVXVGBDufXBWjBxlOwr3WT+jaRKQR9e1ozSnL78vZJ e1r22wyPRaQ8kfZ6m0XQGu5Q8ZHhLl8UqW2brKuPJaoiBVku4ZQYwJRtNyqpr4uz7rgK gbwhBUR5Jn9dZQ1JT3efa9TIExd0f1T6nsmdNG5GzhfpXpqRxHW3jtLs+0qU+OCxrvch RUXw== 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 g7si7160534pfu.135.2022.01.14.15.03.55; Fri, 14 Jan 2022 15:04:06 -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 S244164AbiANTpu (ORCPT + 99 others); Fri, 14 Jan 2022 14:45:50 -0500 Received: from mxout01.lancloud.ru ([45.84.86.81]:39066 "EHLO mxout01.lancloud.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237113AbiANTps (ORCPT ); Fri, 14 Jan 2022 14:45:48 -0500 Received: from LanCloud DKIM-Filter: OpenDKIM Filter v2.11.0 mxout01.lancloud.ru EBF8C209322E 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: =?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 , Florian Fainelli , 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 , , Sergey Shtylyov , "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> From: Sergey Shtylyov Organization: Open Mobile Platform Message-ID: <386a7f56-38c8-229c-4fec-4b38a77c4121@omp.ru> Date: Fri, 14 Jan 2022 22:45:38 +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: <20220113194358.xnnbhsoyetihterb@pengutronix.de> Content-Type: text/plain; charset="windows-1252" 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/13/22 10:43 PM, Uwe Kleine-K?nig 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. Hm... I'm afraid that with this #define they would never get fixed... :-) > Signed-off-by: Uwe Kleine-K?nig > --- > Hello, > > On Thu, Jan 13, 2022 at 02:45:30PM +0000, Mark Brown wrote: >> On Thu, Jan 13, 2022 at 12:08:31PM +0100, Uwe Kleine-K?nig wrote: >> >>> This is all very unfortunate. In my eyes b) is the most sensible >>> sense, but the past showed that we don't agree here. (The most annoying >>> part of regulator_get is the warning that is emitted that regularily >>> makes customers ask what happens here and if this is fixable.) >> >> Fortunately it can be fixed, and it's safer to clearly specify things. >> The prints are there because when the description is wrong enough to >> cause things to blow up we can fail to boot or run messily and >> forgetting to describe some supplies (or typoing so they haven't done >> that) and people were having a hard time figuring out what might've >> happened. > > Yes, that's right. I sent a patch for such a warning in 2019 and pinged > occationally. Still waiting for it to be merged :-\ > (https://lore.kernel.org/r/20190625100412.11815-1-u.kleine-koenig@pengutronix.de) > >>> 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. I can't say I genrally agree with this patch... [...] > diff --git a/include/linux/platform_device.h b/include/linux/platform_device.h > index 7c96f169d274..6d495f15f717 100644 > --- a/include/linux/platform_device.h > +++ b/include/linux/platform_device.h > @@ -69,7 +69,14 @@ extern void __iomem * > devm_platform_ioremap_resource_byname(struct platform_device *pdev, > const char *name); > extern int platform_get_irq(struct platform_device *, unsigned int); > -extern int platform_get_irq_optional(struct platform_device *, unsigned int); > +extern int platform_get_irq_silent(struct platform_device *, unsigned int); > + > +/* > + * platform_get_irq_optional was recently renamed to platform_get_irq_silent. > + * Fixup users to not break patches that were created before the rename. > + */ > +#define platform_get_irq_optional(pdev, index) platform_get_irq_silent(pdev, index) > + Yeah, why bother fixing if it compiles anyway? I think an inline wrapper with an indication to gcc that the function is deprecated (I just forgot how it should look) would be better instead... > extern int platform_irq_count(struct platform_device *); > extern int devm_platform_get_irqs_affinity(struct platform_device *dev, > struct irq_affinity *affd, [...] MBR, Sergey