From: "Uwe Kleine-König" <u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Kevin Wells <kevin.wells-3arQi8VN3Tc@public.gmane.org>
Cc: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Russell King - ARM Linux
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
Vitaly Wool <vitalywool-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 1/1] Remove suspend/resume functionality, add dynamic clocking
Date: Thu, 26 Nov 2009 10:02:52 +0100 [thread overview]
Message-ID: <20091126090252.GB12179@pengutronix.de> (raw)
In-Reply-To: <083DF309106F364B939360100EC290F804F55C9225-SIPbe8o7cfX8DdpCu65jn8FrZmdRls4ZQQ4Iyu8u01E@public.gmane.org>
Hello,
can you please add something like "i2c-pnx: " to the subject?
(Actually it's a great strategy *not* to put it into the Subject. This
way it attracts far more attention :-)
> Remove suspend/resume functionality, I2C driver gates clock on
> only when an I2C transaction is in progress
What happens when the machine suspends while a transfer is in progress?
(This might be a problem that already existed before.) If this is
really a problem the easiest "fix" is to let the suspend callback return
-EBUSY in this case.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2009-11-26 9:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 21:23 [PATCH 1/1] Remove suspend/resume functionality, add dynamic clocking Kevin Wells
[not found] ` <083DF309106F364B939360100EC290F804F55C9225-SIPbe8o7cfX8DdpCu65jn8FrZmdRls4ZQQ4Iyu8u01E@public.gmane.org>
2009-11-26 9:02 ` Uwe Kleine-König [this message]
[not found] ` <20091126090252.GB12179-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-11-26 10:41 ` Russell King - ARM Linux
2009-11-30 17:02 ` Kevin Wells
[not found] ` <083DF309106F364B939360100EC290F804F5659CFF-SIPbe8o7cfX8DdpCu65jn8FrZmdRls4ZQQ4Iyu8u01E@public.gmane.org>
2009-12-06 8:47 ` Pavel Machek
[not found] ` <20091206084731.GE2766-+ZI9xUNit7I@public.gmane.org>
2009-12-06 21:02 ` Uwe Kleine-König
[not found] ` <20091206210225.GA20887-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-12-06 21:08 ` Pavel Machek
[not found] ` <20091206210739.GE10184-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2009-12-07 19:21 ` Kevin Wells
[not found] ` <083DF309106F364B939360100EC290F804F57A69FA-SIPbe8o7cfX8DdpCu65jn8FrZmdRls4ZQQ4Iyu8u01E@public.gmane.org>
2009-12-15 10:36 ` Pavel Machek
2009-11-30 23:19 ` Russell King - ARM Linux
[not found] ` <20091130231920.GB10705-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2009-12-01 18:25 ` Kevin Wells
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=20091126090252.GB12179@pengutronix.de \
--to=u.kleine-koenig-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=kevin.wells-3arQi8VN3Tc@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=vitalywool-Re5JQEeQqe8AvxtiuMwx3w@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