All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jordan Crouse <jcrouse@codeaurora.org>
To: Rob Clark <robdclark@gmail.com>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	freedreno@lists.freedesktop.org
Subject: Re: [Freedreno] PSA: ifc6410 / upstream kernel / clock status stuck at 'off' issues
Date: Thu, 06 Nov 2014 13:09:58 -0700	[thread overview]
Message-ID: <545BD596.6000403@codeaurora.org> (raw)
In-Reply-To: <CAF6AEGuvyRC8_yrVH4oZz-mnj5FDQM4wz6a2nHagzY2cbEWatg@mail.gmail.com>

On 11/06/2014 10:58 AM, Rob Clark wrote:
> Just FYI, newer ifc6410 boards which are shipping with android 4.4
> bootloaders, seem to have an issue with upstream kernel.
>
> If you are seeing problems like:
>
> -------
> [    2.472644] WARNING: CPU: 3 PID: 51 at
> drivers/clk/qcom/clk-branch.c:97 clk_branch_wait+0xd0/0x120()
> [    2.472659] mdp_clk status stuck at 'off'
> [    2.472667] Modules linked in:
> [    2.472688] CPU: 3 PID: 51 Comm: kworker/u8:1 Not tainted 3.18.0-rc1 #912
> [    2.472719] Workqueue: deferwq deferred_probe_work_func
> [    2.472784] [<c02160fc>] (unwind_backtrace) from [<c0211afc>]
> (show_stack+0x10/0x14)
> [    2.472824] [<c0211afc>] (show_stack) from [<c0909864>]
> (dump_stack+0x88/0x98)
> [    2.472859] [<c0909864>] (dump_stack) from [<c0249fa4>]
> (warn_slowpath_common+0x6c/0x88)
> [    2.472889] [<c0249fa4>] (warn_slowpath_common) from [<c0249ff0>]
> (warn_slowpath_fmt+0x30/0x40)
> [    2.472917] [<c0249ff0>] (warn_slowpath_fmt) from [<c0792964>]
> (clk_branch_wait+0xd0/0x120)
> [    2.472952] [<c0792964>] (clk_branch_wait) from [<c0787f78>]
> (__clk_enable+0x5c/0x9c)
> [    2.472975] [<c0787f78>] (__clk_enable) from [<c0788464>]
> (clk_enable+0x18/0x2c)
> [    2.473013] [<c0788464>] (clk_enable) from [<c054121c>]
> (mdp4_enable+0xe4/0x110)
> [    2.473048] [<c054121c>] (mdp4_enable) from [<c0541270>]
> (mdp4_hw_init+0x28/0x344)
> [    2.473075] [<c0541270>] (mdp4_hw_init) from [<c0547e60>]
> (msm_load+0x1c8/0x34c)
> [    2.473108] [<c0547e60>] (msm_load) from [<c052596c>]
> (drm_dev_register+0xa8/0x104)
> [    2.473136] [<c052596c>] (drm_dev_register) from [<c0527824>]
> (drm_platform_init+0x44/0xdc)
> [    2.473166] [<c0527824>] (drm_platform_init) from [<c0566538>]
> (try_to_bring_up_master.part.3+0xc8/0x108)
> [    2.473190] [<c0566538>] (try_to_bring_up_master.part.3) from
> [<c0566620>] (component_master_add_with_match+0xa8/0x120)
> -------
>
> Then the solution for now is to downgrade to version 4.2 rpm fw:
>
>     fastboot flash rpm rpm.mbn
>
> with rpm.mbn from Bootloaders_4.2_880261_V1.0.zip on inforce techweb site.
>
> I've no idea what the root cause is, or why we don't see this on the
> downstream kernel (but I guess it is easier for someone with docs to
> debug).  But sooner or later others will hit the same issue so I
> figured I should send this known workaround to an archived mailing
> list so someone googling for the error has some chance to find it ;-)

Just so you know what is happening here this interesting combination
of error messages is a roundabout way of telling you that you tried
to enable a clock while the regulator was off.

Jordan
-- 
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2014-11-06 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 17:58 PSA: ifc6410 / upstream kernel / clock status stuck at 'off' issues Rob Clark
2014-11-06 20:09 ` Jordan Crouse [this message]
2014-11-06 20:47   ` [Freedreno] " Rob Clark

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=545BD596.6000403@codeaurora.org \
    --to=jcrouse@codeaurora.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robdclark@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.