public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/4] Clockdomains: connect clockdomain code to powerdomain code
Date: Wed, 16 Apr 2008 14:41:39 -0700	[thread overview]
Message-ID: <20080416214136.GN17055@atomide.com> (raw)
In-Reply-To: <20080410163626.045491105@pwsan.com>

* Paul Walmsley <paul@pwsan.com> [080410 10:18]:
> Thie patch adds code to the powerdomain layer to track the
> clockdomains associated with each powerdomain.
> 
> It also modifies the clockdomain code to register clockdomains
> with their corresponding powerdomain when the clockdomain is registered.
> 
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> 
> ---
>  arch/arm/mach-omap2/clockdomain.c       |    4 +
>  arch/arm/mach-omap2/powerdomain.c       |  128 ++++++++++++++++++++++++++++++++
>  include/asm-arm/arch-omap/powerdomain.h |   17 +++-
>  3 files changed, 147 insertions(+), 2 deletions(-)
> 
> Index: linux-omap/arch/arm/mach-omap2/clockdomain.c
> ===================================================================
> --- linux-omap.orig/arch/arm/mach-omap2/clockdomain.c	2008-04-10 08:04:34.000000000 -0600
> +++ linux-omap/arch/arm/mach-omap2/clockdomain.c	2008-04-10 08:07:08.000000000 -0600
> @@ -195,6 +195,8 @@
>  	list_add(&clkdm->node, &clkdm_list);
>  	mutex_unlock(&clkdm_mutex);
>  
> +	pwrdm_add_clkdm(pwrdm, clkdm);
> +
>  	pr_debug("clockdomain: registered %s\n", clkdm->name);
>  
>  	return 0;
> @@ -213,6 +215,8 @@
>  	if (!clkdm)
>  		return -EINVAL;
>  
> +	pwrdm_del_clkdm(clkdm->pwrdm, clkdm);
> +
>  	mutex_lock(&clkdm_mutex);
>  	list_del(&clkdm->node);
>  	mutex_unlock(&clkdm_mutex);
> Index: linux-omap/arch/arm/mach-omap2/powerdomain.c
> ===================================================================
> --- linux-omap.orig/arch/arm/mach-omap2/powerdomain.c	2008-04-10 08:01:43.000000000 -0600
> +++ linux-omap/arch/arm/mach-omap2/powerdomain.c	2008-04-10 08:05:40.000000000 -0600
> @@ -32,6 +32,7 @@
>  
>  #include <asm/arch/cpu.h>
>  #include <asm/arch/powerdomain.h>
> +#include <asm/arch/clockdomain.h>
>  
>  /* pwrdm_list contains all registered struct powerdomains */
>  static LIST_HEAD(pwrdm_list);
> @@ -208,6 +209,133 @@
>  EXPORT_SYMBOL(pwrdm_for_each);
>  
>  /**
> + * pwrdm_add_clkdm - add a clockdomain to a powerdomain
> + * @pwrdm: struct powerdomain * to add the clockdomain to
> + * @clkdm: struct clockdomain * to associate with a powerdomain
> + *
> + * Associate the clockdomain 'clkdm' with a powerdomain 'pwrdm'.  This
> + * enables the use of pwrdm_for_each_clkdm().  Returns -EINVAL if
> + * presented with invalid pointers; -ENOMEM if memory could not be allocated;
> + * or 0 upon success.
> + */
> +int pwrdm_add_clkdm(struct powerdomain *pwrdm, struct clockdomain *clkdm)
> +{
> +	int i;
> +	int ret = 0;
> +
> +	if (!pwrdm || !clkdm)
> +		return -EINVAL;
> +
> +	pr_debug("powerdomain: associating clockdomain %s with powerdomain "
> +		 "%s\n", clkdm->name, pwrdm->name);
> +
> +	mutex_lock(&pwrdm_mutex);
> +
> +	for (i = 0; i < PWRDM_MAX_CLKDMS; i++) {
> +		if (!pwrdm->pwrdm_clkdms[i])
> +			break;
> +#ifdef DEBUG
> +		if (pwrdm->pwrdm_clkdms[i] == clkdm) {
> +			ret = -EINVAL;
> +			goto pac_exit;
> +		}
> +#endif
> +	}
> +
> +	if (i == PWRDM_MAX_CLKDMS) {
> +		pr_debug("powerdomain: increase PWRDM_MAX_CLKDMS for "
> +			 "pwrdm %s clkdm %s\n", pwrdm->name, clkdm->name);
> +		WARN_ON(1);
> +		ret = -ENOMEM;
> +		goto pac_exit;
> +	}
> +
> +	pwrdm->pwrdm_clkdms[i] = clkdm;
> +
> +pac_exit:
> +	mutex_unlock(&pwrdm_mutex);
> +
> +	return ret;
> +}
> +
> +/**
> + * pwrdm_del_clkdm - remove a clockdomain to a powerdomain
> + * @pwrdm: struct powerdomain * to add the clockdomain to
> + * @clkdm: struct clockdomain * to associate with a powerdomain
> + *
> + * Dissociate the clockdomain 'clkdm' from the powerdomain
> + * 'pwrdm'. Returns -EINVAL if presented with invalid pointers;
> + * -ENOENT if the clkdm was not associated with the powerdomain, or 0
> + * upon success.
> + */
> +int pwrdm_del_clkdm(struct powerdomain *pwrdm, struct clockdomain *clkdm)
> +{
> +	int ret = 0;
> +	int i;
> +
> +	if (!pwrdm || !clkdm)
> +		return -EINVAL;
> +
> +	pr_debug("powerdomain: dissociating clockdomain %s from powerdomain "
> +		 "%s\n", clkdm->name, pwrdm->name);
> +
> +	mutex_lock(&pwrdm_mutex);
> +
> +	for (i = 0; i < PWRDM_MAX_CLKDMS; i++)
> +		if (pwrdm->pwrdm_clkdms[i] == clkdm)
> +			break;
> +
> +	if (i == PWRDM_MAX_CLKDMS) {
> +		pr_debug("powerdomain: clkdm %s not associated with pwrdm "
> +			 "%s ?!\n", clkdm->name, pwrdm->name);
> +		ret = -ENOENT;
> +		goto pdc_exit;
> +	}
> +
> +	pwrdm->pwrdm_clkdms[i] = NULL;
> +
> +pdc_exit:
> +	mutex_unlock(&pwrdm_mutex);
> +
> +	return ret;
> +}
> +
> +/**
> + * pwrdm_for_each_clkdm - call function on each clkdm in a pwrdm
> + * @pwrdm: struct powerdomain * to iterate over
> + * @fn: callback function *
> + *
> + * Call the supplied function for each clockdomain in the powerdomain
> + * 'pwrdm'.  The callback function can return anything but 0 to bail
> + * out early from the iterator.	 The callback function is called with
> + * the pwrdm_mutex held, so no powerdomain structure manipulation
> + * functions should be called from the callback, although hardware
> + * powerdomain control functions are fine.  Returns -EINVAL if
> + * presented with invalid pointers; or passes along the last return
> + * value of the callback function, which should be 0 for success or
> + * anything else to indicate failure.
> + */

