[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110322165248.GF22583@opensource.wolfsonmicro.com>
Date: Tue, 22 Mar 2011 16:52:48 +0000
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: "Nori, Sekhar" <nsekhar@...com>
Cc: Subhasish Ghosh <subhasish@...tralsolutions.com>,
"davinci-linux-open-source@...ux.davincidsp.com"
<davinci-linux-open-source@...ux.davincidsp.com>,
"Watkins, Melissa" <m-watkins@...com>,
open list <linux-kernel@...r.kernel.org>,
Samuel Ortiz <sameo@...ux.intel.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"sachi@...tralsolutions.com" <sachi@...tralsolutions.com>
Subject: Re: [PATCH v3 1/7] mfd: add pruss mfd driver.
On Tue, Mar 22, 2011 at 03:05:07PM +0530, Nori, Sekhar wrote:
> On Fri, Mar 18, 2011 at 18:09:17, Mark Brown wrote:
> > ...unfortunately conflicts with this - currently all clock API
> > implementations are unique to the platform and there's no way of adding
> > clocks that works over multiple platforms.
> Hmm, I guess I have a limited view of this. We do have drivers which
> use clock API and work across OMAP and DaVinci series of ARM SoCs.
> The clock implementation in this case is under mach-omap and mach-davinci
> respectively.
It's mostly fine from the point of view of using clocks, it's if you're
trying to provide a clock that there's no API you can rely on - the
clock API itself only includes the user side and every platform gets to
provide its own implementation.
--
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