From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: laurent.pinchart+renesas@ideasonboard.com,
geert+renesas@glider.be, linux-sh@vger.kernel.org,
viresh.kumar@linaro.org, linux-kernel@vger.kernel.org,
chris.brandt@renesas.com, horms+renesas@verge.net.au,
tglx@linutronix.de
Subject: Re: [PATCH] clocksource: sh_mtu2: Fix multiple shutdown call issue
Date: Wed, 28 Oct 2015 10:22:09 +0100 [thread overview]
Message-ID: <563093C1.5060400@linaro.org> (raw)
In-Reply-To: <20151028014323.29894.70699.sendpatchset@little-apple>
On 10/28/2015 02:43 AM, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> On the r7s72100 Genmai board the MTU2 driver currently triggers a common
> clock framework WARN_ON(enable_count) when disabling the clock due to
> the MTU2 driver after recent callback rework may call ->set_state_shutdown()
> multiple times. A similar issue was spotted for the TMU driver and fixed in:
> 452b132 clocksource/drivers/sh_tmu: Fix traceback spotted in -next
>
> On r7s72100 Genmai v4.3-rc7 built with shmobile_defconfig spits out the
> following during boot:
>
> sh_mtu2 fcff0000.timer: ch0: used for clock events
Applied.
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
next prev parent reply other threads:[~2015-10-28 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 1:43 [PATCH] clocksource: sh_mtu2: Fix multiple shutdown call issue Magnus Damm
2015-10-28 2:42 ` Viresh Kumar
2015-10-28 9:22 ` Daniel Lezcano [this message]
2015-10-30 13:35 ` Laurent Pinchart
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=563093C1.5060400@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=chris.brandt@renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
/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).