From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Guilherme Costa <glhrmcosta91@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: __clksrc_of_table and "clocksource_probe: no matching clocksources found"
Date: Tue, 23 Apr 2019 16:17:55 -0400 [thread overview]
Message-ID: <22861.1556050675@turing-police> (raw)
In-Reply-To: <CAD7V0LL95SxGyntSzRLhA5iX3dMfMohQ04+Rde468CbVCtnZKw@mail.gmail.com>
On Tue, 23 Apr 2019 17:07:14 -0300, Guilherme Costa said:
> From the code, we can see that the message was printed because
> clocksources == 0. This implies that there were no matching nodes on
> the device tree,
Right.
> and that acpi_probe_device_table returned 0 (which is correct, seeing
> that the kernel has no ACPI support).
> This leaves me with two questions:
> 1 - Is this message a problem indicator? I'm assuming it is, because
> it's printed with a pr_crit...
Depends. Most systems really want a clocksource of some sort.
> 2 - Why is for_each_matching_node_and_match not getting any matches? I
> did not find where __clksrc_of_table is initialized, so maybe it's
> because it is empty?
My first guess is that your hardware has a busted device tree that doesn't
have an entry pointing at any actual valid hardware clock device. Could
be an incorrect address, or the DT says it's a Frobozz1 clock but the actual
hardware has a Frobozz2 that won't probe using the Frobozz1 driver, or
something else....
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-04-23 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 20:07 __clksrc_of_table and "clocksource_probe: no matching clocksources found" Guilherme Costa
2019-04-23 20:17 ` Valdis Klētnieks [this message]
2019-04-23 20:36 ` Guilherme Costa
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=22861.1556050675@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=glhrmcosta91@gmail.com \
--cc=kernelnewbies@kernelnewbies.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).