From: Ben Dooks <ben-linux@fluff.org>
To: Darius <augulis.darius@gmail.com>
Cc: i2c@lm-sensors.org, Ben Dooks <ben-linux@fluff.org>,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [i2c] [PATCH V6] I2C driver for IMX
Date: Mon, 16 Jun 2008 00:56:01 +0100 [thread overview]
Message-ID: <20080615235601.GB30539@fluff.org.uk> (raw)
In-Reply-To: <4851139B.9000105@gmail.com>
On Thu, Jun 12, 2008 at 03:16:27PM +0300, Darius wrote:
> >> +static struct platform_driver i2c_imx_driver = {
> >> + .probe = i2c_imx_probe,
> >> + .remove = i2c_imx_remove,
> >> + .driver = {
> >> + .name = DRIVER_NAME,
> >> + .owner = THIS_MODULE,
> >> + }
> >> +};
> >
> > No suspend/resume support? See above note on ordering.
> >
>
> There are nothing to do in suspend/resume routines, because no possibility to turn off I2C clock.
> I2C module itself is disabled every time when data is not transmited.
> Seems, that there are only few I2C drivers (at91, blackfin, pnx) with suspend/resume suport.
> Most drivers has not suspend/resume support.
It depends, does the hardware keep the peripheral state during
suspend?
> Should I declare empty suspend/resume routines with return 0; only?
No, the system ignores NULL suspend/resume entries.
> _______________________________________________
> i2c mailing list
> i2c@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/i2c
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2008-06-15 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 6:41 [PATCH V6] I2C driver for IMX Darius
2008-06-01 22:09 ` [i2c] " Ben Dooks
2008-06-12 12:16 ` Darius
2008-06-15 23:56 ` Ben Dooks [this message]
2008-06-16 8:32 ` Darius
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=20080615235601.GB30539@fluff.org.uk \
--to=ben-linux@fluff.org \
--cc=augulis.darius@gmail.com \
--cc=i2c@lm-sensors.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
/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