From: Kevin Hilman <khilman@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: jean.pihet@newoldbits.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, paul@pwsan.com,
Jean Pihet <j-pihet@ti.com>, Vishwanath BS <vishwanath.bs@ti.com>
Subject: Re: [PATCH 1/8] OMAP PM: create a PM layer plugin for per-device constraints
Date: Wed, 04 May 2011 07:36:58 -0700 [thread overview]
Message-ID: <87vcxqv8fp.fsf@ti.com> (raw)
In-Reply-To: <20110504135930.GE2092@atomide.com> (Tony Lindgren's message of "Wed, 4 May 2011 06:59:30 -0700")
Tony,
Tony Lindgren <tony@atomide.com> writes:
> * jean.pihet@newoldbits.com <jean.pihet@newoldbits.com> [110504 06:32]:
>>
>> +int omap_pm_set_max_mpu_wakeup_lat(struct device *dev, long t)
> ...
>
>> +int omap_pm_set_max_dev_wakeup_lat(struct device *req_dev, struct device *dev,
> ...
>
>> +int omap_pm_set_min_clk_rate(struct device *dev, struct clk *c, long r)
> ...
>
> You should implement this as a Linux generic framework, we don't
> want to add more omap specific frameworks.
This series isn't adding any new OMAP-specific frameworks. The OMAP PM
layer is already in place, and has been there for awhile. OMAP PM is a
layer which can have "plugins" so we can experiment with ways of
handling constraints without changing the driver interface, and this
series is just implementing a new plugin.
Once we are happy with a constraint layer, and can prove it will work,
the plan is to get rid of the (existing) OMAP-specific APIs and propose
a generic interface.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] OMAP PM: create a PM layer plugin for per-device constraints
Date: Wed, 04 May 2011 07:36:58 -0700 [thread overview]
Message-ID: <87vcxqv8fp.fsf@ti.com> (raw)
In-Reply-To: <20110504135930.GE2092@atomide.com> (Tony Lindgren's message of "Wed, 4 May 2011 06:59:30 -0700")
Tony,
Tony Lindgren <tony@atomide.com> writes:
> * jean.pihet at newoldbits.com <jean.pihet@newoldbits.com> [110504 06:32]:
>>
>> +int omap_pm_set_max_mpu_wakeup_lat(struct device *dev, long t)
> ...
>
>> +int omap_pm_set_max_dev_wakeup_lat(struct device *req_dev, struct device *dev,
> ...
>
>> +int omap_pm_set_min_clk_rate(struct device *dev, struct clk *c, long r)
> ...
>
> You should implement this as a Linux generic framework, we don't
> want to add more omap specific frameworks.
This series isn't adding any new OMAP-specific frameworks. The OMAP PM
layer is already in place, and has been there for awhile. OMAP PM is a
layer which can have "plugins" so we can experiment with ways of
handling constraints without changing the driver interface, and this
series is just implementing a new plugin.
Once we are happy with a constraint layer, and can prove it will work,
the plan is to get rid of the (existing) OMAP-specific APIs and propose
a generic interface.
Kevin
next prev parent reply other threads:[~2011-05-04 14:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 13:35 [PATCH v4 0/8] OMAP: add PM_CONSTRAINTS framework jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
2011-05-04 13:35 ` [PATCH 1/8] OMAP PM: create a PM layer plugin for per-device constraints jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
2011-05-04 13:59 ` Tony Lindgren
2011-05-04 13:59 ` Tony Lindgren
2011-05-04 14:36 ` Kevin Hilman [this message]
2011-05-04 14:36 ` Kevin Hilman
2011-05-05 6:00 ` Tony Lindgren
2011-05-05 6:00 ` Tony Lindgren
2011-05-06 6:20 ` Tony Lindgren
2011-05-06 6:20 ` Tony Lindgren
2011-05-04 13:35 ` [PATCH 2/8] OMAP2+: powerdomain: control power domains next state jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
2011-05-04 13:35 ` [PATCH 3/8] OMAP3: powerdomain data: add wake-up latency figures jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
2011-05-04 13:35 ` [PATCH 4/8] OMAP2+: omap_hwmod: manage the omap_devices the wake-up latency constraints jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
2011-05-04 13:35 ` [PATCH 5/8] OMAP: PM CONSTRAINTS: add an enum for the classes of constraint jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
2011-05-04 13:35 ` [PATCH 6/8] OMAP2+: omap_device: implement the constraints management code jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
2011-05-04 22:11 ` Todd Poynor
2011-05-04 22:11 ` Todd Poynor
2011-05-04 13:35 ` [PATCH 7/8] OMAP: PM CONSTRAINTS: implement wake-up latency constraints jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
2011-05-04 13:35 ` [PATCH 8/8] OMAP PM: early init of the pwrdms states jean.pihet
2011-05-04 13:35 ` jean.pihet at newoldbits.com
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 15:19 [PATCH v3 0/8] OMAP: add PM CONSTRAINTS framework jean.pihet
2011-03-30 15:19 ` [PATCH 1/8] OMAP PM: create a PM layer plugin for per-device constraints jean.pihet
2011-03-30 15:19 ` jean.pihet at newoldbits.com
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=87vcxqv8fp.fsf@ti.com \
--to=khilman@ti.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
--cc=vishwanath.bs@ti.com \
/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.