[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB593024C47D604@dbde02.ent.ti.com>
Date: Tue, 22 Mar 2011 15:13:46 +0530
From: "Nori, Sekhar" <nsekhar@...com>
To: "Nori, Sekhar" <nsekhar@...com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC: "sachi@...tralsolutions.com" <sachi@...tralsolutions.com>,
"davinci-linux-open-source@...ux.davincidsp.com"
<davinci-linux-open-source@...ux.davincidsp.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
Subhasish Ghosh <subhasish@...tralsolutions.com>,
open list <linux-kernel@...r.kernel.org>,
"Watkins, Melissa" <m-watkins@...com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH v3 1/7] mfd: add pruss mfd driver.
On Tue, Mar 22, 2011 at 15:05:07, Nori, Sekhar wrote:
> Hi Mark,
>
> On Fri, Mar 18, 2011 at 18:09:17, Mark Brown wrote:
> > On Fri, Mar 18, 2011 at 05:29:39PM +0530, Nori, Sekhar wrote:
> >
> > > PRUSS as an IP is not really tied to the DA8xx SoC architecture.
> > > So, can you please name the files ti-pruss* or even just pruss if
> > > MFD folks are okay with it?
> >
> > This...
> >
> > > > +EXPORT_SYMBOL(pruss_get_clk_freq);
> >
> > > This looks strange. Why do we need this? There
> > > is clk_get_rate() API in the kernel would would
> > > seem more suitable.
> >
> > ...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
This should have read "under plat-omap/mach-omap2 and mach-davinci"
Thanks,
Sekhar
--
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