From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: JH <jupiter.hce@gmail.com>
Cc: linux-rtc@vger.kernel.org
Subject: Re: rtc rtc0: Timeout trying to get valid LPSRT Counter read
Date: Fri, 31 Jan 2020 15:13:24 +0100 [thread overview]
Message-ID: <20200131141324.GD3515@piout.net> (raw)
In-Reply-To: <CAA=hcWQoacmPsi-VH3B1BGFHJhHi1a-tLaJXBiwAn03E7BiTiQ@mail.gmail.com>
On 31/01/2020 16:27:15+1100, JH wrote:
> Hi Alexandre,
>
> On 1/31/20, Alexandre Belloni <alexandre.belloni@bootlin.com> wrote:
> >> So it was already included in 4.19, I don't need to patch it, that is
> >> good :-). Sorry I am still not clear how to stop that error message of
> >> "rtc rtc0: Timeout trying to get valid LPSRT Counter read", the
> >> message says "To avoid kernel hangs, put in timeouts", I am running
> >> kernel 4.19.75 on iMX6, where should I put in timeouts?
> >>
> >
> > The patch is adding the timeouts, without them, your kernel would be
> > freezing. I'd say your issue is the 32k clock.
>
> Did you mean that is the issue of the hardware setup IMX6ULL for 32k
> RTC_XTALI? That is nominal frequency 32.768 kHz for IMX6ULL EVK and
> customized devices. Change to which frequency (64k?) can fix the
> problem and remove the error message?
>
I can't help much more without seeing the schematics of your particular
board. 32k is the correct frequency but are your sure it is going to the
RTC? Are you sure you have power on VDD_SNVS_IN? Was there a security
violation detected?
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-31 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 8:40 rtc rtc0: Timeout trying to get valid LPSRT Counter read JH
2020-01-12 11:03 ` Alexandre Belloni
2020-01-30 2:36 ` JH
2020-01-30 10:47 ` Alexandre Belloni
2020-01-30 11:27 ` JH
2020-01-30 14:40 ` Alexandre Belloni
2020-01-31 5:27 ` JH
2020-01-31 14:13 ` Alexandre Belloni [this message]
2020-01-31 23:36 ` JH
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=20200131141324.GD3515@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=jupiter.hce@gmail.com \
--cc=linux-rtc@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;
as well as URLs for NNTP newsgroup(s).