From: Sebastian Reichel <sre@debian.org>
To: linux-omap@vger.kernel.org
Cc: tony@atomide.com, John Stultz <john.stultz@linaro.org>,
a.zummo@towertech.it, rtc-linux@googlegroups.com,
balajitk@ti.com, Ilkka Koskinen <ilkkakos@kolumbus.fi>
Subject: Re: [PATCH] rtc-twl: Switch to using threaded irq
Date: Tue, 31 May 2011 10:51:39 +0200 [thread overview]
Message-ID: <20110531085139.GA7290@earth.universe> (raw)
In-Reply-To: <4DD41BE5.4050600@kolumbus.fi>
[-- Attachment #1.1: Type: text/plain, Size: 1375 bytes --]
Hi,
I think the patch should also remove the local_irq_enable() call in
twl_rtc_interrupt, since it's no longer needed with threaded irq. At
least on the Pandaboard the RTC is still working with the appended
patch.
-- Sebastian
> >> On Apr 13, 2011 Krishnamoorthy, Balaji T wrote:
> >>> On Wed, Mar 16, 2011 at 9:37 PM, Ilkka Koskinen
> >> <ilkka.koskinen@nokia.com> wrote:
> >>>>
> >>>> The driver is accessing to i2c bus in interrupt handler.
> >>>> Therefore, it should use threaded irq.
> >>
> >>> Acked-by: Balaji T K <balajitk@ti.com>
> >>
> >>>>
> >>>> Signed-off-by: Ilkka Koskinen <ilkka.koskinen@nokia.com>
> >>>> ---
> >>>> drivers/rtc/rtc-twl.c | 2 +-
> >>>> 1 files changed, 1 insertions(+), 1 deletions(-)
> >>>>
> >>>> diff --git a/drivers/rtc/rtc-twl.c b/drivers/rtc/rtc-twl.c
> >>>> index ed1b868..2715b96 100644
> >>>> --- a/drivers/rtc/rtc-twl.c
> >>>> +++ b/drivers/rtc/rtc-twl.c
> >>>> @@ -475,7 +475,7 @@ static int __devinit twl_rtc_probe(struct platform_device *pdev)
> >>>> if (ret < 0)
> >>>> goto out1;
> >>>>
> >>>> - ret = request_irq(irq, twl_rtc_interrupt,
> >>>> + ret = request_threaded_irq(irq, NULL, twl_rtc_interrupt,
> >>>> IRQF_TRIGGER_RISING,
> >>>> dev_name(&rtc->dev), rtc);
> >>>> if (ret < 0) {
> >>>> --
> >>>> 1.7.0.4
[-- Attachment #1.2: fix-twl-rtc.patch --]
[-- Type: text/x-diff, Size: 908 bytes --]
--- a/drivers/rtc/rtc-twl.c 2011-05-19 06:06:34.000000000 +0200
+++ b/drivers/rtc/rtc-twl.c 2011-05-26 20:34:03.000000000 +0200
@@ -362,14 +362,6 @@
int res;
u8 rd_reg;
-#ifdef CONFIG_LOCKDEP
- /* WORKAROUND for lockdep forcing IRQF_DISABLED on us, which
- * we don't want and can't tolerate. Although it might be
- * friendlier not to borrow this thread context...
- */
- local_irq_enable();
-#endif
-
res = twl_rtc_read_u8(&rd_reg, REG_RTC_STATUS_REG);
if (res)
goto out;
@@ -462,7 +454,7 @@
if (ret < 0)
goto out1;
- ret = request_irq(irq, twl_rtc_interrupt,
+ ret = request_threaded_irq(irq, NULL, twl_rtc_interrupt,
IRQF_TRIGGER_RISING,
dev_name(&rtc->dev), rtc);
if (ret < 0) {
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-05-31 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 16:07 [PATCH] rtc-twl: Switch to using threaded irq Ilkka Koskinen
2011-04-13 7:41 ` Krishnamoorthy, Balaji T
2011-05-05 7:51 ` ilkka.koskinen
2011-05-12 23:24 ` John Stultz
2011-05-18 19:20 ` Ilkka Koskinen
2011-05-31 8:51 ` Sebastian Reichel [this message]
2011-06-27 16:45 ` Sebastian Reichel
2011-08-10 22:44 ` John Stultz
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=20110531085139.GA7290@earth.universe \
--to=sre@debian.org \
--cc=a.zummo@towertech.it \
--cc=balajitk@ti.com \
--cc=ilkkakos@kolumbus.fi \
--cc=john.stultz@linaro.org \
--cc=linux-omap@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=tony@atomide.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).