From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: linux-mips@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Burton <paul.burton@mips.com>,
MIPS Creator CI20 Development
<mips-creator-ci20-dev@googlegroups.com>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: MIPS: bug: gettimeofday syscall broken on CI20 board
Date: Thu, 28 Nov 2019 16:10:00 +0100 [thread overview]
Message-ID: <C3F683EF-FB6E-43FD-A732-4096BCB9433C@goldelico.com> (raw)
In-Reply-To: <091536b5-6c77-eed4-eec1-82b331332a74@arm.com>
> Am 28.11.2019 um 15:04 schrieb Vincenzo Frascino <vincenzo.frascino@arm.com>:
>
> On 28/11/2019 12:16, H. Nikolaus Schaller wrote:
>> Ah, good question. How do I find out? Checking defconfig did not show any
>> config with R4K or GIC. So it is likely NONE. CONFIG_RTC_DRV_JZ4740=y if that
>> helps.
>
> Try to check what do you have in /sys/devices/system/clocksource.
Ok, have finished another project and could check:
root@letux:~# ls -l /sys/devices/system/clocksource/clocksource0/
total 0
-r--r--r-- 1 root root 4096 Nov 3 17:18 available_clocksource
-rw-r--r-- 1 root root 4096 Nov 3 17:18 current_clocksource
drwxr-xr-x 2 root root 0 Nov 3 17:18 power
lrwxrwxrwx 1 root root 0 Nov 3 17:16 subsystem -> ../../../../bus/clocksource
-rw-r--r-- 1 root root 4096 Nov 3 17:16 uevent
--w------- 1 root root 4096 Nov 3 17:18 unbind_clocksource
root@letux:~# cat /sys/devices/system/clocksource/clocksource0/*
ingenic-timer
ingenic-timer
cat: /sys/devices/system/clocksource/clocksource0/power: Is a directory
cat: /sys/devices/system/clocksource/clocksource0/subsystem: Is a directory
cat: /sys/devices/system/clocksource/clocksource0/unbind_clocksource: Permission denied
root@letux:~#
Does that help?
BR,
Nikolaus
next prev parent reply other threads:[~2019-11-28 15:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 16:21 MIPS: bug: gettimeofday syscall broken on CI20 board? H. Nikolaus Schaller
2019-11-17 13:14 ` MIPS: bug: gettimeofday syscall broken on CI20 board H. Nikolaus Schaller
2019-11-23 7:29 ` H. Nikolaus Schaller
2019-11-26 10:52 ` MIPS: " Vincenzo Frascino
2019-11-27 13:53 ` H. Nikolaus Schaller
2019-11-27 14:29 ` H. Nikolaus Schaller
2019-11-28 12:05 ` Vincenzo Frascino
2019-11-28 12:16 ` H. Nikolaus Schaller
2019-11-28 14:04 ` Vincenzo Frascino
2019-11-28 15:10 ` H. Nikolaus Schaller [this message]
2019-11-28 11:51 ` Vincenzo Frascino
2019-11-28 12:11 ` H. Nikolaus Schaller
2019-11-28 12:21 ` Vincenzo Frascino
2019-11-28 12:33 ` H. Nikolaus Schaller
2019-11-28 13:29 ` Maarten ter Huurne
2019-11-28 13:48 ` H. Nikolaus Schaller
2019-11-28 14:01 ` Vincenzo Frascino
2019-11-28 15:42 ` H. Nikolaus Schaller
2019-11-28 15:07 ` Thomas Bogendoerfer
2019-11-28 15:41 ` H. Nikolaus Schaller
2019-11-28 15:46 ` Vincenzo Frascino
2019-11-28 16:47 ` H. Nikolaus Schaller
2019-11-29 8:57 ` Vincenzo Frascino
2019-11-29 10:53 ` Vincenzo Frascino
2019-11-29 11:51 ` H. Nikolaus Schaller
2019-12-01 3:08 ` [PATCH] Mips32 gettimeofday fix kbuild test robot
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=C3F683EF-FB6E-43FD-A732-4096BCB9433C@goldelico.com \
--to=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=mips-creator-ci20-dev@googlegroups.com \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=vincenzo.frascino@arm.com \
/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).