linux-kernel - RE: [PATCH] tty: serial: imx: Only get second/third IRQ when there is more than one IRQ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <DB3PR0402MB3916361F60FA8ACBB434E7ADF5950@DB3PR0402MB3916.eurprd04.prod.outlook.com>
Date:   Wed, 9 Oct 2019 09:36:36 +0000
From:   Anson Huang <anson.huang@....com>
To:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>,
        Andy Shevchenko <andy.shevchenko@...il.com>
CC:     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 09, 2019 at 11:12:20AM +0300, Andy Shevchenko wrote:
> > 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.
> 
> This is even already in 5.4-rc1 as
> 8973ea47901c81a1912bd05f1577bed9b5b52506.

Great, I will send out a V2 using platform_get_irq_optional() for second/third IRQ.

Thanks,
Anson