public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux PM list <linux-pm@vger.kernel.org>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] clocksource: sh_cmt: Only perform clocksource suspend/resume if enabled
Date: Wed, 05 Aug 2015 18:59:21 +0200	[thread overview]
Message-ID: <55C240E9.1070205@linaro.org> (raw)
In-Reply-To: <CAMuHMdU+dwETiSk4=rgpykbJt03Fe4dnSmHYJP6G_xC4M45N3w@mail.gmail.com>

On 08/05/2015 03:56 PM, Geert Uytterhoeven wrote:
> Hi Daniel,
>
> On Thu, Jul 16, 2015 at 4:03 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>> On Thu, Jul 16, 2015 at 3:41 PM, Daniel Lezcano
>> <daniel.lezcano@linaro.org> wrote:
>>> do you mean to test if the patch [1] solves your problem.
>>>
>>>    -- Daniel
>>>
>>> [1] https://lkml.org/lkml/2015/1/16/81
>>
>> I'll give it a try after my holidays...
>
> Apparently that patch was integrated in v4.2-rc1, while I still see the problem
> on recent kernels.
>
> Furthermore, that patch handles clockevents, not clocksources.
> struct clocksource doesn't seem to have a way to check if it's enabled,
> so I still need my patch.

Hmm, I see. I will take this patch as a fix then.

Thanks.
   -- Daniel


-- 
  <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:[~2015-08-05 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 11:41 [PATCH v2] clocksource: sh_cmt: Only perform clocksource suspend/resume if enabled Geert Uytterhoeven
2015-07-16 13:41 ` Daniel Lezcano
2015-07-16 14:03   ` Geert Uytterhoeven
2015-08-05 13:56     ` Geert Uytterhoeven
2015-08-05 16:59       ` Daniel Lezcano [this message]

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=55C240E9.1070205@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --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