2014-06-24 23:56:59

by Doug Anderson

[permalink] [raw]
Subject: [PATCH v2] i2c: s3c2410: resume the I2C controller earlier

From: Vincent Palatin <[email protected]>

When the wake-up is triggered by the PMIC RTC, the RTC driver is trying
to read the PMIC interrupt status over I2C and fails because the I2C
controller is not resumed yet.
Let's resume the I2C controller earlier in the _noirq phase
(as other hardwares are doing), so we can properly get the wake-up
condition.

Signed-off-by: Vincent Palatin <[email protected]>
Signed-off-by: Doug Anderson <[email protected]>
---
Changes in v2:
- Added missing freeze/thaw/poweroff/restore

drivers/i2c/busses/i2c-s3c2410.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
index e828a1d..ecb389c 100644
--- a/drivers/i2c/busses/i2c-s3c2410.c
+++ b/drivers/i2c/busses/i2c-s3c2410.c
@@ -1267,7 +1267,7 @@ static int s3c24xx_i2c_suspend_noirq(struct device *dev)
return 0;
}

-static int s3c24xx_i2c_resume(struct device *dev)
+static int s3c24xx_i2c_resume_noirq(struct device *dev)
{
struct platform_device *pdev = to_platform_device(dev);
struct s3c24xx_i2c *i2c = platform_get_drvdata(pdev);
@@ -1285,7 +1285,11 @@ static int s3c24xx_i2c_resume(struct device *dev)
static const struct dev_pm_ops s3c24xx_i2c_dev_pm_ops = {
#ifdef CONFIG_PM_SLEEP
.suspend_noirq = s3c24xx_i2c_suspend_noirq,
- .resume = s3c24xx_i2c_resume,
+ .resume_noirq = s3c24xx_i2c_resume_noirq,
+ .freeze_noirq = s3c24xx_i2c_suspend_noirq,
+ .thaw_noirq = s3c24xx_i2c_resume_noirq,
+ .poweroff_noirq = s3c24xx_i2c_suspend_noirq,
+ .restore_noirq = s3c24xx_i2c_resume_noirq,
#endif
};

--
2.0.0.526.g5318336


2014-06-25 18:09:51

by Javier Martinez Canillas

[permalink] [raw]
Subject: Re: [PATCH v2] i2c: s3c2410: resume the I2C controller earlier

Hello Doug,

On 06/25/2014 01:56 AM, Doug Anderson wrote:
> From: Vincent Palatin <[email protected]>
>
> When the wake-up is triggered by the PMIC RTC, the RTC driver is trying
> to read the PMIC interrupt status over I2C and fails because the I2C
> controller is not resumed yet.
> Let's resume the I2C controller earlier in the _noirq phase
> (as other hardwares are doing), so we can properly get the wake-up
> condition.
>
> Signed-off-by: Vincent Palatin <[email protected]>
> Signed-off-by: Doug Anderson <[email protected]>
> ---
> Changes in v2:
> - Added missing freeze/thaw/poweroff/restore
>
> drivers/i2c/busses/i2c-s3c2410.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
> index e828a1d..ecb389c 100644
> --- a/drivers/i2c/busses/i2c-s3c2410.c
> +++ b/drivers/i2c/busses/i2c-s3c2410.c
> @@ -1267,7 +1267,7 @@ static int s3c24xx_i2c_suspend_noirq(struct device *dev)
> return 0;
> }
>
> -static int s3c24xx_i2c_resume(struct device *dev)
> +static int s3c24xx_i2c_resume_noirq(struct device *dev)
> {
> struct platform_device *pdev = to_platform_device(dev);
> struct s3c24xx_i2c *i2c = platform_get_drvdata(pdev);
> @@ -1285,7 +1285,11 @@ static int s3c24xx_i2c_resume(struct device *dev)
> static const struct dev_pm_ops s3c24xx_i2c_dev_pm_ops = {
> #ifdef CONFIG_PM_SLEEP
> .suspend_noirq = s3c24xx_i2c_suspend_noirq,
> - .resume = s3c24xx_i2c_resume,
> + .resume_noirq = s3c24xx_i2c_resume_noirq,
> + .freeze_noirq = s3c24xx_i2c_suspend_noirq,
> + .thaw_noirq = s3c24xx_i2c_resume_noirq,
> + .poweroff_noirq = s3c24xx_i2c_suspend_noirq,
> + .restore_noirq = s3c24xx_i2c_resume_noirq,
> #endif
> };
>
>

Looks good to me.

Reviewed-by: Javier Martinez Canillas <[email protected]>

Best regards,
Javier

2014-06-30 18:01:25

by Tomasz Figa

[permalink] [raw]
Subject: Re: [PATCH v2] i2c: s3c2410: resume the I2C controller earlier

Hi Doug,

On 25.06.2014 01:56, Doug Anderson wrote:
> From: Vincent Palatin <[email protected]>
>
> When the wake-up is triggered by the PMIC RTC, the RTC driver is trying
> to read the PMIC interrupt status over I2C and fails because the I2C
> controller is not resumed yet.
> Let's resume the I2C controller earlier in the _noirq phase
> (as other hardwares are doing), so we can properly get the wake-up
> condition.
>
> Signed-off-by: Vincent Palatin <[email protected]>
> Signed-off-by: Doug Anderson <[email protected]>
> ---
> Changes in v2:
> - Added missing freeze/thaw/poweroff/restore
>
> drivers/i2c/busses/i2c-s3c2410.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-s3c2410.c b/drivers/i2c/busses/i2c-s3c2410.c
> index e828a1d..ecb389c 100644
> --- a/drivers/i2c/busses/i2c-s3c2410.c
> +++ b/drivers/i2c/busses/i2c-s3c2410.c
> @@ -1267,7 +1267,7 @@ static int s3c24xx_i2c_suspend_noirq(struct device *dev)
> return 0;
> }
>
> -static int s3c24xx_i2c_resume(struct device *dev)
> +static int s3c24xx_i2c_resume_noirq(struct device *dev)
> {
> struct platform_device *pdev = to_platform_device(dev);
> struct s3c24xx_i2c *i2c = platform_get_drvdata(pdev);
> @@ -1285,7 +1285,11 @@ static int s3c24xx_i2c_resume(struct device *dev)
> static const struct dev_pm_ops s3c24xx_i2c_dev_pm_ops = {
> #ifdef CONFIG_PM_SLEEP
> .suspend_noirq = s3c24xx_i2c_suspend_noirq,
> - .resume = s3c24xx_i2c_resume,
> + .resume_noirq = s3c24xx_i2c_resume_noirq,
> + .freeze_noirq = s3c24xx_i2c_suspend_noirq,
> + .thaw_noirq = s3c24xx_i2c_resume_noirq,
> + .poweroff_noirq = s3c24xx_i2c_suspend_noirq,
> + .restore_noirq = s3c24xx_i2c_resume_noirq,
> #endif
> };

Also fixes certain issues on Exynos4-based boards.

Acked-by: Tomasz Figa <[email protected]>

--
Best regards,
Tomasz

2014-07-16 17:35:53

by Wolfram Sang

[permalink] [raw]
Subject: Re: [PATCH v2] i2c: s3c2410: resume the I2C controller earlier

On Tue, Jun 24, 2014 at 04:56:54PM -0700, Doug Anderson wrote:
> From: Vincent Palatin <[email protected]>
>
> When the wake-up is triggered by the PMIC RTC, the RTC driver is trying
> to read the PMIC interrupt status over I2C and fails because the I2C
> controller is not resumed yet.
> Let's resume the I2C controller earlier in the _noirq phase
> (as other hardwares are doing), so we can properly get the wake-up
> condition.
>
> Signed-off-by: Vincent Palatin <[email protected]>
> Signed-off-by: Doug Anderson <[email protected]>

Applied to for-current (because Tomasz said it fixes issues), thanks! If
you think the exynos patch of the same style should also be in current,
please let me know...


Attachments:
(No filename) (720.00 B)
signature.asc (819.00 B)
Digital signature
Download all attachments

2014-07-16 22:31:59

by Doug Anderson

[permalink] [raw]
Subject: Re: [PATCH v2] i2c: s3c2410: resume the I2C controller earlier

Wolfram,

On Wed, Jul 16, 2014 at 10:35 AM, Wolfram Sang <[email protected]> wrote:
> On Tue, Jun 24, 2014 at 04:56:54PM -0700, Doug Anderson wrote:
>> From: Vincent Palatin <[email protected]>
>>
>> When the wake-up is triggered by the PMIC RTC, the RTC driver is trying
>> to read the PMIC interrupt status over I2C and fails because the I2C
>> controller is not resumed yet.
>> Let's resume the I2C controller earlier in the _noirq phase
>> (as other hardwares are doing), so we can properly get the wake-up
>> condition.
>>
>> Signed-off-by: Vincent Palatin <[email protected]>
>> Signed-off-by: Doug Anderson <[email protected]>
>
> Applied to for-current (because Tomasz said it fixes issues), thanks! If
> you think the exynos patch of the same style should also be in current,
> please let me know...

Thanks! I don't think the exynos one needs to go into for-current.
for-next is enough. :)

-Doug