From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Lee Jones <lee.jones@linaro.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Samuel Ortiz <sameo@linux.intel.com>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
linux-kernel@vger.kernel.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Kumar Gala <galak@codeaurora.org>,
Daniel Mack <daniel@zonque.org>
Subject: Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board
Date: Wed, 21 Jan 2015 08:46:29 +0100 [thread overview]
Message-ID: <873874fuei.fsf@free.fr> (raw)
In-Reply-To: 20150120115658.GJ26493@n2100.arm.linux.org.uk
Russell King - ARM Linux <linux@arm.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
next prev parent reply other threads:[~2015-01-21 7:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 11:00 [PATCH v3 1/3] dt-bindings: mfd: add lubbock-io binding Robert Jarzmik
2015-01-16 11:00 ` [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board Robert Jarzmik
2015-01-19 9:17 ` Lee Jones
2015-01-19 19:09 ` Robert Jarzmik
2015-01-20 10:29 ` Lee Jones
2015-01-20 11:56 ` Russell King - ARM Linux
2015-01-21 7:46 ` Robert Jarzmik [this message]
2015-01-21 8:16 ` Lee Jones
2015-01-21 8:27 ` Robert Jarzmik
2015-01-21 12:35 ` Lee Jones
2015-01-21 13:02 ` Russell King - ARM Linux
2015-01-21 13:36 ` robert.jarzmik
2015-01-21 15:10 ` Lee Jones
2015-01-21 19:22 ` Robert Jarzmik
2015-01-21 9:47 ` Russell King - ARM Linux
2015-01-21 9:44 ` Russell King - ARM Linux
2015-01-21 16:05 ` unclear ipv6 redirect message (was Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board) Joe Perches
2015-01-21 16:11 ` Russell King - ARM Linux
2015-01-21 16:40 ` Joe Perches
2015-01-21 16:46 ` Russell King - ARM Linux
2015-01-16 11:00 ` [PATCH v3 3/3] ARM: pxa: lubbock: use new lubbock_io driver Robert Jarzmik
2015-01-19 8:35 ` [PATCH v3 1/3] dt-bindings: mfd: add lubbock-io binding Lee Jones
2015-01-19 19:29 ` Robert Jarzmik
2015-01-20 10:18 ` Lee Jones
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=873874fuei.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=haojian.zhuang@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).