linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux-Next <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: linux-next: Tree for Jan 30 (clk related WARNING on arm)
Date: Sun, 01 Feb 2015 10:49:54 -0800	[thread overview]
Message-ID: <54CE7552.9070600@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdV64QF=WNxOgFn3mzpSCrA8amr6wrWQJFaZsUYozTVW=Q@mail.gmail.com>

On 02/01/2015 01:23 AM, Geert Uytterhoeven wrote:
> On Fri, Jan 30, 2015 at 8:07 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> On Fri, Jan 30, 2015 at 06:02:09PM +1100, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20150129:
>>>
>>> The arm-soc gained conflicts against the arm-current and arm trees.
>>>
>>> The spi tree gained a build failure for which I reverted a commit.
>>>
>>> Non-merge commits (relative to Linus' tree): 6300
>>>   6348 files changed, 255117 insertions(+), 131620 deletions(-)
>>>
>>> ----------------------------------------------------------------------------
>>>
>> I see the following runtime warning repeatedly (with different call
>> paths to vexpress_osc_round_rate) with my qemu vexpress test.
>>
>> Bisect points to commit cb75a8fcd14e71 ("clk: Add rate constraints to clocks").
>>
>> Guenter
>>
>> ---
>> WARNING: CPU: 0 PID: 1 at drivers/clk/versatile/clk-vexpress-osc.c:47
>> vexpress_osc_round_rate+0x58/0x64()
>
> See also the thread started at
> http://www.spinics.net/lists/linux-doc/msg28017.html
>
> Will try the patch after FOSDEM.
>
Hi Geert,

thanks a lot for the pointer.

Stephen Boyd's patch ("clk: Assign a requested rate by default")
fixes the problem seen in my test. Stephen, please feel free to add

Tested-by: Guenter Roeck <linux@roeck-us.net>

to that patch.

Thanks,
Guenter


      reply	other threads:[~2015-02-01 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30  7:02 linux-next: Tree for Jan 30 Stephen Rothwell
2015-01-30 14:25 ` linux-next: Tree for Jan 30 (build failures) Guenter Roeck
2015-01-30 16:01   ` Oleksij Rempel
2015-01-30 17:30     ` Guenter Roeck
2015-01-31  8:13       ` [PATCH] ARM: clocksource: whitelist asm9260_timer driver for ARM Oleksij Rempel
2015-01-30 16:15   ` linux-next: Tree for Jan 30 (build failures) Boris Brezillon
2015-01-30 19:07 ` linux-next: Tree for Jan 30 (clk related WARNING on arm) Guenter Roeck
2015-02-01  9:23   ` Geert Uytterhoeven
2015-02-01 18:49     ` Guenter Roeck [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=54CE7552.9070600@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tomeu.vizoso@collabora.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;
as well as URLs for NNTP newsgroup(s).