linux-rtc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 30 Jan 2020 11:47:56 +0100	[thread overview]
Message-ID: <20200130104756.GC3583@piout.net> (raw)
In-Reply-To: <CAA=hcWQoY95oPbLYyD306_wxmj=GU57t8m-m_kWwyy5-7Quj=Q@mail.gmail.com>

On 30/01/2020 13:36:26+1100, JH wrote:
> Hi Alexandre,
> 
> Thanks for your response.
> 
> On 1/12/20, Alexandre Belloni <alexandre.belloni@bootlin.com> wrote:
> > Hi,
> >
> > On 02/01/2020 19:40:10+1100, JH wrote:
> >> Hi,
> >>
> >> I am running kernel 4.19 on imx6, could anyone help for clues what
> >> that error is about? What I could be missing and how to fix it?
> >>
> >
> > I'd say that you have an issue with the 32k clock or tamper detection,
> > have a look at this commit:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd7f3a249dbed2858e6c2f30e5be7f1f7a709ee2
> 
> Is that a patch for 4.19.75? Or where can I download the patch for 4.19.75?
> 

This patch was included in 4.19. It introduced the message you are
seeing and the commit message explains why you are seeing it.


-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-01-30 10:47 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 [this message]
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
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=20200130104756.GC3583@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).