Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jul 2019 18:59:17 -0600
From:      Ian Lepore <ian@freebsd.org>
To:        Stefan Parvu <sparvu@kronometrix.org>, freebsd-arm@freebsd.org
Subject:   Re: Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0
Message-ID:  <6a39f74088d2984b5426e8585b5f7e864a6766f8.camel@freebsd.org>
In-Reply-To: <5F33E59B-7EA5-4B8B-A95A-CD1FB569ACDC@kronometrix.org>
References:  <41A4CA5C-B487-490F-8A19-2D51F43E1004@kronometrix.org> <95616620-bbaf-dbc3-49eb-3e2562638d49@bunyatech.com.au> <AB510253-52D9-469C-B06E-5EC73C5F188E@kronometrix.org> <fd9991c4e6aaccb812a59ff86c9c8564ebd1d767.camel@freebsd.org> <74E3E782-8481-4B5B-A0AF-A04590C27D6D@kronometrix.org> <790afcb5f0809a89b45982958a85f1539fec05c7.camel@freebsd.org> <36088812-2135-4433-BC49-0BC433EC6767@kronometrix.org> <c52f9d9ab358ac0dc09af411bf97625945579b4e.camel@freebsd.org> <86CC4711-47AC-45C6-B6D3-71C9FFDD4A91@kronometrix.org> <BE321299-8569-4B2E-98FD-FD5210E1B6AF@kronometrix.org> <A9FD7D2B-9382-4EAE-B245-5F4DE643DBB7@gromit.dlib.vt.edu> <C93E2C64-6280-464D-AB5F-B1E968690CEF@kronometrix.org> <2ec7d7f63de31065b9cab396c662fe24f0107078.camel@freebsd.org> <BD0BE075-9E69-4CB0-826A-5DF2D160E9B1@kronometrix.org> <d71fc4e3db26242ffa817814d6cd92b8899fc2ab.camel@freebsd.org> <EF94BC84-4B8D-455C-952F-4FD1CC5557CE@kronometrix.org> <2AC05799-7D11-4200-8D16-38E3718470BB@kronometrix.org> <91E26684-07A0-4F03-92BC-8D49359B1358@kronometrix.org> <5F33E59B-7EA5-4B8B-A95A-CD1FB569ACDC@kronometrix.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2019-07-18 at 00:59 +0300, Stefan Parvu wrote:
> $ dmesg | grep nxp
> nxprtc0: <NXP PCF2129 RTC> at addr 0xa2 on iicbus0
> nxprtc0: WARNING: RTC battery failed; time is invalid
> nxprtc0: registered as a time-of-day clock, resolution 0.015625s
> nxprtc0: RTC clock not running
> 
> Stefan Parvu
> sparvu@kronometrix.org

Why does it claim to have found a PCF2129 when the rpi i2c overlay only
has an entry for 2127?  The driver will believe whatever is in the dts
compatible string, it has no way to ask the chip at runtime what model
it is.

-- Ian




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6a39f74088d2984b5426e8585b5f7e864a6766f8.camel>