[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3E54258959B69E4282D79E01AB1F32B7041B059A@DFLE12.ent.ti.com>
Date: Mon, 3 Sep 2012 22:15:10 +0000
From: "Karicheri, Muralidharan" <m-karicheri2@...com>
To: Linus Walleij <linus.walleij@...aro.org>,
"Hilman, Kevin" <khilman@...com>, "Nori, Sekhar" <nsekhar@...com>
CC: "grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mturquette@...aro.org" <mturquette@...aro.org>
Subject: RE: [PATCH] gpio:clk: preparation for switch to common clock
framework
>> -----Original Message-----
>> From: Linus Walleij [mailto:linus.walleij@...aro.org]
>> Sent: Friday, August 31, 2012 7:14 PM
>> To: Karicheri, Muralidharan; Hilman, Kevin; Nori, Sekhar
>> Cc: grant.likely@...retlab.ca; linux-kernel@...r.kernel.org; mturquette@...aro.org
>> Subject: Re: [PATCH] gpio:clk: preparation for switch to common clock framework
>>
>> On Thu, Aug 30, 2012 at 8:03 PM, Murali Karicheri <m-karicheri2@...com> wrote:
>>
>> > As a first step towards migrating davinci platforms to use common clock
>> > framework, replace all instances of clk_enable() with clk_prepare_enable()
>> > and clk_disable() with clk_disable_unprepare(). Until the platform is
>> > switched to use the CONFIG_HAVE_CLK_PREPARE Kconfig variable, this just
>> > adds a might_sleep() call and would work without any issues.
>> >
>> > This will make it easy later to switch to common clk based implementation
>> > of clk driver from DaVinci specific driver.
>> >
>> > Signed-off-by: Murali Karicheri <m-karicheri2@...com>
>>
>> OK the patch is so obviously correct so I just applied it, DaVinci folks,
>> scream if you still don't want it for some reason...
>>
Linus,
Thanks for applying this patch.
Murali Karicheri
Software Design Engineer
>> Yours,
>> Linus Walleij
--
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