mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	od@zcrc.me, linux-kernel@vger.kernel.org,
	Maarten ter Huurne <maarten@treewalker.org>,
	Mathieu Malaterre <malat@debian.org>,
	Artur Rojek <contact@artur-rojek.eu>
Subject: Re: [PATCH] clocksource: Add driver for the Ingenic JZ47xx OST
Date: Thu, 7 Nov 2019 20:39:08 +0100	[thread overview]
Message-ID: <a7aa0b0d-e52f-564f-11ef-a8b74f9f1ac8@linaro.org> (raw)
In-Reply-To: <54210a015f148218e11e7f3c1d107192@crapouillou.net>

On 07/11/2019 16:56, Paul Cercueil wrote:
> Hi Daniel,
> 
> On 2019-08-16 16:54, Daniel Lezcano wrote:
>> On 09/08/2019 14:38, Paul Cercueil wrote:
>>> From: Maarten ter Huurne <maarten@treewalker.org>
>>>
>>> OST is the OS Timer, a 64-bit timer/counter with buffered reading.
>>>
>>> SoCs before the JZ4770 had (if any) a 32-bit OST; the JZ4770 and
>>> JZ4780 have a 64-bit OST.
>>>
>>> This driver will register both a clocksource and a sched_clock to the
>>> system.
>>>
>>> Signed-off-by: Maarten ter Huurne <maarten@treewalker.org>
>>> Signed-off-by: Paul Cercueil <paul@crapouillou.net>
>>> Tested-by: Mathieu Malaterre <malat@debian.org>
>>> Tested-by: Artur Rojek <contact@artur-rojek.eu>
>>> ---
>>>
>>
>> [ ... ]
>>
>>> +    err = clocksource_register_hz(cs, rate);
>>> +    if (err) {
>>> +        dev_err(dev, "clocksource registration failed: %d\n", err);
>>> +        clk_disable_unprepare(ost->clk);
>>> +        return err;
>>> +    }
>>> +
>>> +    /* Cannot register a sched_clock with interrupts on */
>>
>> Aren't they already disabled?
> 
> Sorry for the late reply.
> 
> No, they are not already disabled; this is what I get if I comment out
> the local_irq_save()/local_irq_restore():
> 
> [    0.361014] clocksource: ingenic-ost: mask: 0xffffffff max_cycles:
> 0xffffffff, max_idle_ns: 159271703898 ns
> [    0.361515] clocksource: Switched to clocksource ingenic-ost
> [    0.361686] ------------[ cut here ]------------
> [    0.361893] WARNING: CPU: 0 PID: 1 at kernel/time/sched_clock.c:179
> sched_clock_register+0x7c/0x2e4
> [    0.362174] CPU: 0 PID: 1 Comm: swapper Not tainted 5.4.0-rc5+ #461
> [    0.362330] Stack : 80744558 80069b44 80770000 00000000 00000000
> 00dfd7a7 806e6db4 8106bb74
> [    0.362619]         806f0000 81067ca4 806f31c7 80769478 00000020
> 10000400 8106bb20 00dfd7a7
> [    0.362906]         00000000 00000000 80780000 00000000 00000007
> 00000001 00000049 3563722d
> [    0.363191]         8106ba61 00000000 ffffffff 00000010 806f0000
> 00000000 00000000 806f0000
> [    0.363477]         00000020 00000000 80714534 80770000 00000002
> 80319154 00000000 80770000
> [    0.363762]         ...
> [    0.363906] Call Trace:
> [    0.364087] [<8001af14>] show_stack+0x40/0x128
> [    0.364289] [<8002fd88>] __warn+0xb8/0xe0
> [    0.364478] [<8002fe14>] warn_slowpath_fmt+0x64/0xc0
> [    0.364678] [<8072b1c8>] sched_clock_register+0x7c/0x2e4
> [    0.364895] [<8073c874>] ingenic_ost_probe+0x224/0x248
> [    0.365090] [<803d5394>] platform_drv_probe+0x40/0x94
> [    0.365526] [<803d362c>] really_probe+0x104/0x374
> [    0.365743] [<803d3ff0>] device_driver_attach+0x78/0x80
> [    0.365938] [<803d4070>] __driver_attach+0x78/0x118
> [    0.366129] [<803d1700>] bus_for_each_dev+0x7c/0xc8
> [    0.366318] [<803d226c>] bus_add_driver+0x1bc/0x204
> [    0.366513] [<803d4878>] driver_register+0x84/0x14c
> [    0.366717] [<8073a144>] __platform_driver_probe+0x98/0x140
> [    0.366931] [<80724e38>] do_one_initcall+0x84/0x1b4
> [    0.367126] [<807250cc>] kernel_init_freeable+0x164/0x240
> [    0.367318] [<805df75c>] kernel_init+0x10/0xf8
> [    0.367510] [<8001542c>] ret_from_kernel_thread+0x14/0x1c
> [    0.367722] ---[ end trace 7fedf00408fa3bed ]---
> [    0.367985] sched_clock: 32 bits at 12MHz, resolution 83ns, wraps
> every 178956970966ns
> 
> At kernel/time/sched_clock.c:179 there is:
> WARN_ON(!irqs_disabled());

That is strange, no drivers is doing that and no warning is appearing.

Isn't missing a local_irq_disable in the code path in the stack above?

>>> +    local_irq_save(flags);
>>> +    if (soc_info->is64bit)
>>> +        sched_clock_register(ingenic_ost_read_cntl, 32, rate);
>>> +    else
>>> +        sched_clock_register(ingenic_ost_read_cnth, 32, rate);
>>> +    local_irq_restore(flags);
>>> +
>>> +    return 0;
>>> +}
>>> +


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2019-11-07 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 12:38 Paul Cercueil
2019-08-16 14:54 ` Daniel Lezcano
2019-11-07 15:56   ` Paul Cercueil
2019-11-07 19:39     ` Daniel Lezcano [this message]
2019-11-07 19:57       ` Paul Cercueil
2019-11-07 20:22         ` Daniel Lezcano
2019-11-07 20:34           ` Paul Cercueil
2019-12-10  9:19             ` Daniel Lezcano

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=a7aa0b0d-e52f-564f-11ef-a8b74f9f1ac8@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=contact@artur-rojek.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten@treewalker.org \
    --cc=malat@debian.org \
    --cc=od@zcrc.me \
    --cc=paul@crapouillou.net \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®