All of lore.kernel.org
 help / color / mirror / Atom feed
From: rbthomas@pobox.com (Rick Thomas)
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: Tue, 28 Apr 2015 22:48:29 -0700	[thread overview]
Message-ID: <74D54565-F9AE-4BE5-B48D-FFC8903CEF9D@pobox.com> (raw)
In-Reply-To: <CAOMZO5BrWbxarSEEC52Kb7=QR4K2e1qyAmMz3Rx+nq9r1vbdcw@mail.gmail.com>


On Apr 28, 2015, at 8:02 PM, Fabio Estevam <festevam@gmail.com> wrote:

> On Fri, Apr 10, 2015 at 9:08 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> 
>>> Whenever I reset my cubox-i4Pro by disconnecting the power plug, the hardware real-time-clock gets
>>> reset to midnight UTC, Dec 31, 1970.
>>> Even though the SolidRun literature says that the i4Pro has a battery backed RTC.
> 
>> If this RTC is not battery backed, it seems like it ought to be disabled
>> in this board's device tree.
> 
> Agreed. Just sent a patch for this.
> 
>>> # CONFIG_RTC_DRV_PCF8523 is not set
>>> 
>>> and
>>> 
>>> CONFIG_RTC_DRV_SNVS=y
> 
> And also a patch for turning on this option as well.
> 
> Regards,
> 
> Fabio Estevam

I don?t know if this makes any difference, but please remember that this box comes in several flavors.  Only the i4pro flavor has the battery-backed clock turned on in the hardware.

  parent reply	other threads:[~2015-04-29  5:48 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 [this message]
2015-04-29  8:57   ` Russell King - ARM Linux
2015-05-02 16:01     ` Ian Campbell
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=74D54565-F9AE-4BE5-B48D-FFC8903CEF9D@pobox.com \
    --to=rbthomas@pobox.com \
    --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 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.