Tabs here too in comments.


> +int pwrdm_for_each_clkdm(struct powerdomain *pwrdm,
> +			 int (*fn)(struct powerdomain *pwrdm,
> +				   struct clockdomain *clkdm))
> +{
> +	int ret = 0;
> +	int i;
> +
> +	if (!fn)
> +		return -EINVAL;
> +
> +	mutex_lock(&pwrdm_mutex);
> +
> +	for (i = 0; i < PWRDM_MAX_CLKDMS && !ret; i++)
> +		ret = (*fn)(pwrdm, pwrdm->pwrdm_clkdms[i]);
> +
> +	mutex_unlock(&pwrdm_mutex);
> +
> +	return ret;
> +}
> +
> +/**
>   * pwrdm_add_wkdep - add a wakeup dependency from pwrdm2 to pwrdm1
>   * @pwrdm1: wake this struct powerdomain * up (dependent)
>   * @pwrdm2: when this struct powerdomain * wakes up (source)
> Index: linux-omap/include/asm-arm/arch-omap/powerdomain.h
> ===================================================================
> --- linux-omap.orig/include/asm-arm/arch-omap/powerdomain.h	2008-04-10 08:01:43.000000000 -0600
> +++ linux-omap/include/asm-arm/arch-omap/powerdomain.h	2008-04-10 08:05:40.000000000 -0600
> @@ -44,9 +44,16 @@
>   */
>  #define PWRDM_MAX_MEM_BANKS	4
>  
> +/*
> + * Maximum number of clockdomains that can be associated with a powerdomain.
> + * CORE powerdomain is probably the worst case.
> + */
> +#define PWRDM_MAX_CLKDMS	3
> +
>  /* XXX A completely arbitrary number. What is reasonable here? */
>  #define PWRDM_TRANSITION_BAILOUT 100000
>  
> +struct clockdomain;
>  struct powerdomain;
>  
>  /* Encodes dependencies between powerdomains - statically defined */
> @@ -94,8 +101,8 @@
>  	/* Possible memory bank pwrstates when pwrdm is ON */
>  	const u8 pwrsts_mem_on[PWRDM_MAX_MEM_BANKS];
>  
> -	/* List of clockdomains in this powerdomain */
> -	struct list_head pwrdm_clkdms;
> +	/* Clockdomains in this powerdomain */
> +	struct clockdomain *pwrdm_clkdms[PWRDM_MAX_CLKDMS];
>  
>  	struct kobject *kobj;
>  	struct list_head node;
> @@ -111,6 +118,12 @@
>  
>  int pwrdm_for_each(int (*fn)(struct powerdomain *pwrdm));
>  
> +int pwrdm_add_clkdm(struct powerdomain *pwrdm, struct clockdomain *clkdm);
> +int pwrdm_del_clkdm(struct powerdomain *pwrdm, struct clockdomain *clkdm);
> +int pwrdm_for_each_clkdm(struct powerdomain *pwrdm,
> +			 int (*fn)(struct powerdomain *pwrdm,
> +				   struct clockdomain *clkdm));
> +
>  int pwrdm_add_wkdep(struct powerdomain *pwrdm1, struct powerdomain *pwrdm2);
>  int pwrdm_del_wkdep(struct powerdomain *pwrdm1, struct powerdomain *pwrdm2);
>  int pwrdm_read_wkdep(struct powerdomain *pwrdm1, struct powerdomain *pwrdm2);
> 
> -- 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-04-16 21:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 16:25 [PATCH 0/4] Clockdomains: add OMAP2/3 clockdomain code, link 34xx clocks with clockdomains Paul Walmsley
2008-04-10 16:25 ` [PATCH 1/4] Clockdomains: add base OMAP2/3 clockdomain code Paul Walmsley
2008-04-16 21:39   ` Tony Lindgren
2008-04-10 16:25 ` [PATCH 2/4] Clockdomains: connect clockdomain code to powerdomain code Paul Walmsley
2008-04-16 21:41   ` Tony Lindgren [this message]
2008-04-10 16:25 ` [PATCH 3/4] Clockdomains: encode OMAP2/3 clockdomains Paul Walmsley
2008-04-10 16:25 ` [PATCH 4/4] Clockdomains: Integrate OMAP3 clocks with clockdomain code Paul Walmsley
  -- strict thread matches above, loose matches on Subject: below --
2008-04-19  1:42 [PATCH 0/4] clockdomains: add OMAP2/3 clockdomain code, link 34xx clocks with clockdomains Paul Walmsley
2008-04-19  1:43 ` [PATCH 2/4] clockdomains: connect clockdomain code to powerdomain code 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=20080416214136.GN17055@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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