From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/7] mfd: add pruss mfd driver.
Date: Tue, 22 Mar 2011 16:52:48 +0000 [thread overview]
Message-ID: <20110322165248.GF22583@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024C47D5EE@dbde02.ent.ti.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Nori, Sekhar" <nsekhar@ti.com>
Cc: Subhasish Ghosh <subhasish@mistralsolutions.com>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"Watkins, Melissa" <m-watkins@ti.com>,
open list <linux-kernel@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"sachi@mistralsolutions.com" <sachi@mistralsolutions.com>
Subject: Re: [PATCH v3 1/7] mfd: add pruss mfd driver.
Date: Tue, 22 Mar 2011 16:52:48 +0000 [thread overview]
Message-ID: <20110322165248.GF22583@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024C47D5EE@dbde02.ent.ti.com>
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.
next prev parent reply other threads:[~2011-03-22 16:52 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 13:57 [PATCH v3 0/7] pruss mfd drivers Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 1/7] mfd: add pruss mfd driver Subhasish Ghosh
2011-03-08 13:57 ` Subhasish Ghosh
2011-03-09 11:56 ` Marc Kleine-Budde
2011-03-09 11:56 ` Marc Kleine-Budde
2011-03-24 13:16 ` Subhasish Ghosh
2011-03-24 13:16 ` Subhasish Ghosh
2011-03-24 13:24 ` Marc Kleine-Budde
2011-03-24 13:24 ` Marc Kleine-Budde
2011-03-24 13:41 ` Kurt Van Dijck
2011-03-24 13:41 ` Kurt Van Dijck
2011-03-11 15:28 ` Arnd Bergmann
2011-03-11 15:28 ` Arnd Bergmann
2011-03-30 7:16 ` Subhasish Ghosh
2011-03-30 7:16 ` Subhasish Ghosh
2011-03-30 10:59 ` Arnd Bergmann
2011-03-30 10:59 ` Arnd Bergmann
2011-04-05 6:40 ` Subhasish Ghosh
2011-04-05 6:40 ` Subhasish Ghosh
2011-03-30 9:15 ` Subhasish Ghosh
2011-03-30 9:15 ` Subhasish Ghosh
2011-03-30 11:38 ` Arnd Bergmann
2011-03-30 11:38 ` Arnd Bergmann
2011-03-18 11:59 ` Nori, Sekhar
2011-03-18 11:59 ` Nori, Sekhar
2011-03-18 12:39 ` Mark Brown
2011-03-18 12:39 ` Mark Brown
2011-03-22 9:35 ` Nori, Sekhar
2011-03-22 9:35 ` Nori, Sekhar
2011-03-22 9:43 ` Nori, Sekhar
2011-03-22 9:43 ` Nori, Sekhar
2011-03-22 16:52 ` Mark Brown [this message]
2011-03-22 16:52 ` Mark Brown
2011-03-08 13:57 ` [PATCH v3 2/7] da850: pruss platform specific additions Subhasish Ghosh
2011-03-08 13:57 ` Subhasish Ghosh
2011-03-08 15:17 ` Sergei Shtylyov
2011-03-08 15:17 ` Sergei Shtylyov
2011-03-08 13:57 ` [PATCH v3 3/7] da850: pruss board " Subhasish Ghosh
2011-03-08 13:57 ` Subhasish Ghosh
2011-03-08 15:19 ` Sergei Shtylyov
2011-03-08 15:19 ` Sergei Shtylyov
2011-03-09 4:29 ` Subhasish Ghosh
2011-03-09 4:29 ` Subhasish Ghosh
2011-03-09 11:59 ` Marc Kleine-Budde
2011-03-09 11:59 ` Marc Kleine-Budde
2011-03-08 13:57 ` [PATCH v3 4/7] mfd: pruss SUART private data Subhasish Ghosh
2011-03-08 13:57 ` Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 5/7] da850: pruss SUART board specific additions Subhasish Ghosh
2011-03-08 13:57 ` Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 6/7] da850: pruss SUART platform " Subhasish Ghosh
2011-03-08 13:57 ` Subhasish Ghosh
2011-03-08 13:57 ` [PATCH v3 7/7] tty: add pruss SUART driver Subhasish Ghosh
2011-03-08 13:57 ` Subhasish Ghosh
2011-03-08 18:47 ` Randy Dunlap
2011-03-08 18:47 ` Randy Dunlap
2011-03-15 7:23 ` Subhasish Ghosh
2011-03-15 7:23 ` Subhasish Ghosh
2011-03-18 5:43 ` Subhasish Ghosh
2011-03-18 5:43 ` Subhasish Ghosh
2011-03-18 11:45 ` Alan Cox
2011-03-18 11:45 ` Alan Cox
2011-03-18 12:07 ` Arnd Bergmann
2011-03-18 12:07 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110322165248.GF22583@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.