From: Stephen Boyd <sboyd@codeaurora.org>
To: Paul Walmsley <pwalmsley@nvidia.com>, Tony Lindgren <tony@atomide.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Nishanth Menon <nm@ti.com>,
khilman@linaro.org
Subject: Re: regression: Clock changes in next-20141205 break at least omap4
Date: Tue, 16 Dec 2014 11:01:02 -0800 [thread overview]
Message-ID: <5490816E.7060706@codeaurora.org> (raw)
In-Reply-To: <548F8B70.2060803@nvidia.com>
On 12/15/2014 05:31 PM, Paul Walmsley wrote:
>
> I just took a quick glance at Tero's second patch, and it looks like a
> hack to me. Better to fix the problem in the core CCF code if
> possible. I don't think there's any reason why a PLL couldn't have
> just one parent clock. But I'm fine with merging it as a short-term
> fix if fixing the core code is difficult or risky.
Can you describe what's wrong? Does the PLL have a mux with two inputs
that map to the same clock?
--
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: regression: Clock changes in next-20141205 break at least omap4
Date: Tue, 16 Dec 2014 11:01:02 -0800 [thread overview]
Message-ID: <5490816E.7060706@codeaurora.org> (raw)
In-Reply-To: <548F8B70.2060803@nvidia.com>
On 12/15/2014 05:31 PM, Paul Walmsley wrote:
>
> I just took a quick glance at Tero's second patch, and it looks like a
> hack to me. Better to fix the problem in the core CCF code if
> possible. I don't think there's any reason why a PLL couldn't have
> just one parent clock. But I'm fine with merging it as a short-term
> fix if fixing the core code is difficult or risky.
Can you describe what's wrong? Does the PLL have a mux with two inputs
that map to the same clock?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-12-16 19:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 16:55 regression: Clock changes in next-20141205 break at least omap4 Tony Lindgren
2014-12-05 16:55 ` Tony Lindgren
2014-12-05 18:21 ` Stephen Boyd
2014-12-05 18:21 ` Stephen Boyd
2014-12-05 18:38 ` Tony Lindgren
2014-12-05 18:38 ` Tony Lindgren
[not found] ` <20141212194238.20398.33333@quantum>
[not found] ` <alpine.DEB.2.02.1412122310570.29716@utopia.booyaka.com>
[not found] ` <20141215220224.20398.98259@quantum>
2014-12-16 0:21 ` Paul Walmsley
2014-12-16 0:21 ` Paul Walmsley
2014-12-16 0:38 ` Tony Lindgren
2014-12-16 0:38 ` Tony Lindgren
2014-12-16 1:31 ` Paul Walmsley
2014-12-16 1:31 ` Paul Walmsley
2014-12-16 19:01 ` Stephen Boyd [this message]
2014-12-16 19:01 ` Stephen Boyd
2014-12-16 20:01 ` Paul Walmsley
2014-12-16 20:01 ` Paul Walmsley
2014-12-16 20:23 ` Russell King - ARM Linux
2014-12-16 20:23 ` Russell King - ARM Linux
2014-12-16 20:45 ` Paul Walmsley
2014-12-16 20:45 ` Paul Walmsley
2014-12-16 20:57 ` Russell King - ARM Linux
2014-12-16 20:57 ` Russell King - ARM Linux
2014-12-16 22:25 ` Paul Walmsley
2014-12-16 22:25 ` Paul Walmsley
2014-12-17 9:52 ` Lucas Stach
2014-12-17 9:52 ` Lucas Stach
2014-12-17 11:59 ` Tero Kristo
2014-12-17 11:59 ` Tero Kristo
2014-12-19 16:45 ` Paul Walmsley
2014-12-19 16:45 ` Paul Walmsley
2014-12-18 19:23 ` Paul Walmsley
2014-12-18 19:23 ` Paul Walmsley
2014-12-18 23:37 ` Mike Turquette
2014-12-18 23:37 ` Mike Turquette
2014-12-19 2:15 ` Paul Walmsley
2014-12-19 2:15 ` Paul Walmsley
2014-12-20 0:23 ` Mike Turquette
2014-12-20 0:23 ` Mike Turquette
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=5490816E.7060706@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=pwalmsley@nvidia.com \
--cc=tomeu.vizoso@collabora.com \
--cc=tony@atomide.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.