[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcWXT+j5cfVzxPL+3YdgR+3uhFSb0qEDRr4YL+WenVKUQ@mail.gmail.com>
Date: Wed, 9 Oct 2019 11:12:20 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Cc: Anson Huang <Anson.Huang@....com>,
Stephen Boyd <swboyd@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
"open list:SERIAL DRIVERS" <linux-serial@...r.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
dl-linux-imx <Linux-imx@....com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: [PATCH] tty: serial: imx: Only get second/third IRQ when there is
more than one IRQ
On Wed, Oct 9, 2019 at 9:53 AM Uwe Kleine-König
<u.kleine-koenig@...gutronix.de> wrote:
> The patch is fine given the changed behaviour of platform_get_irq. I
> wonder if it is sensible to introduce a variant of platform_get_irq (say
> platform_get_irq_nowarn) that behaves like __platform_get_irq does
> today. Then the imx driver would just call platform_get_irq_nowarn
> without having to check the number of available irqs first.
It's being discussed in parallel thread about
platform_get_irq_optional() which won't issue a warning.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists