linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ijc@hellion.org.uk (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks
Date: Sat, 02 May 2015 17:01:04 +0100	[thread overview]
Message-ID: <1430582464.15640.186.camel@hellion.org.uk> (raw)
In-Reply-To: <20150429085705.GG12732@n2100.arm.linux.org.uk>

On Wed, 2015-04-29 at 09:57 +0100, Russell King - ARM Linux wrote:
> On Sat, Apr 11, 2015 at 01:08:50AM +0100, Ben Hutchings wrote:
> > If this RTC is not battery backed, it seems like it ought to be disabled
> > in this board's device tree.
> 
> It's not that simple.
> 
> On the lower-end models, the on-SoC RTC is the only RTC there is.  If
> it were disabled, there would be no RTC available at all, so there
> would be no preservation of time-of-day across reboots.
> 
> On the Pro models, the battery backed RTC is fitted.  However, the
> battery backed RTC has no wakeup facility.
> 
> Only the on-SoC RTC has that ability, so in order to perform time-based
> wakeup, the on-SoC RTC needs to be synchronised with the current ToD
> and its alarm set.
> 
> Not having the on-SoC RTC enabled means that there is no ToD based
> wakeup possible.

So is your advice for a multi platform kernel supporting all Cubox
devices to just enable both and to sort out any syncing/naming etc in
userspace?

Thanks,
Ian.

  reply	other threads:[~2015-05-02 16:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150410232854.23367.58862.reportbug@cube.rcthomas.org>
2015-04-11  0:08 ` Bug#782364: linux-image-3.16.0-4-armmp: please configure drivers for both Cubox i4pro real time clocks Ben Hutchings
2015-04-29  3:02   ` Fabio Estevam
2015-04-29  5:46     ` Rick Thomas
2015-04-29  5:48     ` Rick Thomas
2015-04-29  8:57   ` Russell King - ARM Linux
2015-05-02 16:01     ` Ian Campbell [this message]
2015-05-02 16:12       ` Russell King - ARM Linux
2015-05-02 16:21         ` Ian Campbell
2015-05-06  8:01           ` Ian Campbell
2015-05-06 10:00             ` Rick Thomas
2015-05-06 10:27               ` Ian Campbell
2015-05-06 10:35                 ` Rick Thomas
2015-05-12  8:33                   ` Rick Thomas
2015-05-12  9:11                     ` Ian Campbell
2015-05-13  4:54                       ` Rick Thomas

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=1430582464.15640.186.camel@hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).