Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932342AbcDYMf0 (ORCPT ); Mon, 25 Apr 2016 08:35:26 -0400 Received: from hqemgate16.nvidia.com ([216.228.121.65]:13538 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932139AbcDYMfY (ORCPT ); Mon, 25 Apr 2016 08:35:24 -0400 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Mon, 25 Apr 2016 05:34:59 -0700 Subject: Re: [PATCH v6 1/4] i2c: tegra: disable clock before returning error To: Shardar Shariff Md , , , , , , , , References: <1461585458-23948-1-git-send-email-smohammed@nvidia.com> X-Nvconfidentiality: public From: Jon Hunter Message-ID: <571E0F05.60507@nvidia.com> Date: Mon, 25 Apr 2016 13:35:17 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <1461585458-23948-1-git-send-email-smohammed@nvidia.com> X-Originating-IP: [10.21.132.106] X-ClientProxiedBy: UKMAIL101.nvidia.com (10.26.138.13) To UKMAIL101.nvidia.com (10.26.138.13) Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1575 Lines: 53 On 25/04/16 12:57, Shardar Shariff Md wrote: > Disable clock before returning error in tegra_i2c_init() May be explain why we should do this? It looks like currently we will leave the clock on in the case of an error and so we may never turn it off again as now we have an unbalanced enable/disable, etc. > Signed-off-by: Shardar Shariff Md > > --- > Changes in v5: > - Move current patch as separate patch > > Changes in v6: > - Remove unnecessary line > --- > drivers/i2c/busses/i2c-tegra.c | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) > > diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c > index d764d64..445398c3 100644 > --- a/drivers/i2c/busses/i2c-tegra.c > +++ b/drivers/i2c/busses/i2c-tegra.c > @@ -483,19 +483,20 @@ static int tegra_i2c_init(struct tegra_i2c_dev *i2c_dev) > if (time_after(jiffies, timeout)) { > dev_warn(i2c_dev->dev, > "timeout waiting for config load\n"); > - return -ETIMEDOUT; > + err = -ETIMEDOUT; > + goto err; > } > msleep(1); > } > } > > - tegra_i2c_clock_disable(i2c_dev); > - > if (i2c_dev->irq_disabled) { > i2c_dev->irq_disabled = 0; > enable_irq(i2c_dev->irq); > } > > +err: > + tegra_i2c_clock_disable(i2c_dev); Thierry, Stephen, thinking about this some more I wonder if we should not change the order here, in case of a potential race between an interrupt and disabling the clock. May be it is safer to disable the clock first? However, this is in the init and so may be that is not likely? Cheers Jon