From: Trilok Soni <tsoni@codeaurora.org>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: Kevin Hilman <khilman@ti.com>,
jean.pihet@newoldbits.com, LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-omap@vger.kernel.org, Jean Pihet <j-pihet@ti.com>,
linux-arm-kernel@lists.infradead.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 2/9] ARM: OMAP2+: SmartReflex: move the driver specific macros in include/linux/power
Date: Thu, 05 Apr 2012 12:23:25 +0530 [thread overview]
Message-ID: <4F7D4165.2060101@codeaurora.org> (raw)
In-Reply-To: <4F7CA3E1.2050809@ti.com>
Hi Benoit,
>
> The main motivation is that it's a driver and thus does not have
> anything to do inside mach-omap2.
Right, I understood that. mach-omap2 is not suitable for full fledged
drivers.
>
> Where will you put that otherwise?
Couple of suggestions:
drivers/platform/omap/avs?
drivers/misc/omap/avs?
I prefer first one.
>
> IIRC, David Brownell was referring to the rule of three for such case.
> Meaning that it worth having a generic fmwk when at least three
> different drivers are doing the same kind of things.
Yes, I remember that rule, but that's not stopping us to create a fwk,
may be others will rise once they see the framework and contribute
if their h/w architecture requirements are not addressed?
---Trilok Soni
--
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: tsoni@codeaurora.org (Trilok Soni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/9] ARM: OMAP2+: SmartReflex: move the driver specific macros in include/linux/power
Date: Thu, 05 Apr 2012 12:23:25 +0530 [thread overview]
Message-ID: <4F7D4165.2060101@codeaurora.org> (raw)
In-Reply-To: <4F7CA3E1.2050809@ti.com>
Hi Benoit,
>
> The main motivation is that it's a driver and thus does not have
> anything to do inside mach-omap2.
Right, I understood that. mach-omap2 is not suitable for full fledged
drivers.
>
> Where will you put that otherwise?
Couple of suggestions:
drivers/platform/omap/avs?
drivers/misc/omap/avs?
I prefer first one.
>
> IIRC, David Brownell was referring to the rule of three for such case.
> Meaning that it worth having a generic fmwk when at least three
> different drivers are doing the same kind of things.
Yes, I remember that rule, but that's not stopping us to create a fwk,
may be others will rise once they see the framework and contribute
if their h/w architecture requirements are not addressed?
---Trilok Soni
--
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-04-05 6:53 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 16:12 [PATCH v2 0/9] PM: Create the AVS class of drivers jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 1/9] ARM: OMAP3+: voltage: export functions to plat/voltage.h jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-04-18 17:27 ` Kevin Hilman
2012-04-18 17:27 ` Kevin Hilman
2012-04-18 20:36 ` Jean Pihet
2012-04-18 20:36 ` Jean Pihet
2012-04-18 20:36 ` Jean Pihet
2012-03-19 16:12 ` [PATCH 2/9] ARM: OMAP2+: SmartReflex: move the driver specific macros in include/linux/power jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-04-04 19:10 ` Trilok Soni
2012-04-04 19:10 ` Trilok Soni
2012-04-04 19:41 ` Cousson, Benoit
2012-04-04 19:41 ` Cousson, Benoit
2012-04-04 19:41 ` Cousson, Benoit
2012-04-05 6:53 ` Trilok Soni [this message]
2012-04-05 6:53 ` Trilok Soni
2012-04-05 8:59 ` Jean Pihet
2012-04-05 8:59 ` Jean Pihet
2012-04-05 9:35 ` Trilok Soni
2012-04-05 9:35 ` Trilok Soni
2012-04-19 13:54 ` Arnd Bergmann
2012-04-19 13:54 ` Arnd Bergmann
2012-04-19 16:02 ` Jean Pihet
2012-04-19 16:02 ` Jean Pihet
2012-04-19 16:02 ` Jean Pihet
2012-04-19 17:06 ` Kevin Hilman
2012-04-19 17:06 ` Kevin Hilman
2012-04-19 17:06 ` Kevin Hilman
2012-03-19 16:12 ` [PATCH 3/9] ARM: OMAP3+: SmartReflex: class drivers should use struct omap_sr * jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 4/9] ARM: OMAP2+: smartreflex: Use the names from hwmod data instead of voltage domains jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 5/9] ARM: OMAP3: hwmod: rename the smartreflex entries jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-04-18 17:33 ` Kevin Hilman
2012-04-18 17:33 ` Kevin Hilman
2012-04-18 20:41 ` Jean Pihet
2012-04-18 20:41 ` Jean Pihet
2012-04-18 20:41 ` Jean Pihet
2012-03-19 16:12 ` [PATCH 6/9] ARM: OMAP2+: SmartReflex: introduce a busy loop condition test macro jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 7/9] ARM: OMAP2+: SmartReflex: Use per-OPP data structure jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-04-18 18:21 ` Kevin Hilman
2012-04-18 18:21 ` Kevin Hilman
2012-04-18 20:52 ` Jean Pihet
2012-04-18 20:52 ` Jean Pihet
2012-04-18 20:52 ` Jean Pihet
2012-03-19 16:12 ` [PATCH 8/9] ARM: OMAP2+: SmartReflex: add POWER_AVS Kconfig options jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-03-19 16:12 ` [PATCH 9/9] ARM: OMAP: SmartReflex: Move smartreflex driver to drivers/ jean.pihet
2012-03-19 16:12 ` jean.pihet at newoldbits.com
2012-04-18 18:17 ` Kevin Hilman
2012-04-18 18:17 ` Kevin Hilman
2012-04-03 11:14 ` [PATCH v2 0/9] PM: Create the AVS class of drivers Jean Pihet
2012-04-03 11:14 ` Jean Pihet
2012-04-03 11:14 ` Jean Pihet
2012-04-18 8:04 ` Jean Pihet
2012-04-18 8:04 ` Jean Pihet
2012-04-19 0:08 ` Greg KH
2012-04-19 0:08 ` Greg KH
2012-04-18 18:29 ` Kevin Hilman
2012-04-18 18:29 ` Kevin Hilman
2012-04-18 18:30 ` Kevin Hilman
2012-04-18 18:30 ` Kevin Hilman
2012-04-18 18:30 ` Kevin Hilman
2012-04-18 18:49 ` Rafael J. Wysocki
2012-04-18 18:49 ` Rafael J. Wysocki
2012-04-18 18:49 ` Rafael J. Wysocki
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=4F7D4165.2060101@codeaurora.org \
--to=tsoni@codeaurora.org \
--cc=b-cousson@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.