[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <873874fuei.fsf@free.fr>
Date: Wed, 21 Jan 2015 08:46:29 +0100
From: Robert Jarzmik <robert.jarzmik@...e.fr>
To: Lee Jones <lee.jones@...aro.org>,
Russell King - ARM Linux <linux@....linux.org.uk>
Cc: Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org,
Samuel Ortiz <sameo@...ux.intel.com>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
linux-kernel@...r.kernel.org,
Haojian Zhuang <haojian.zhuang@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
linux-arm-kernel@...ts.infradead.org,
Kumar Gala <galak@...eaurora.org>,
Daniel Mack <daniel@...que.org>
Subject: Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board
Russell King - ARM Linux <linux@....linux.org.uk> writes:
> What I'd suggest (and always have done) is:
>
> dev_err(&pdev->dev, "couldn't request main irq%d: %d\n",
> irq, ret);
I like it, it's even more compact, I'll use it for next patch version.
> but I guess printing the IRQ number no longer makes sense with todays
> dynamic mapping of logical IRQ numbers, as it is no longer meaningful.
Yes ... we're not yet there with pxa gpio interrupts, maybe it will come
eventually one day.
For Lee:
> > > platform_get_irq()?
> > No. I need the flags.
> Where are they used?
A couple of lines below, using local "irqflags" variable :
ret = devm_request_irq(&pdev->dev, cot->irq, lubbock_irq_handler,
irqflags, dev_name(&pdev->dev), cot);
Cheers.
--
Robert
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists