From: Shubhrajyoti <shubhrajyoti-l0cyMroinI0@public.gmane.org>
To: Jon Hunter <jon-hunter-l0cyMroinI0@public.gmane.org>
Cc: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>,
Alexander Aring <a.aring-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c_omap: correct OMAP_I2C_SYSC_REG offset
Date: Fri, 09 Dec 2011 12:16:00 +0530 [thread overview]
Message-ID: <4EE1AEA8.6000008@ti.com> (raw)
In-Reply-To: <4EE11091.20404-l0cyMroinI0@public.gmane.org>
On Friday 09 December 2011 01:01 AM, Jon Hunter wrote:
> Hi Kevin,
>
> On 12/8/2011 12:12, Kevin Hilman wrote:
>> Alexander Aring<a.aring-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org> writes:
>>
>>> Correct OMAP_I2C_SYSC_REG offset in omap4 register map.
>>> Offset 0x20 is reserved and OMAP_I2C_SYSC_REG has 0x10 as offset.
>>>
>>> Signed-off-by: Alexander Aring<a.aring-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
>>
>> Thanks for the patch!
>>
>> A different approach to fix this is being done by Shubhrajyoti[1] as
>> part of his reset series.
>>
>> However, I think we should probably apply this patch for v3.2 and also
>> send to the stable kernel for v3.0& v3.1.
>>
>> Shubhrajyoti/Jon, any objections to me queuing this fix for v3.2 (and
>> stable.) It would just mean rebasing your other fixes and cleanup
>> series on top of this.
>
> I have no issue with that and I am in favour of getting the fix in now.
I too have no issues.
>
> Cheers
> Jon
>
>>
>>> ---
>>> drivers/i2c/busses/i2c-omap.c | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/drivers/i2c/busses/i2c-omap.c
>>> b/drivers/i2c/busses/i2c-omap.c
>>> index a43d002..fc3bb37 100644
>>> --- a/drivers/i2c/busses/i2c-omap.c
>>> +++ b/drivers/i2c/busses/i2c-omap.c
>>> @@ -235,7 +235,7 @@ static const u8 reg_map_ip_v2[] = {
>>> [OMAP_I2C_BUF_REG] = 0x94,
>>> [OMAP_I2C_CNT_REG] = 0x98,
>>> [OMAP_I2C_DATA_REG] = 0x9c,
>>> - [OMAP_I2C_SYSC_REG] = 0x20,
>>> + [OMAP_I2C_SYSC_REG] = 0x10,
>>> [OMAP_I2C_CON_REG] = 0xa4,
>>> [OMAP_I2C_OA_REG] = 0xa8,
>>> [OMAP_I2C_SA_REG] = 0xac,
next prev parent reply other threads:[~2011-12-09 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 14:43 [PATCH] i2c_omap: correct OMAP_I2C_SYSC_REG offset Alexander Aring
[not found] ` <1323355433-8508-1-git-send-email-a.aring-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2011-12-08 18:12 ` Kevin Hilman
[not found] ` <87obvjj5l5.fsf-l0cyMroinI0@public.gmane.org>
2011-12-08 19:31 ` Jon Hunter
[not found] ` <4EE11091.20404-l0cyMroinI0@public.gmane.org>
2011-12-09 6:46 ` Shubhrajyoti [this message]
[not found] ` <4EE1AEA8.6000008-l0cyMroinI0@public.gmane.org>
2011-12-09 17:51 ` Kevin Hilman
2011-12-09 18:03 ` 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=4EE1AEA8.6000008@ti.com \
--to=shubhrajyoti-l0cymroini0@public.gmane.org \
--cc=a.aring-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=jon-hunter-l0cyMroinI0@public.gmane.org \
--cc=khilman-l0cyMroinI0@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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).