public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>
To: ext Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 04/09] OMAP PM srf implementation
Date: Mon, 14 Jul 2008 16:29:09 +0300	[thread overview]
Message-ID: <20080714132909.GA4639@codecarver.research.nokia.com> (raw)
In-Reply-To: <030b01c8e0ef$46c859c0$68bf18ac@ent.ti.com>

Hi Rajendra,

> +void omap_pm_set_min_bus_tput(struct device *dev, struct bus_type *bus,
> +				    unsigned long r)

According to Paul's prototypes this should be 
void omap_pm_set_min_bus_tput(struct device *dev, u8 agent_id, 
			      unsigned long r)
				
> +{
> +	if (!dev) {
> +		WARN_ON(1);
> +		return;
> +	};
> +
> +	if (r == 0)
> +		pr_debug("OMAP PM: remove min bus tput constraint: "
> +			 "dev %p for bus %s\n", dev, bus->name);
> +	else
> +		pr_debug("OMAP PM: add min bus tput constraint: "
> +			 "dev %p for bus %s: rate %ld KiB\n", dev,
> +			 bus->name, r);
> +
> +	/*
> +	 * This code should model the bus and compute the required
> +	 * bus frequency, convert that to a VDD2 OPP ID, then set the VDD2
> +	 * OPP appropriately.
> +	 *
> +	 * TI CDP code can call constraint_set here on the VDD2 OPP.
> +	 */
> +}
> +

omap_pm_if_early_init and omap_pm_if_init are missing. I added dummy
functions for those.

With all of these changes it seems to work.

Cheers,

Peter.

-- 
goa is a state of mind

  reply	other threads:[~2008-07-14 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 11:39 [PATCH 04/09] OMAP PM srf implementation Rajendra Nayak
2008-07-14 13:29 ` Peter 'p2' De Schrijver [this message]
2008-07-14 14:54   ` Rajendra Nayak
2008-07-15 12:31     ` Peter 'p2' De Schrijver
2008-07-15 15:11     ` Paul Walmsley

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=20080714132909.GA4639@codecarver.research.nokia.com \
    --to=peter.de-schrijver@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox