public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
To: shubhrajyoti-l0cyMroinI0@public.gmane.org
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
	andy.green-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH][RFC] OMAP4: I2C : I2C context save
Date: Mon, 20 Jun 2011 08:35:23 -0700	[thread overview]
Message-ID: <87ips08qis.fsf@ti.com> (raw)
In-Reply-To: <1308559552-24028-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org> (shubhrajyoti-l0cyMroinI0@public.gmane.org's message of "Mon, 20 Jun 2011 14:15:52 +0530")

shubhrajyoti-l0cyMroinI0@public.gmane.org writes:

> From: Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org>
>
> Currently the OMAP4 doesnot hit device off still the
> driver may have support for it.Adding support for the
> same.
>
> Signed-off-by: Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org>

Please Cc linux-omap as this change to the hwmod data would go through
Tony.

Also, please describe why this hwmod data change affects the problem
described in the changelog.

Kevin

> ---
> Applies on top of patches from Andy Green
> http://www.spinics.net/lists/linux-i2c/msg05632.html
>
>  arch/arm/mach-omap2/omap_hwmod_44xx_data.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 0fe9556..5e2c748 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -2130,7 +2130,8 @@ static struct omap_hwmod_class omap44xx_i2c_hwmod_class = {
>  };
>  
>  static struct omap_i2c_dev_attr i2c_dev_attr = {
> -	.flags  = OMAP_I2C_FLAG_BUS_SHIFT_NONE,
> +	.flags  = OMAP_I2C_FLAG_BUS_SHIFT_NONE |
> +			OMAP_I2C_FLAG_RESET_REGS_POSTIDLE,
>  };
>  
>  /* i2c1 */

  parent reply	other threads:[~2011-06-20 15:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20  8:45 [PATCH][RFC] OMAP4: I2C : I2C context save shubhrajyoti-l0cyMroinI0
     [not found] ` <1308559552-24028-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-06-20 15:35   ` Kevin Hilman [this message]
     [not found]     ` <87ips08qis.fsf-l0cyMroinI0@public.gmane.org>
2011-06-20 15:43       ` Shubhrajyoti
     [not found]         ` <4DFF6A9E.5050209-l0cyMroinI0@public.gmane.org>
2011-07-05 18:31           ` Kevin Hilman
     [not found]             ` <87y60cr344.fsf-l0cyMroinI0@public.gmane.org>
2011-07-06  6:21               ` Shubhrajyoti
  -- strict thread matches above, loose matches on Subject: below --
2011-07-05  9:20 Shubhrajyoti D
     [not found] ` <1309857646-29401-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-07-13 19:07   ` Ben Dooks
2011-07-13 21:15     ` Kevin Hilman
     [not found]       ` <87k4blopaw.fsf-l0cyMroinI0@public.gmane.org>
2011-07-13 21:27         ` Hilman, Kevin
2011-07-14 10:53           ` Shubhrajyoti
     [not found]             ` <4E1ECABA.7010306-l0cyMroinI0@public.gmane.org>
2011-07-14 15:38               ` 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=87ips08qis.fsf@ti.com \
    --to=khilman-l0cymroini0@public.gmane.org \
    --cc=andy.green-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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