From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Michael Lange <linuxstuff@milaw.biz>
Cc: rtc-linux@googlegroups.com
Subject: Re: [rtc-linux] [PATCH] rtc: ds1307.c: add support for the DT property 'wakeup-source'
Date: Fri, 22 Jan 2016 01:07:28 +0100 [thread overview]
Message-ID: <20160122000728.GE3608@piout.net> (raw)
In-Reply-To: <1453396216-8367-1-git-send-email-linuxstuff@milaw.biz>
Hi,
On 21/01/2016 at 18:10:16 +0100, Michael Lange wrote :
> For RTC chips with no IRQ directly connected to the SoC, the RTC chip
> can be forced as a wakeup source by stating that explicitly in
> the device's .dts file using the "wakeup-source" boolean property.
> This will guarantee the 'wakealarm' sysfs entry is available on the
> device, if supported by the RTC.
>
> With these changes to the driver rtc-ds1307 and the necessary entries
> in the .dts file, I get an working ds1337 RTC on the Witty Pi extension
> board by UUGear for the Raspberry Pi.
>
> An example for the entry in the .dts file:
>
> rtc: ds1337@68 {
> compatible = "dallas,ds1337";
> reg = <0x68>;
> wakeup-source;
>
> If the "wakeup-source" property is set, do not request an IRQ.
> Set also UIE mode to unsupported, to get a working 'hwclock' binary.
>
I don't think setting uie_unsupported is necessary because the alarm
functions will fail anyway. What kind of issue did you have?
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-01-22 0:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 17:10 [rtc-linux] [PATCH] rtc: ds1307.c: add support for the DT property 'wakeup-source' Michael Lange
2016-01-22 0:07 ` Alexandre Belloni [this message]
2016-01-22 15:35 ` Michael Lange
2016-01-22 15:58 ` Alexandre Belloni
2016-01-26 8:26 ` Alexandre Belloni
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=20160122000728.GE3608@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=linuxstuff@milaw.biz \
--cc=rtc-linux@googlegroups.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