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
> [email protected]
> http://lists.lm-sensors.org/mailman/listinfo/i2c
--
Ben ([EMAIL PROTECTED], http://www.fluff.org/)
'a smiley only costs 4 bytes'
_______________________________________________
i2c mailing list
[email protected]
http://lists.lm-sensors.org/mailman/listinfo/i2c
