From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751714AbdBFJcv (ORCPT ); Mon, 6 Feb 2017 04:32:51 -0500 Received: from mga06.intel.com ([134.134.136.31]:58945 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751632AbdBFJcu (ORCPT ); Mon, 6 Feb 2017 04:32:50 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,341,1477983600"; d="scan'208";a="817533165" Subject: Re: [PATCH] i2c: designwear: Fix clk warning on suspend/resume To: John Stultz , lkml References: <1486162893-12313-1-git-send-email-john.stultz@linaro.org> Cc: Andy Shevchenko , Mika Westerberg , Wolfram Sang , linux-i2c@vger.kernel.org From: Jarkko Nikula Message-ID: Date: Mon, 6 Feb 2017 11:32:46 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0 MIME-Version: 1.0 In-Reply-To: <1486162893-12313-1-git-send-email-john.stultz@linaro.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On 04.02.2017 01:01, John Stultz wrote: > On my HiKey board, I'm seeing clk warnings on suspend/resume, which > seem to be caused by runtime pm suspending the device, then the same > suspend hook being called again on suspend time. > > Thus this patch adds suspend state tracking to avoid runtime pm and > suspend causing double suspend calls on i2c-designware-platdrv. > > Feedback would be greatly appreciated! > > Cc: Jarkko Nikula > Cc: Andy Shevchenko > Cc: Mika Westerberg > Cc: Wolfram Sang > Cc: linux-i2c@vger.kernel.org > Signed-off-by: John Stultz > --- > drivers/i2c/busses/i2c-designware-core.h | 1 + > drivers/i2c/busses/i2c-designware-platdrv.c | 9 +++++++++ > 2 files changed, 10 insertions(+) > ... > @@ -340,8 +340,12 @@ static int dw_i2c_plat_suspend(struct device *dev) > struct platform_device *pdev = to_platform_device(dev); > struct dw_i2c_dev *i_dev = platform_get_drvdata(pdev); > > + if (i_dev->suspended) > + return 0; > + > i2c_dw_disable(i_dev); > i2c_dw_plat_prepare_clk(i_dev, false); > + i_dev->suspended = true; > This feels a band-aid fix. At quick look some drivers appear to use SET_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend, pm_runtime_force_resume) in their dev_pm_ops. Could you try does it help in your case and I'll check our platforms. -- Jarkko