From: David Brownell <david-b@pacbell.net>
To: Tony Lindgren <tony@atomide.com>
Cc: Jean Delvare <khali@linux-fr.org>,
linux-omap@vger.kernel.org, i2c@lm-sensors.org
Subject: Re: [PATCH] I2C: Fix unhandled fault in i2c-omap controller, take #2
Date: Mon, 17 Mar 2008 00:07:49 -0800 [thread overview]
Message-ID: <200803170107.50083.david-b@pacbell.net> (raw)
In-Reply-To: <20080317071949.GP11653@atomide.com>
On Monday 17 March 2008, Tony Lindgren wrote:
> @@ -360,7 +374,7 @@ omap_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg msgs[], int num)
> int i;
> int r;
>
> - omap_i2c_enable_clocks(dev);
> + omap_i2c_unidle(dev);
>
> if ((r = omap_i2c_wait_for_bb(dev)) < 0)
> goto out;
> @@ -374,7 +388,7 @@ omap_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg msgs[], int num)
> if (r == 0)
> r = num;
> out:
> - omap_i2c_disable_clocks(dev);
> + omap_i2c_idle(dev);
> return r;
> }
>
Wouldn't it be nice -- from a pure power management perspective
of course! -- if more drivers were this careful about idling
their clocks when they have no work to do. ;)
- Dave
--
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
next prev parent reply other threads:[~2008-03-17 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 15:51 I2C: Fix unhandled fault in i2c-omap controller Tony Lindgren
[not found] ` <20080313155123.GI11653-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2008-03-14 15:53 ` Jean Delvare
2008-03-17 6:39 ` Tony Lindgren
2008-03-14 17:52 ` Jean Delvare
2008-03-17 6:46 ` Tony Lindgren
2008-03-17 7:19 ` [PATCH] I2C: Fix unhandled fault in i2c-omap controller, take #2 Tony Lindgren
2008-03-17 8:07 ` David Brownell [this message]
[not found] ` <20080317071949.GP11653-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2008-03-17 11:05 ` Jean Delvare
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=200803170107.50083.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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