All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stefan Agner <stefan@agner.ch>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-clk@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH] clk: imx7d: do not set the parent of IMX7D_ENET_AXI_ROOT_SRC
Date: Thu, 11 Aug 2016 15:28:42 -0700	[thread overview]
Message-ID: <20160811222842.GM2996@codeaurora.org> (raw)
In-Reply-To: <CAOMZO5BjdhCDNU-Vr7OT81ag0LqgFQ3+oP1D_o0FUOZVafneqQ@mail.gmail.com>

On 08/10, Fabio Estevam wrote:
> Hi Mike,
> 
> On Fri, Jul 15, 2016 at 10:53 AM, Fabio Estevam <fabio.estevam@nxp.com> wrote:
> > Booting the kernel on a imx7s-warp leads to several warnings like these:
> >
> > [    0.000000] ------------[ cut here ]------------
> > [    0.000000] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3536 lock_release+0x2f8/0x330
> > [    0.000000] releasing a pinned lock
> >
> > [    0.000000] ------------[ cut here ]------------
> > [    0.000000] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2722 trace_hardirqs_on_caller+0x1ac/0x1f4
> > [    0.000000] DEBUG_LOCKS_WARN_ON(unlikely(early_boot_irqs_disabled))
> >
> > [    0.000000] ---[ end trace cb88537fdc8fa201 ]---
> > [    0.000000] bad: scheduling from the idle thread!
> > [    0.000000] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7-next-20160715 #404
> >
> > [    0.000000] ------------[ cut here ]------------
> > [    0.000000] WARNING: CPU: 0 PID: 0 at kernel/time/sched_clock.c:179 sched_clock_register+0x44/0x1f8
> > [    0.000000] Modules linked in:
> >
> > [    0.000591] ------------[ cut here ]------------
> > [    0.000610] WARNING: CPU: 0 PID: 0 at kernel/time/sched_clock.c:179 sched_clock_register+0x44/0x1f8
> >
> > [    0.002084] ------------[ cut here ]------------
> > [    0.002104] WARNING: CPU: 0 PID: 0 at init/main.c:576 start_kernel+0x258/0x3b0
> > [    0.002114] Interrupts were enabled early
> >
> >
> > This fix is along the same lines as 5e33ebff7edd ("clk: imx7d: do not
> > set parent of ethernet time/ref clocks") and the explanation from that
> > commit is:
> >
> > "The reason for the warning is that setting the parent enables the ENET
> >  PLL since we are using CLK_OPS_PARENT_ENABLE. Enabling the ENET PLL can
> >  cause clk_pllv3_wait_lock to sleep. See also:
> >  commit fc8726a2c021 ("clk: core: support clocks which requires parents
> >  enable (part 2)")."
> >
> > imx7s-warp does not even use the FEC interface, so we should not really
> > configure the parent of IMX7D_ENET_AXI_ROOT_SRC in the common MX7 clock
> > driver code.
> >
> > The dts file should use the assigned-clocks/assigned-clock-parents method,
> > so simply remove the configuration of IMX7D_ENET_AXI_ROOT_SRC parent.
> >
> > Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> 
> Do you think this one could be applied to 4.8-rc?
>

Is there a "Fixes:" tag that can be applied here? Does this
depend on some sort of DTS changes to add assigned clocks and
parents?

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

WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: imx7d: do not set the parent of IMX7D_ENET_AXI_ROOT_SRC
Date: Thu, 11 Aug 2016 15:28:42 -0700	[thread overview]
Message-ID: <20160811222842.GM2996@codeaurora.org> (raw)
In-Reply-To: <CAOMZO5BjdhCDNU-Vr7OT81ag0LqgFQ3+oP1D_o0FUOZVafneqQ@mail.gmail.com>

On 08/10, Fabio Estevam wrote:
> Hi Mike,
> 
> On Fri, Jul 15, 2016 at 10:53 AM, Fabio Estevam <fabio.estevam@nxp.com> wrote:
> > Booting the kernel on a imx7s-warp leads to several warnings like these:
> >
> > [    0.000000] ------------[ cut here ]------------
> > [    0.000000] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3536 lock_release+0x2f8/0x330
> > [    0.000000] releasing a pinned lock
> >
> > [    0.000000] ------------[ cut here ]------------
> > [    0.000000] WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:2722 trace_hardirqs_on_caller+0x1ac/0x1f4
> > [    0.000000] DEBUG_LOCKS_WARN_ON(unlikely(early_boot_irqs_disabled))
> >
> > [    0.000000] ---[ end trace cb88537fdc8fa201 ]---
> > [    0.000000] bad: scheduling from the idle thread!
> > [    0.000000] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.7.0-rc7-next-20160715 #404
> >
> > [    0.000000] ------------[ cut here ]------------
> > [    0.000000] WARNING: CPU: 0 PID: 0 at kernel/time/sched_clock.c:179 sched_clock_register+0x44/0x1f8
> > [    0.000000] Modules linked in:
> >
> > [    0.000591] ------------[ cut here ]------------
> > [    0.000610] WARNING: CPU: 0 PID: 0 at kernel/time/sched_clock.c:179 sched_clock_register+0x44/0x1f8
> >
> > [    0.002084] ------------[ cut here ]------------
> > [    0.002104] WARNING: CPU: 0 PID: 0 at init/main.c:576 start_kernel+0x258/0x3b0
> > [    0.002114] Interrupts were enabled early
> >
> >
> > This fix is along the same lines as 5e33ebff7edd ("clk: imx7d: do not
> > set parent of ethernet time/ref clocks") and the explanation from that
> > commit is:
> >
> > "The reason for the warning is that setting the parent enables the ENET
> >  PLL since we are using CLK_OPS_PARENT_ENABLE. Enabling the ENET PLL can
> >  cause clk_pllv3_wait_lock to sleep. See also:
> >  commit fc8726a2c021 ("clk: core: support clocks which requires parents
> >  enable (part 2)")."
> >
> > imx7s-warp does not even use the FEC interface, so we should not really
> > configure the parent of IMX7D_ENET_AXI_ROOT_SRC in the common MX7 clock
> > driver code.
> >
> > The dts file should use the assigned-clocks/assigned-clock-parents method,
> > so simply remove the configuration of IMX7D_ENET_AXI_ROOT_SRC parent.
> >
> > Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> 
> Do you think this one could be applied to 4.8-rc?
>

Is there a "Fixes:" tag that can be applied here? Does this
depend on some sort of DTS changes to add assigned clocks and
parents?

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

  reply	other threads:[~2016-08-11 22:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 13:53 [PATCH] clk: imx7d: do not set the parent of IMX7D_ENET_AXI_ROOT_SRC Fabio Estevam
2016-07-15 13:53 ` Fabio Estevam
2016-08-10 11:37 ` Fabio Estevam
2016-08-10 11:37   ` Fabio Estevam
2016-08-11 22:28   ` Stephen Boyd [this message]
2016-08-11 22:28     ` Stephen Boyd
2016-08-11 23:53     ` Fabio Estevam
2016-08-11 23:53       ` Fabio Estevam
2016-08-11 23:57       ` Stefan Agner
2016-08-11 23:57         ` Stefan Agner
2016-08-12  1:35         ` Fabio Estevam
2016-08-12  1:35           ` Fabio Estevam
2016-08-12  1:45           ` Stephen Boyd
2016-08-12  1:45             ` Stephen Boyd
2016-08-12  1:47             ` Fabio Estevam
2016-08-12  1:47               ` Fabio Estevam
2016-08-13  0:57 ` Stephen Boyd
2016-08-13  0:57   ` Stephen Boyd

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=20160811222842.GM2996@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    /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.