From: Meelis Roos <mroos@linux.ee>
To: linux-parisc@vger.kernel.org
Subject: parisc hardware clock
Date: Sun, 9 Oct 2016 01:16:14 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1610090107540.12761@math.ut.ee> (raw)
On my Gentoo hppa systems with custom kernels, I get the following
error on bootup:
* Setting system clock using the hardware clock [UTC] ...
hwclock: settimeofday() failed: Invalid argument
* Failed to set the system clock
Once the system has booted up, hwclock --hctosys and hwclock --systohc
work fine. Maybe something related to gentoo /etc/init.d/hwclock but
before reporting it there I want to understand it first.
What RTC driver and options should be selected in the kernel for RTC
operations to work?
I have only RTC_DRV_GENERIC set for RTC drivers.
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_INTF_DEV_UIE_EMUL=y
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
#
# SPI RTC drivers
#
#
# SPI and I2C RTC drivers
#
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1685_FAMILY is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
#
# on-CPU RTC drivers
#
CONFIG_RTC_DRV_GENERIC=y
#
# HID Sensor RTC drivers
#
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2016-10-08 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 22:16 Meelis Roos [this message]
2016-10-08 21:20 ` parisc hardware clock Helge Deller
2016-10-08 21:47 ` Helge Deller
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=alpine.LRH.2.20.1610090107540.12761@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-parisc@vger.kernel.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