[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220214140027.npw6ddrxklarb6wp@pengutronix.de>
Date: Mon, 14 Feb 2022 15:00:27 +0100
From: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Andrew Lunn <andrew@...n.ch>, Ulf Hansson <ulf.hansson@...aro.org>,
Vignesh Raghavendra <vigneshr@...com>, kvm@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>, linux-iio@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
Amit Kucheria <amitk@...nel.org>, alsa-devel@...a-project.org,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Liam Girdwood <lgirdwood@...il.com>,
Guenter Roeck <groeck@...omium.org>,
Thierry Reding <thierry.reding@...il.com>,
linux-mtd@...ts.infradead.org, linux-i2c@...r.kernel.org,
Miquel Raynal <miquel.raynal@...tlin.com>,
linux-phy@...ts.infradead.org,
Oleksij Rempel <linux@...pel-privat.de>,
Lee Jones <lee.jones@...aro.org>,
"David S. Miller" <davem@...emloft.net>,
Peter Korsgaard <peter@...sgaard.com>,
Florian Fainelli <f.fainelli@...il.com>,
Matthias Schiffer <matthias.schiffer@...tq-group.com>,
Joakim Zhang <qiangqing.zhang@....com>,
Kamal Dasu <kdasu.kdev@...il.com>,
Jiri Slaby <jirislaby@...nel.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Kishon Vijay Abraham I <kishon@...com>,
bcm-kernel-feedback-list@...adcom.com,
linux-serial@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
platform-driver-x86@...r.kernel.org, linux-pwm@...r.kernel.org,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Corey Minyard <minyard@....org>, linux-pm@...r.kernel.org,
John Garry <john.garry@...wei.com>,
William Breathitt Gray <vilhelm.gray@...il.com>,
Mark Gross <markgross@...nel.org>, linux-gpio@...r.kernel.org,
Alex Williamson <alex.williamson@...hat.com>,
Mark Brown <broonie@...nel.org>,
linux-mediatek@...ts.infradead.org,
Eric Auger <eric.auger@...hat.com>,
Takashi Iwai <tiwai@...e.com>,
Matthias Brugger <matthias.bgg@...il.com>,
openipmi-developer@...ts.sourceforge.net,
Jaroslav Kysela <perex@...ex.cz>,
Benson Leung <bleung@...omium.org>,
linux-arm-kernel@...ts.infradead.org,
Sergey Shtylyov <s.shtylyov@....ru>,
Mun Yew Tham <mun.yew.tham@...el.com>,
Hans de Goede <hdegoede@...hat.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
Cornelia Huck <cohuck@...hat.com>, linux-mmc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, Vinod Koul <vkoul@...nel.org>,
Zha Qipeng <qipeng.zha@...el.com>,
Richard Weinberger <richard@....at>,
Niklas Söderlund <niklas.soderlund@...natech.se>,
Brian Norris <computersforpeace@...il.com>,
netdev@...r.kernel.org
Subject: Re: [PATCH v2 1/2] platform: make platform_get_irq_optional()
optional
Hello Geert,
On Mon, Feb 14, 2022 at 10:01:14AM +0100, Geert Uytterhoeven wrote:
> Also IMHO, the dummy value handling is a red herring. Contrary to
> optional clocks and resets, a missing optional interrupt does not
> always mean there is nothing to do: in case of polling, something
> else must definitely be done.
Note this is exactly why I don't like this change. I'd even go so far
and claim that "a missing optional interrupt hardly ever means there is
nothing to do".
> So even if request_irq() would accept a dummy interrupt zero and just
> do nothing, it would give the false impression that that is all there
> is to do, while an actual check for zero with polling code handling
> may still need to be present, thus leading to more not less bugs.
Yes, a dummy irq value will just not be possible.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists