From: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
To: Shubhrajyoti <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,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH][RFC] OMAP4: I2C : I2C context save
Date: Tue, 05 Jul 2011 11:31:23 -0700 [thread overview]
Message-ID: <87y60cr344.fsf@ti.com> (raw)
In-Reply-To: <4DFF6A9E.5050209-l0cyMroinI0@public.gmane.org> (shubhrajyoti-l0cyMroinI0@public.gmane.org's message of "Mon, 20 Jun 2011 21:13:26 +0530")
Shubhrajyoti <shubhrajyoti-l0cyMroinI0@public.gmane.org> writes:
> On Monday 20 June 2011 09:05 PM, Kevin Hilman wrote:
>> 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.
> Yes , missed out.
>> Also, please describe why this hwmod data change affects the problem
>> described in the changelog.
>>
> After Andy's patch set
> <code snippet>
> static void omap_i2c_unidle(struct omap_i2c_dev *dev)
> {
> <snip>
>
> pm_runtime_get_sync(&pdev->dev);
>
> if (pdata->flags & OMAP_I2C_FLAG_RESET_REGS_POSTIDLE) {
> omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, 0);
> omap_i2c_write_reg(dev, OMAP_I2C_PSC_REG, dev->pscstate);
> omap_i2c_write_reg(dev, OMAP_I2C_SCLL_REG, dev->scllstate);
> omap_i2c_write_reg(dev, OMAP_I2C_SCLH_REG, dev->sclhstate);
> omap_i2c_write_reg(dev, OMAP_I2C_BUF_REG, dev->bufstate);
> omap_i2c_write_reg(dev, OMAP_I2C_SYSC_REG, dev->syscstate);
> omap_i2c_write_reg(dev, OMAP_I2C_WE_REG, dev->westate);
> omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, OMAP_I2C_CON_EN);
> }
> dev->idle = 0;
>
> This is dependent on the flag, I am making it true for OMAP4 also.
What I meant was: please describe this in the changelog. Without more
detail, the hwmod change itself is not understandable.
Kevin
next prev parent reply other threads:[~2011-07-05 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308559552-24028-1-git-send-email-shubhrajyoti@ti.com>
[not found] ` <87ips08qis.fsf@ti.com>
[not found] ` <87ips08qis.fsf-l0cyMroinI0@public.gmane.org>
2011-06-20 15:43 ` [PATCH][RFC] OMAP4: I2C : I2C context save Shubhrajyoti
[not found] ` <4DFF6A9E.5050209-l0cyMroinI0@public.gmane.org>
2011-07-05 18:31 ` Kevin Hilman [this message]
[not found] ` <87y60cr344.fsf-l0cyMroinI0@public.gmane.org>
2011-07-06 6:21 ` Shubhrajyoti
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=87y60cr344.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=linux-omap-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