From: Darius <augulis.darius@gmail.com>
To: linux-arm-kernel@lists.arm.linux.org.uk
Cc: i2c@lm-sensors.org
Subject: Re: [i2c] [PATCH V6] I2C driver for IMX
Date: Mon, 16 Jun 2008 11:32:22 +0300 [thread overview]
Message-ID: <g358q6$m2f$1@ger.gmane.org> (raw)
In-Reply-To: <20080615235601.GB30539@fluff.org.uk>
Ben Dooks wrote:
> 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?
yes, all registers remains unchanged.
>
>> Should I declare empty suspend/resume routines with return 0; only?
>
> No, the system ignores NULL suspend/resume entries.
also, I'll don't implement suspend, because no reason to do so.
I have next patch version with other your comments corrected.
>
>> _______________________________________________
>> i2c mailing list
>> i2c@lm-sensors.org
>> http://lists.lm-sensors.org/mailman/listinfo/i2c
>
-------------------------------------------------------------------
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
prev parent reply other threads:[~2008-06-16 8:32 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
2008-06-16 8:32 ` Darius [this message]
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='g358q6$m2f$1@ger.gmane.org' \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.