From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform: finally disallow IRQ0 in platform_get_irq() and its ilk
Date: Fri, 3 Dec 2021 00:11:57 +0300 [thread overview]
Message-ID: <f08072e8-df0a-95b4-0937-47e5763b40dc@omp.ru> (raw)
In-Reply-To: <YaEJUiZRhkGRZqpt@kroah.com>
Hello!
On 11/26/21 7:20 PM, Greg Kroah-Hartman wrote:
>> The commit a85a6c86c25b ("driver core: platform: Clarify that IRQ 0 is
>> invalid") only calls WARN() when IRQ0 is about to be returned, however
>> using IRQ0 is considered invalid (according to Linus) outside the arch/
>> code where it's used by the i8253 drivers. Many driver subsystems treat
>> 0 specially (e.g. as an indication of the polling mode by libata), so
>> the users of platform_get_irq[_byname]() in them would have to filter
>> out IRQ0 explicitly and this (quite obviously) doesn't scale...
>> Let's finally get this straight and return -EINVAL instead of IRQ0!
>>
>> Fixes: a85a6c86c25b ("driver core: platform: Clarify that IRQ 0 is invalid")
>> Signed-off-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>>
>> ---
>> The patch is against the 'driver-core-linus' branch of Greg Kroah-Hartman's
>> 'driver-core.git' repo.
>>
>> drivers/base/platform.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> Index: driver-core/drivers/base/platform.c
>> ===================================================================
>> --- driver-core.orig/drivers/base/platform.c
>> +++ driver-core/drivers/base/platform.c
>> @@ -231,7 +231,8 @@ int platform_get_irq_optional(struct pla
>> out_not_found:
>> ret = -ENXIO;
>> out:
>> - WARN(ret == 0, "0 is an invalid IRQ number\n");
>> + if (WARN(!ret, "0 is an invalid IRQ number\n"))
>> + return -EINVAL;
>
> You need to get approval from the interrrupt developers for this type of
> change, as it is a change and might break existing platforms, right?
Well, that's always possible... :-)
I do remember we had issues with the serial driver on the Alchemy MIPS SoCs
back in the 2.6.1x time frame: UART0 used IRQ0 there and the serial driver treated
0 as an indication of the polling mode, IIRC... Now Alchemies have the SoC IRQ0
mapped to the Linux IRQ8, so this is not a problem anymore (the 1st 8 IRQs are
mapped to the MIPS CPU IRQs and IRQ0 isn't even used)...
> thanks,
>
> greg k-h
MBR, Sergey
next prev parent reply other threads:[~2021-12-02 21:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 20:26 Sergey Shtylyov
2021-11-26 16:20 ` Greg Kroah-Hartman
2021-12-02 21:11 ` Sergey Shtylyov [this message]
2021-12-09 20:06 ` Andy Shevchenko
2021-12-09 20:21 ` Sergey Shtylyov
2021-12-10 11:17 ` Andy Shevchenko
2022-01-04 19:27 ` Sergey Shtylyov
2022-01-05 10:09 ` Andy Shevchenko
2022-01-09 11:31 ` Sergey Shtylyov
2022-01-04 9:26 ` Marc Zyngier
2022-01-04 9:47 ` Geert Uytterhoeven
2022-01-04 10:48 ` Marc Zyngier
2022-01-04 10:53 ` Greg Kroah-Hartman
2022-01-04 11:13 ` Marc Zyngier
2022-01-05 10:02 ` Andy Shevchenko
2022-01-04 11:24 ` Geert Uytterhoeven
2022-01-05 9:59 ` Andy Shevchenko
2022-01-04 12:23 ` Sergey Shtylyov
2022-01-04 20:30 ` Sergey Shtylyov
2022-01-12 17:53 ` Sergey Shtylyov
2022-01-12 18:08 ` Marc Zyngier
2022-01-12 20:08 ` Sergey Shtylyov
2022-02-11 20:20 ` Sergey Shtylyov
2022-01-12 18:19 ` Greg Kroah-Hartman
2022-01-12 20:20 ` Sergey Shtylyov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f08072e8-df0a-95b4-0937-47e5763b40dc@omp.ru \
--to=s.shtylyov@omp.ru \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome