public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: x0080970@ti.com
Cc: linux-omap@vger.kernel.org, Nishanth Menon <nm@ti.com>,
	David Derrick <dderrick@ti.com>,
	Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH v2 1/6] omap3: pm: re-program the sleep state of TRITON resources by modifying the REMAP register
Date: Thu, 21 Jan 2010 14:53:14 -0800	[thread overview]
Message-ID: <877hrbhxyd.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1263922501-13701-1-git-send-email-x0080970@ti.com> (x0080970@ti.com's message of "Tue\, 19 Jan 2010 23\:05\:01 +0530")

x0080970@ti.com writes:

> From: Lesly A M <x0080970@ti.com>
>
> omap3: pm: re-program the sleep state of TRITON resources by modifying the REMAP register

This line duplicates subject, and is duplicated when applying to git.
This causes maintainers to have t manually edit the changelog to
remove the duplicate lines.

Could I recommend that you use git-format-patch + git-send-email?

The additional From: at the top isn't necessary either when the sender
and the author are the same.  To ensure you have the right name/email
in your git-generated patches, edit/edit  ~/.gitconfig and add something
that looks like this (changing the name/email to yours of course)  ;)

[user]
	name = Kevin Hilman
	email = khilman@deeprootsystems.com

I also noticed that the diffstat in PATCH 0/6 did not reflect all the
files touched.  At least the twl4030-script* files are missing from
the diffstat.

Again, git-format-patch would help here.  Using the --cover-letter option
to git-format-patch would generate a template for PATCH 0/x with the right
diffstat already done.


> Removed the warning print with checking order of scripts, since the order
> is not important. Only the values configured in the register, which is pointing to
> the starting address of each sequence should be correct.
>
> Signed-off-by: Lesly A M <x0080970@ti.com>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: David Derrick <dderrick@ti.com>
> Cc: Samuel Ortiz <sameo@linux.intel.com>

So I take it this patch can be ignored, as the equivalent is already
upstream, right?

Kevin

> ---
>  drivers/mfd/twl4030-power.c |   30 +++++++++++++++++++++++-------
>  1 file changed, 23 insertions(+), 7 deletions(-)
>
> Index: linux-omap-pm/drivers/mfd/twl4030-power.c
> ===================================================================
> --- linux-omap-pm.orig/drivers/mfd/twl4030-power.c	2010-01-19 19:18:56.000000000 +0530
> +++ linux-omap-pm/drivers/mfd/twl4030-power.c	2010-01-19 19:19:02.000000000 +0530
> @@ -416,14 +416,35 @@
>  		return err;
>  	}
>  
> -	return 0;
> +
> +	/* Set the remap sleep cmd */
> +	err = twl_i2c_read_u8(TWL4030_MODULE_PM_RECEIVER, &remap,
> +					rconfig_addr + REMAP_OFFSET);
> +	if (err < 0) {
> +		printk(KERN_ERR "TWL4030 Resource %d remap could not read\n",
> +							rconfig->resource);
> +		return err;
> +	}
> +
> +	if (rconfig->remap_sleep >= 0) {
> +		remap &= ~SLEEP_STATE_MASK;
> +		remap |= rconfig->remap_sleep;
> +	}
> +
> +	err = twl_i2c_write_u8(TWL4030_MODULE_PM_RECEIVER, remap,
> +				rconfig_addr + REMAP_OFFSET);
> +	if (err < 0) {
> +		pr_err("TWL4030 failed to program remap sleep cmd \n");
> +		return err;
> +	}
> +
> +	return err;
>  }
>  
>  static int __init load_twl4030_script(struct twl4030_script *tscript,
>  	       u8 address)
>  {
>  	int err;
> -	static int order;
>  
>  	/* Make sure the script isn't going beyond last valid address (0x3f) */
>  	if ((address + tscript->size) > END_OF_SCRIPT) {
> @@ -444,7 +465,6 @@
>  		err = twl4030_config_wakeup12_sequence(address);
>  		if (err)
>  			goto out;
> -		order = 1;
>  	}
>  	if (tscript->flags & TWL4030_WAKEUP3_SCRIPT) {
>  		err = twl4030_config_wakeup3_sequence(address);
> @@ -452,10 +472,6 @@
>  			goto out;
>  	}
>  	if (tscript->flags & TWL4030_SLEEP_SCRIPT)
> -		if (order)
> -			pr_warning("TWL4030: Bad order of scripts (sleep "\
> -					"script before wakeup) Leads to boot"\
> -					"failure on some boards\n");
>  		err = twl4030_config_sleep_sequence(address);
>  out:
>  	return err;
> --
> 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

      parent reply	other threads:[~2010-01-21 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19 17:35 [PATCH v2 1/6] omap3: pm: re-program the sleep state of TRITON resources by modifying the REMAP register x0080970
2010-01-20 15:28 ` Mike Rapoport
2010-01-21  6:10   ` Lesly AM
2010-01-21 23:30     ` Mike Turquette
2010-01-22  0:10       ` Kevin Hilman
2010-01-22 16:41         ` Mike Turquette
2010-01-21 22:53 ` Kevin Hilman [this message]

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=877hrbhxyd.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=dderrick@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=x0080970@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