[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 10 Oct 2012 14:19:30 +0000
From: "Karicheri, Muralidharan" <m-karicheri2@...com>
To: "Nori, Sekhar" <nsekhar@...com>
CC: "Hilman, Kevin" <khilman@...com>,
"davinci-linux-open-source@...ux.davincidsp.com"
<davinci-linux-open-source@...ux.davincidsp.com>,
"mturquette@...aro.org" <mturquette@...aro.org>,
"linux-c6x-dev@...ux-c6x.org" <linux-c6x-dev@...ux-c6x.org>,
"arnd@...db.de" <arnd@...db.de>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"linux-keystone@...t.ti.com - Linux developers for Keystone family of
devices (May contain non-TIers)" <linux-keystone@...t.ti.com>,
"viresh.linux@...il.com" <viresh.linux@...il.com>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"shawn.guo@...aro.org" <shawn.guo@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH 02/13] clk: davinci - add PSC clock driver
>> -----Original Message-----
>> From: Nori, Sekhar
>> Sent: Wednesday, October 10, 2012 8:46 AM
>> To: Nori, Sekhar
>> Cc: Karicheri, Muralidharan; Hilman, Kevin; davinci-linux-open-
>> source@...ux.davincidsp.com; mturquette@...aro.org; linux-c6x-dev@...ux-c6x.org;
>> arnd@...db.de; linus.walleij@...aro.org; linux-kernel@...r.kernel.org;
>> rob.herring@...xeda.com; linux-keystone@...t.ti.com - Linux developers for Keystone
>> family of devices (May contain non-TIers); viresh.linux@...il.com;
>> linux@....linux.org.uk; akpm@...ux-foundation.org; shawn.guo@...aro.org; linux-arm-
>> kernel@...ts.infradead.org
>> Subject: Re: [PATCH 02/13] clk: davinci - add PSC clock driver
>>
>> On 10/10/2012 6:05 PM, Sekhar Nori wrote:
>>
>> >> +struct clk *clk_register_davinci_psc(struct device *dev, const char *name,
>> >> + const char *parent_name,
>> >> + struct clk_davinci_psc_data *psc_data,
>> >> + spinlock_t *lock)
>> >
>> > Why do you need the lock to be provided from outside of this file? You
>> > can initialize a lock for serializing writes to PSC registers within
>> > this file, no?
>>
>> Looking again, it seems like the common clock framework defines an "enable_lock" in
>> drivers/clk/clk.c to serialize the clock enable/disable calls. Unless I am missing something,
>> this lock seems unnecessary.
>>
I think you are right. For enable() api, enable_lock is sufficient and I will remove this.
>> Thanks,
>> Sekhar
Powered by blists - more mailing lists