From: "J, KEERTHY" <j-keerthy@ti.com>
To: <daniel.lezcano@linaro.org>, <tglx@linutronix.de>
Cc: <lokeshvutla@ti.com>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <baolin.wang@linaro.org>,
<d-gerlach@ti.com>, <tony@atomide.com>,
<grygorii.strashko@ti.com>, <t-kristo@ti.com>
Subject: Re: [PATCH v2] clocksource: ti-32k: Add CLOCK_SOURCE_SUSPEND_NONSTOP flag for non-am43 SoCs
Date: Tue, 28 Aug 2018 17:14:00 +0530 [thread overview]
Message-ID: <12b80b5f-3dd8-793e-75b2-94d2a0248d3e@ti.com> (raw)
In-Reply-To: <1533734099-1398-1-git-send-email-j-keerthy@ti.com>
On 8/8/2018 6:44 PM, Keerthy wrote:
> The 32k clocksource is NONSTOP for non-am43 SoCs. Hence
> add the flag for all the other SoCs.
A gentle ping on this one.
>
> Reported-by: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> Acked-by: Tony Lindgren <tony@atomide.com>
> ---
>
> Changes in v2:
>
> * Changed am43 compatible to more generic ti,am43 to cover epos boards.
> * Added Tony's Ack.
>
> drivers/clocksource/timer-ti-32k.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/clocksource/timer-ti-32k.c b/drivers/clocksource/timer-ti-32k.c
> index 29e2e1a..dd09171 100644
> --- a/drivers/clocksource/timer-ti-32k.c
> +++ b/drivers/clocksource/timer-ti-32k.c
> @@ -97,6 +97,9 @@ static int __init ti_32k_timer_init(struct device_node *np)
> return -ENXIO;
> }
>
> + if (!of_machine_is_compatible("ti,am43"))
> + ti_32k_timer.cs.flags |= CLOCK_SOURCE_SUSPEND_NONSTOP;
> +
> ti_32k_timer.counter = ti_32k_timer.base;
>
> /*
>
next prev parent reply other threads:[~2018-08-28 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 13:14 Keerthy
2018-08-28 11:44 ` J, KEERTHY [this message]
2018-08-28 12:11 ` Daniel Lezcano
2018-08-29 15:17 ` 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=12b80b5f-3dd8-793e-75b2-94d2a0248d3e@ti.com \
--to=j-keerthy@ti.com \
--cc=baolin.wang@linaro.org \
--cc=d-gerlach@ti.com \
--cc=daniel.lezcano@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=t-kristo@ti.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®