From: b.brezillon.dev@gmail.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: register fixed-clock only if #clock-cells property is present
Date: Thu, 27 Mar 2014 12:14:01 +0100 [thread overview]
Message-ID: <533407F9.7060509@gmail.com> (raw)
In-Reply-To: <5333F704.7020504@samsung.com>
Hi Sylwester,
Le 27/03/2014 11:01, Sylwester Nawrocki a ?crit :
> Hi Boris,
>
> On 27/03/14 08:58, Boris BREZILLON wrote:
>> This solution solve the problem for this specific case because clks are
>> declared in the correct order in imx DTs.
>> But, even with your patch I think we could see similar issues by
>> reordering DT nodes...
>>
>> The real problem here is that imx platform does not declare the CCM clocks
>> dependencies upon ckil, ckih1 and osc fixed clocks within the DT [1], and
>> retrieve these clocks when initializing the CCM clocks ([2] and [3]).
>>
>> We should try to a add these dependencies in the DT and see if it works.
> While presumably all of us agree the dependencies should be correctly
> specified in dts I think we should minimize possible regressions by
> keeping the clocks registration order as before, i.e. as parsed by the
> kernel from DT. Rather than explicitly reversing it, which does not gain
> us anything AFAICS. Instead we are seeing regressions where new kernels
> stop working with old dtbs.
I totally agree with you on this point: my patch is not a replacement of
yours.
I just wanted to point out that we need to fix DT definitions to avoid these
kind of issues in the future.
>
> I'm going to resend the patch replacing list_add() with list_add_tail(),
> with this the mvebu platform would work and there should be no regression
> on imx and exynos.
>
> Please note that specifying dependencies between CCM on imx and the fixed
> clocks might not be enough. If the fixed clocks get matched on "fixed-clock"
> compatible some clock specifiers (i.e. those using phandle to the CCM) could
> get invalid, since the clocks won't get registered by the ccm driver, but by
> the regular fixed clock driver. That means a phandle to different node would
> need to be used to reference the fixed clock. I'm not sure if this is the case
> for imx, but changes may be needed all over various dts files.
> In addition, we should make sure the kernel works with current and modified
> dtbs.
>
>> [1] http://lxr.free-electrons.com/source/arch/arm/boot/dts/imx6sl.dtsi#L379
>> [2] http://lxr.free-electrons.com/source/arch/arm/mach-imx/clk-imx6q.c#L151
>> [3] http://lxr.free-electrons.com/source/arch/arm/mach-imx/clk.c#L30
next prev parent reply other threads:[~2014-03-27 11:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 18:22 [PATCH] clk: register fixed-clock only if #clock-cells property is present Sylwester Nawrocki
2014-03-26 18:33 ` Fabio Estevam
2014-03-26 19:57 ` Sylwester Nawrocki
2014-03-26 20:14 ` Fabio Estevam
2014-03-26 20:25 ` Gregory CLEMENT
2014-03-26 20:34 ` Fabio Estevam
2014-03-27 7:58 ` Boris BREZILLON
2014-03-27 8:11 ` [PATCH] ARM: imx6/dt: add ccm dependency upon ckil, ckih1 and osc clocks Boris BREZILLON
2014-03-27 8:39 ` Boris BREZILLON
2014-03-27 11:19 ` Fabio Estevam
2014-03-27 13:27 ` Boris BREZILLON
2014-03-27 10:01 ` [PATCH] clk: register fixed-clock only if #clock-cells property is present Sylwester Nawrocki
2014-03-27 11:14 ` Boris BREZILLON [this message]
2014-03-27 10:55 ` Sylwester Nawrocki
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=533407F9.7060509@gmail.com \
--to=b.brezillon.dev@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).