All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	paul@pwsan.com
Subject: Re: [PATCH 4/7] OMAP2+: pm: Use hwmod name instead of dev pointer
Date: Wed, 31 Aug 2011 15:24:57 -0700	[thread overview]
Message-ID: <87ippd8bie.fsf@ti.com> (raw)
In-Reply-To: <1314026347-21623-5-git-send-email-b-cousson@ti.com> (Benoit Cousson's message of "Mon, 22 Aug 2011 17:19:04 +0200")

Benoit Cousson <b-cousson@ti.com> writes:

> Replace the struct device parameter of omap2_set_init_voltage
> by the hwmod name. It will avoid having to store explicitely
> the device pointer into a static variable.
> Moreover, it will be a little bit more scalable if we introduce
> new DVFS devices.
>
> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> Cc: Kevin Hilman <khilman@ti.com>
> ---
>  arch/arm/mach-omap2/pm.c |   22 +++++++++++++++-------
>  1 files changed, 15 insertions(+), 7 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c
> index 54281e5..17725d2 100644
> --- a/arch/arm/mach-omap2/pm.c
> +++ b/arch/arm/mach-omap2/pm.c
> @@ -171,18 +171,26 @@ err:
>   * in the opp entry
>   */
>  static int __init omap2_set_init_voltage(char *vdd_name, char *clk_name,
> -						struct device *dev)
> +					 const char *oh_name)
>  {
>  	struct voltagedomain *voltdm;
>  	struct clk *clk;
>  	struct opp *opp;
>  	unsigned long freq, bootup_volt;
> +	struct device *dev;
>  
> -	if (!vdd_name || !clk_name || !dev) {
> +	if (!vdd_name || !clk_name || !oh_name) {
>  		printk(KERN_ERR "%s: Invalid parameters!\n", __func__);
>  		goto exit;
>  	}
>  
> +	dev = omap_hwmod_name_get_dev(oh_name);
> +	if (IS_ERR(dev)) {
> +		pr_err("%s: Unable to get dev pointer for hwmod %s\n",
> +			__func__, oh_name);
> +		goto exit;
> +	}
> +
>  	voltdm = omap_voltage_domain_lookup(vdd_name);
>  	if (IS_ERR(voltdm)) {
>  		printk(KERN_ERR "%s: Unable to get vdd pointer for vdd_%s\n",
> @@ -228,8 +236,8 @@ static void __init omap3_init_voltages(void)
>  	if (!cpu_is_omap34xx())
>  		return;
>  
> -	omap2_set_init_voltage("mpu", "dpll1_ck", mpu_dev);
> -	omap2_set_init_voltage("core", "l3_ick", l3_dev);
> +	omap2_set_init_voltage("mpu", "dpll1_ck", "mpu");
> +	omap2_set_init_voltage("core", "l3_ick", "l3_main");
>  }
>  
>  static void __init omap4_init_voltages(void)
> @@ -237,9 +245,9 @@ static void __init omap4_init_voltages(void)
>  	if (!cpu_is_omap44xx())
>  		return;
>  
> -	omap2_set_init_voltage("mpu", "dpll_mpu_ck", mpu_dev);
> -	omap2_set_init_voltage("core", "l3_div_ck", l3_dev);
> -	omap2_set_init_voltage("iva", "dpll_iva_m5x2_ck", iva_dev);
> +	omap2_set_init_voltage("mpu", "dpll_mpu_ck", "mpu");
> +	omap2_set_init_voltage("core", "l3_div_ck", "l3_main_1");
> +	omap2_set_init_voltage("iva", "dpll_iva_m5x2_ck", "iva");
>  }
>  
>  static int __init omap2_common_pm_init(void)

Looks fine.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] OMAP2+: pm: Use hwmod name instead of dev pointer
Date: Wed, 31 Aug 2011 15:24:57 -0700	[thread overview]
Message-ID: <87ippd8bie.fsf@ti.com> (raw)
In-Reply-To: <1314026347-21623-5-git-send-email-b-cousson@ti.com> (Benoit Cousson's message of "Mon, 22 Aug 2011 17:19:04 +0200")

Benoit Cousson <b-cousson@ti.com> writes:

> Replace the struct device parameter of omap2_set_init_voltage
> by the hwmod name. It will avoid having to store explicitely
> the device pointer into a static variable.
> Moreover, it will be a little bit more scalable if we introduce
> new DVFS devices.
>
> Signed-off-by: Benoit Cousson <b-cousson@ti.com>
> Cc: Kevin Hilman <khilman@ti.com>
> ---
>  arch/arm/mach-omap2/pm.c |   22 +++++++++++++++-------
>  1 files changed, 15 insertions(+), 7 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm.c b/arch/arm/mach-omap2/pm.c
> index 54281e5..17725d2 100644
> --- a/arch/arm/mach-omap2/pm.c
> +++ b/arch/arm/mach-omap2/pm.c
> @@ -171,18 +171,26 @@ err:
>   * in the opp entry
>   */
>  static int __init omap2_set_init_voltage(char *vdd_name, char *clk_name,
> -						struct device *dev)
> +					 const char *oh_name)
>  {
>  	struct voltagedomain *voltdm;
>  	struct clk *clk;
>  	struct opp *opp;
>  	unsigned long freq, bootup_volt;
> +	struct device *dev;
>  
> -	if (!vdd_name || !clk_name || !dev) {
> +	if (!vdd_name || !clk_name || !oh_name) {
>  		printk(KERN_ERR "%s: Invalid parameters!\n", __func__);
>  		goto exit;
>  	}
>  
> +	dev = omap_hwmod_name_get_dev(oh_name);
> +	if (IS_ERR(dev)) {
> +		pr_err("%s: Unable to get dev pointer for hwmod %s\n",
> +			__func__, oh_name);
> +		goto exit;
> +	}
> +
>  	voltdm = omap_voltage_domain_lookup(vdd_name);
>  	if (IS_ERR(voltdm)) {
>  		printk(KERN_ERR "%s: Unable to get vdd pointer for vdd_%s\n",
> @@ -228,8 +236,8 @@ static void __init omap3_init_voltages(void)
>  	if (!cpu_is_omap34xx())
>  		return;
>  
> -	omap2_set_init_voltage("mpu", "dpll1_ck", mpu_dev);
> -	omap2_set_init_voltage("core", "l3_ick", l3_dev);
> +	omap2_set_init_voltage("mpu", "dpll1_ck", "mpu");
> +	omap2_set_init_voltage("core", "l3_ick", "l3_main");
>  }
>  
>  static void __init omap4_init_voltages(void)
> @@ -237,9 +245,9 @@ static void __init omap4_init_voltages(void)
>  	if (!cpu_is_omap44xx())
>  		return;
>  
> -	omap2_set_init_voltage("mpu", "dpll_mpu_ck", mpu_dev);
> -	omap2_set_init_voltage("core", "l3_div_ck", l3_dev);
> -	omap2_set_init_voltage("iva", "dpll_iva_m5x2_ck", iva_dev);
> +	omap2_set_init_voltage("mpu", "dpll_mpu_ck", "mpu");
> +	omap2_set_init_voltage("core", "l3_div_ck", "l3_main_1");
> +	omap2_set_init_voltage("iva", "dpll_iva_m5x2_ck", "iva");
>  }
>  
>  static int __init omap2_common_pm_init(void)

Looks fine.

Kevin

  reply	other threads:[~2011-08-31 22:25 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 15:19 [PATCH 0/7] OMAP: omap_device cleanup before device-tree integration Benoit Cousson
2011-08-22 15:19 ` Benoit Cousson
2011-08-22 15:19 ` [PATCH 1/7] OMAP: PM: omap_device: add omap_hwmod_name_get_odev Benoit Cousson
2011-08-22 15:19   ` Benoit Cousson
2011-08-31 22:20   ` Kevin Hilman
2011-08-31 22:20     ` Kevin Hilman
2011-09-01 11:48     ` Cousson, Benoit
2011-09-01 11:48       ` Cousson, Benoit
2011-09-01 20:44       ` Menon, Nishanth
2011-09-01 20:44         ` Menon, Nishanth
2011-09-26 18:18   ` Kevin Hilman
2011-09-26 18:18     ` Kevin Hilman
2011-08-22 15:19 ` [PATCH 2/7] OMAP: PM: omap_device: add few quick access functions Benoit Cousson
2011-08-22 15:19   ` Benoit Cousson
2011-08-31 22:23   ` Kevin Hilman
2011-08-31 22:23     ` Kevin Hilman
2011-09-01 11:55     ` Cousson, Benoit
2011-09-01 11:55       ` Cousson, Benoit
2011-09-01 14:55       ` Kevin Hilman
2011-09-01 14:55         ` Kevin Hilman
2011-09-02 12:39     ` Cousson, Benoit
2011-09-02 12:39       ` Cousson, Benoit
2011-08-22 15:19 ` [PATCH 3/7] OMAP3: beagle-board: Use the omap_hwmod_name_get_dev API Benoit Cousson
2011-08-22 15:19   ` Benoit Cousson
2011-08-31 22:24   ` Kevin Hilman
2011-08-31 22:24     ` Kevin Hilman
2011-08-22 15:19 ` [PATCH 4/7] OMAP2+: pm: Use hwmod name instead of dev pointer Benoit Cousson
2011-08-22 15:19   ` Benoit Cousson
2011-08-31 22:24   ` Kevin Hilman [this message]
2011-08-31 22:24     ` Kevin Hilman
2011-08-22 15:19 ` [PATCH 5/7] OMAP2+: pm: Remove static devices variable for mpu, dsp, iva and l3 PM Benoit Cousson
2011-08-22 15:19   ` Benoit Cousson
2011-08-31 22:25   ` Kevin Hilman
2011-08-31 22:25     ` Kevin Hilman
2011-08-22 15:19 ` [PATCH 6/7] OMAP: omap_device: Create a default omap_device_pm_latency Benoit Cousson
2011-08-22 15:19   ` Benoit Cousson
2011-08-31 22:30   ` Kevin Hilman
2011-08-31 22:30     ` Kevin Hilman
2011-08-22 15:19 ` [PATCH 7/7] OMAP2+: devices: Remove all omap_device_pm_latency structures Benoit Cousson
2011-08-22 15:19   ` Benoit Cousson
2011-08-31 22:31   ` Kevin Hilman
2011-08-31 22:31     ` Kevin Hilman
2011-09-01 11:59     ` Cousson, Benoit
2011-09-01 11:59       ` Cousson, Benoit
2011-09-01 16:28 ` [PATCH 0/7] OMAP: omap_device cleanup before device-tree integration Kevin Hilman
2011-09-01 16:28   ` Kevin Hilman

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=87ippd8bie.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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 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.