From: Ashish Jangam <ashish.jangam@kpitcummins.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <sameo@linux.intel.com>,
<p_gortmaker@yahoo.com>, <dchen@diasemi.com>,
<rtc-linux@googlegroups.com>,
Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: [Patch v1] rtc: fix for the DA9052 rtc device registration
Date: Tue, 19 Mar 2013 17:12:45 +0530 [thread overview]
Message-ID: <1363693365.6897.1.camel@dhruva> (raw)
In-Reply-To: <20130318152145.3a458537db6c4799311a2143@linux-foundation.org>
On Mon, 2013-03-18 at 15:21 -0700, Andrew Morton wrote:
> On Fri, 15 Mar 2013 13:59:39 +0530 Ashish Jangam <ashish.jangam@kpitcummins.com> wrote:
>
> > DA9052/53 MFD core handles only virtual irq therefore rtc driver needs
> > to be updated to work on virtual irq. Without this update DA9052/53 rtc
> > driver will fail during its registration.
> > Also getting irq by it name is no longer supported in DA9052/53 core.
> >
> > ...
> >
> > --- a/drivers/rtc/rtc-da9052.c
> > +++ b/drivers/rtc/rtc-da9052.c
> > @@ -239,10 +239,10 @@ static int da9052_rtc_probe(struct platform_device *pdev)
> >
> > rtc->da9052 = dev_get_drvdata(pdev->dev.parent);
> > platform_set_drvdata(pdev, rtc);
> > - rtc->irq = platform_get_irq_byname(pdev, "ALM");
> > - ret = request_threaded_irq(rtc->irq, NULL, da9052_rtc_irq,
> > - IRQF_TRIGGER_LOW | IRQF_ONESHOT,
> > - "ALM", rtc);
> > + rtc->irq = DA9052_IRQ_ALARM;
> > +
> > + ret = da9052_request_irq(rtc->da9052, rtc->irq, "ALM",
> > + da9052_rtc_irq, rtc);
> > if (ret != 0) {
> > rtc_err(rtc->da9052, "irq registration failed: %d\n", ret);
> > return ret;
>
> drivers/rtc/rtc-da9052.c was converted to use
> devm_request_threaded_irq() after linux-3.8, so I cannot apply this
> patch to mainline. Can you please prepare a patch against 3.9-rc3?
Yes.
>
> Do you believe that the patch should be backported into -stable
> kernels? If so, Greg will need a different version of it - ie, the one
> you have just sent. Please send that to him at the appropriate time
> (say, when you see me drop the 3.9-rc3 version from the -mm tree).
Ok, I will do the necessary.
prev parent reply other threads:[~2013-03-19 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 8:29 [Patch v1] rtc: fix for the DA9052 rtc device registration Ashish Jangam
2013-03-18 22:21 ` Andrew Morton
2013-03-19 11:42 ` Ashish Jangam [this message]
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=1363693365.6897.1.camel@dhruva \
--to=ashish.jangam@kpitcummins.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=dchen@diasemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
--cc=rtc-linux@googlegroups.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.