From: Guo Ren <ren_guo@c-sky.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: tglx@linutronix.de, jason@lakedaemon.net, marc.zyngier@arm.com,
robh+dt@kernel.org, mark.rutland@arm.com, anurup.m@huawei.com,
Jonathan.Cameron@huawei.com, will.deacon@arm.com,
zhangshaokun@hisilicon.com, jhogan@kernel.org,
paul.burton@mips.com, peterz@infradead.org, f.fainelli@gmail.com,
arnd@arndb.de, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH V9 3/8] clocksource: add C-SKY SMP timer
Date: Fri, 5 Oct 2018 00:14:32 +0800 [thread overview]
Message-ID: <20181004161431.GA30844@guoren-Inspiron-7460> (raw)
In-Reply-To: <49238cda-d12c-7d3f-9333-296527d94f12@linaro.org>
On Tue, Oct 02, 2018 at 09:59:42AM +0200, Daniel Lezcano wrote:
> On 02/10/2018 07:40, Guo Ren wrote:
> [ ... ]
>
> >>
> >> irq = irq_of_parse_and_map(np, 0);
> >> if (irq <= 0)
> >> return -EINVAL;
> > panic();
> > I want a panic here. Return will make debug confused and directly tell
> > the people where is wrong. It's root-timer for us and it must bootup.
> >
> > If it's a co-timer, I also think return is good.
>
> We don't need a panic in case of failure. If the board as an alternate
> timer it should be able to boot, that is the general rule of thumb for
> these drivers in this directory.
>
> The init timer functions will be called via the timer_probe() which
> browse the timer_of_table (the one with all entries for the
> TIMER_OF_DECLARE macros).
>
> You can see in the code below (from timer_probe.c), there is an error
> message emitted if the driver fails to initialize and another one much
> stronger if no timer was initialize.
>
> This is enough trace IMO.
>
> void __init timer_probe(void)
> {
> struct device_node *np;
> const struct of_device_id *match;
> of_init_fn_1_ret init_func_ret;
> unsigned timers = 0;
> int ret;
>
> for_each_matching_node_and_match(np, __timer_of_table, &match) {
> if (!of_device_is_available(np))
> continue;
>
> init_func_ret = match->data;
>
> ret = init_func_ret(np);
> if (ret) {
> pr_err("Failed to initialize '%pOF': %d\n", np,
> ret);
> continue;
> }
>
> timers++;
Ok, let other timers boot up as possible and no panic for csky timer.
Guo Ren
next prev parent reply other threads:[~2018-10-04 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 1:35 [PATCH V9 0/8] C-SKY(csky) Linux Kernel Drivers Guo Ren
2018-10-01 1:35 ` [PATCH V9 1/8] irqchip: add C-SKY SMP interrupt controller Guo Ren
2018-10-01 1:35 ` [PATCH V9 2/8] dt-bindings: interrupt-controller: C-SKY SMP intc Guo Ren
2018-10-01 1:35 ` [PATCH V9 3/8] clocksource: add C-SKY SMP timer Guo Ren
2018-10-01 9:14 ` Daniel Lezcano
2018-10-02 5:40 ` Guo Ren
2018-10-02 7:59 ` Daniel Lezcano
2018-10-04 16:14 ` Guo Ren [this message]
2018-10-01 1:35 ` [PATCH V9 4/8] dt-bindings: timer: C-SKY Multi-processor timer Guo Ren
2018-10-01 1:36 ` [PATCH V9 5/8] dt-bindings: interrupt-controller: C-SKY APB intc Guo Ren
2018-10-01 1:36 ` [PATCH V9 6/8] irqchip: add C-SKY APB bus interrupt controller Guo Ren
2018-10-01 1:36 ` [PATCH V9 7/8] dt-bindings: timer: gx6605s SOC timer Guo Ren
2018-10-01 1:36 ` [PATCH V9 8/8] clocksource: add gx6605s SOC system timer Guo Ren
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=20181004161431.GA30844@guoren-Inspiron-7460 \
--to=ren_guo@c-sky.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anurup.m@huawei.com \
--cc=arnd@arndb.de \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jason@lakedaemon.net \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=paul.burton@mips.com \
--cc=peterz@infradead.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=zhangshaokun@hisilicon.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