[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <559B06C7.80209@codeaurora.org>
Date: Mon, 06 Jul 2015 15:52:55 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Daniel Kurtz <djkurtz@...omium.org>
CC: James Liao <jamesjj.liao@...iatek.com>,
Mike Turquette <mturquette@...aro.org>,
srv_heupstream <srv_heupstream@...iatek.com>,
"open list:OPEN FIRMWARE AND..." <devicetree@...r.kernel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ricky Liang <jcliang@...omium.org>,
Rob Herring <robh+dt@...nel.org>,
linux-mediatek@...ts.infradead.org,
Sascha Hauer <kernel@...gutronix.de>,
Matthias Brugger <matthias.bgg@...il.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 1/4] clk: mediatek: mt8173: Fix enabling of critical
clocks
On 07/02/2015 11:29 PM, Daniel Kurtz wrote:
> Hi Stephen,
>
> On Fri, Jul 3, 2015 at 7:03 AM, Stephen Boyd <sboyd@...eaurora.org> wrote:
>> On 06/30, James Liao wrote:
>>> From: Sascha Hauer <s.hauer@...gutronix.de>
>>>
>>> On the MT8173 the clocks are provided by different units. To enable
>>> the critical clocks we must be sure that all parent clocks are already
>>> registered, otherwise the parents of the critical clocks end up being
>>> unused and get disabled later. To find a place where all parents are
>>> registered we try each time after we've registered some clocks if
>>> all known providers are present now and only then we enable the critical
>>> clocks
>>>
>>> Signed-off-by: Sascha Hauer <s.hauer@...gutronix.de>
>>> Signed-off-by: James Liao <jamesjj.liao@...iatek.com>
>>> ---
>> Applied to clk-fixes
> I think James plans to send an updated version of this patch.
>
>
Oh right. Well those comments are minor so I'll just fold them in given
that I'm rewinding clk-fixes today. I see that comment in init.h about
uninitialized variables and __initdata too. I found this 10 year old
thread about that [1]. At least with my gcc-4.9 arm compiler I don't see
uninitialized __initdata moved to bss. A workaround seems to be to
initialize it to NULL in this case, but maybe that doesn't matter
because compilers don't have that problem anymore.
[1] http://lkml.iu.edu/hypermail/linux/kernel/0512.0/1366.html
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists