From: "Rajendra Nayak" <rnayak@ti.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH 00/09] OMAP PM interface implementation using Shared resource f/w
Date: Tue, 8 Jul 2008 17:09:18 +0530 [thread overview]
Message-ID: <030701c8e0ef$42440a20$68bf18ac@ent.ti.com> (raw)
Hi,
The patches which follow implement the API's defined by Paul Walmsley as part of the
OMAP PM Interface on OMAP3430sdp.
Shared resource f/w is used for the underlying implementation.
The following resources are modeled
1) MPU/CORE latency resources
2) Power Domain latency resources (One for each Power domain)
3) OPP/Freq resources (For DVFS)
The below API from the OMAP PM interface is yet to be implemented.
void omap_pm_set_min_bus_tput(struct device *dev, struct bus_type *bus,
unsigned long r)
regards,
Rajendra
next reply other threads:[~2008-07-08 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 11:39 Rajendra Nayak [this message]
2008-07-11 11:52 ` [PATCH 00/09] OMAP PM interface implementation using Shared resource f/w Peter 'p2' De Schrijver
2008-07-11 11:54 ` [PATCH 00/09] OMAP PM interface implementation using Sharedresource f/w Rajendra Nayak
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='030701c8e0ef$42440a20$68bf18ac@ent.ti.com' \
--to=rnayak@ti.com \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox