From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
LINUXKERNEL <linux-kernel@vger.kernel.org>,
RTC-LINUX <rtc-linux@googlegroups.com>,
David Dajun Chen <david.chen@diasemi.com>,
Support Opensource <support.opensource@diasemi.com>
Subject: Re: [PATCH V1] rtc: da9063: access ordering error during RTC interrupt system power on
Date: Mon, 21 Dec 2015 09:19:08 +0100 [thread overview]
Message-ID: <20151221081908.GG3541@piout.net> (raw)
In-Reply-To: <20151208163406.B34683FB25@swsrvapps-01.diasemi.com>
On 08/12/2015 at 16:28:39 +0000, Steve Twiss wrote :
> From: Steve Twiss <stwiss.opensource@diasemi.com>
>
> This fix alters the ordering of the IRQ and device registrations in the RTC
> driver probe function. This change will apply to the RTC driver that supports
> both DA9063 and DA9062 PMICs.
>
> A problem could occur with the existing RTC driver if:
>
> A system is started from a cold boot using the PMIC RTC IRQ to initiate a
> power on operation. For instance, if an RTC alarm is used to start a
> platform from power off.
> The existing driver IRQ is requested before the device has been properly
> registered.
> i.e.
> ret = devm_request_threaded_irq()
> comes before
> rtc->rtc_dev = devm_rtc_device_register();
>
> In this case, the interrupt can be called before the device has been
> registered and the handler can be called immediately. The IRQ handler
> da9063_alarm_event() contains the function call
>
> rtc_update_irq(rtc->rtc_dev, 1, RTC_IRQF | RTC_AF);
>
> which in turn tries to access the unavailable rtc->rtc_dev.
>
> The fix is to reorder the functions inside the RTC probe. The IRQ is
> requested after the RTC device resource has been registered so that
> get_irq_byname is the last thing to happen.
>
> Signed-off-by: Steve Twiss <stwiss.opensource@diasemi.com>
This patch has been applied and landed in v4.4-rc6
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-21 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 16:28 [PATCH V1] rtc: da9063: access ordering error during RTC interrupt system power on Steve Twiss
2015-12-16 23:47 ` Alexandre Belloni
2015-12-17 11:37 ` Opensource [Steve Twiss]
2015-12-17 11:44 ` Alexandre Belloni
2015-12-21 8:19 ` Alexandre Belloni [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=20151221081908.GG3541@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=david.chen@diasemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=stwiss.opensource@diasemi.com \
--cc=support.opensource@diasemi.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