linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
To: Shubhrajyoti <shubhrajyoti-l0cyMroinI0@public.gmane.org>
Cc: balbi-l0cyMroinI0@public.gmane.org,
	"\"Andy Green (林安廸)\""
	<andy-/Zus8d0mwwtBDgjK7y7TUQ@public.gmane.org>,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	santosh.shilimkar-l0cyMroinI0@public.gmane.org
Subject: Re: [PATCH] OMAP4: I2C: Enable the wakeup in I2C_WE
Date: Fri, 29 Jul 2011 17:03:37 +0300	[thread overview]
Message-ID: <20110729140336.GU31013@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <4E32B88E.6030508-l0cyMroinI0@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3070 bytes --]

Hi,

On Fri, Jul 29, 2011 at 07:11:34PM +0530, Shubhrajyoti wrote:
> On Friday 29 July 2011 06:07 PM, Felipe Balbi wrote:
> >Hi,
> >
> >On Fri, Jul 29, 2011 at 01:28:12PM +0100, "Andy Green (林安廸)" wrote:
> >>On 07/29/2011 01:07 PM, Somebody in the thread at some point said:
> >>
> >>Hi -
> >>
> >>>-                       omap_i2c_write_reg(dev, OMAP_I2C_WE_REG, dev->westate);
> >>>+                       if (dev->rev<   OMAP_I2C_REV_ON_3530_4430)
> >>>+                               omap_i2c_write_reg(dev, OMAP_I2C_WE_REG,
> >>>+                                                               dev->westate);
> >>>Andy, can you clarify why you added the revision check which didn't
> >>>exist before ?
> >>>
> >>>[1] http://git.kernel.org/?p=linux/kernel/git/khilman/linux-omap-pm.git;a=commitdiff;h=a3a7acbcc3df4e9ecc12aa1fc435534d74ebbdf4
> >>>
> >>At the time I wrote the patches back in March, the code there was
> >>different: there was a pre-extant test avoiding that line on 4430,
> >>and the patch is simply converting it to the new scheme.  You can see
> >>it here:
> >>
> >>http://permalink.gmane.org/gmane.linux.ports.arm.omap/54940
> >>
> >>@@ -379,7 +379,7 @@ static int omap_i2c_init(struct omap_i2c_dev *dev)
> >>  			 * REVISIT: Some wkup sources might not be needed.
> >>  			 */
> >>  			dev->westate = OMAP_I2C_WE_ALL;
> >>-			if (dev->rev<  OMAP_I2C_REV_ON_4430)
> >>+			if (dev->rev<  OMAP_I2C_REV_ON_3530_4430)
> >>  				omap_i2c_write_reg(dev, OMAP_I2C_WE_REG,
> >>  								dev->westate);
> >>  		}
> >>
> >>I guess since March and before this got committed for 3.1, someone
> >>got a patch in first removing the test, so when my patchset was
> >>uplevelled for commit against 3.1-rc this conflict was dealt with by
> >>re-introducing the test.
> >>
> >>Long story short, it's there from me as a mechanical 1:1 renaming
> >>action as part of the fix that 3530 and 4430 (different) IPs return
> >>the same rev number.  Despite how it now looks I didn't add it, so if
> >>Shubhrajyoti has reasons to think it should be gone again I have
> >>nothing against that at all.
> >yeah, looks like a bad conflict resolution. Shubhrajyoti, care to respin
> >the patch and update commit log stating that it is fixing a bad conflict
> >resolution or something ?
> I wasn't aware of the conflict resolution part. Actually came across this
> piece of code as per the discussion on the reset implementation patch
> will update
> the changelogs.
> How about,
> 
> From: Shubhrajyoti D<shubhrajyoti-l0cyMroinI0@public.gmane.org>
> 
> Currently for OMAP4 the I2C_WE is not programmed.
> This patch enables the programming for OMAP4.
> 
> Fixes a conflict resolution of Andy's patches.

I think you need to be a bit more verbose here ;-) Describe what
happened and point to the commit number and mailing list archives for
references. Imagine someone else reads this commit half a year from now,
will s/he have enough information to understand the background of this
patch ?

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2011-07-29 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29 11:48 [PATCH] OMAP4: I2C: Enable the wakeup in I2C_WE Shubhrajyoti D
2011-07-29 12:07 ` Felipe Balbi
     [not found]   ` <20110729120711.GL31013-UiBtZHVXSwEVvW8u9ZQWYwjfymiNCTlR@public.gmane.org>
2011-07-29 12:28     ` "Andy Green (林安廸)"
     [not found]       ` <4E32A75C.5060400-/Zus8d0mwwtBDgjK7y7TUQ@public.gmane.org>
2011-07-29 12:37         ` Felipe Balbi
2011-07-29 13:41           ` Shubhrajyoti
     [not found]             ` <4E32B88E.6030508-l0cyMroinI0@public.gmane.org>
2011-07-29 14:03               ` Felipe Balbi [this message]
     [not found]             ` <CANQgH-YVzcvST=ofs4DYw5e4e_Qb1xO-=T46O6ioxMRDf2mpFg@mail.gmail.com>
     [not found]               ` <CANQgH-YVzcvST=ofs4DYw5e4e_Qb1xO-=T46O6ioxMRDf2mpFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-07-29 14:09                 ` Felipe Balbi

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=20110729140336.GU31013@legolas.emea.dhcp.ti.com \
    --to=balbi-l0cymroini0@public.gmane.org \
    --cc=andy-/Zus8d0mwwtBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=santosh.shilimkar-l0cyMroinI0@public.gmane.org \
    --cc=shubhrajyoti-l0cyMroinI0@public.gmane.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;
as well as URLs for NNTP newsgroup(s).