Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751868Ab2FLKZ2 (ORCPT ); Tue, 12 Jun 2012 06:25:28 -0400 Received: from hqemgate03.nvidia.com ([216.228.121.140]:16738 "EHLO hqemgate03.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750875Ab2FLKZZ (ORCPT ); Tue, 12 Jun 2012 06:25:25 -0400 X-PGP-Universal: processed; by hqnvupgp08.nvidia.com on Tue, 12 Jun 2012 03:25:25 -0700 Message-ID: <4FD71709.9040208@nvidia.com> Date: Tue, 12 Jun 2012 15:46:41 +0530 From: Laxman Dewangan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Wolfram Sang CC: "khali@linux-fr.org" , "ben-linux@fluff.org" , "swarren@wwwdotorg.org" , "olof@lixom.net" , "linux-i2c@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-tegra@vger.kernel.org" Subject: Re: [PATCH 1/4] i2c: tegra: make sure register writes completes References: <1338901800-23968-1-git-send-email-ldewangan@nvidia.com> <1338901800-23968-2-git-send-email-ldewangan@nvidia.com> <20120612075422.GB9230@pengutronix.de> In-Reply-To: <20120612075422.GB9230@pengutronix.de> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2122 Lines: 57 On Tuesday 12 June 2012 01:24 PM, Wolfram Sang wrote: > * PGP Signed by an unknown key > > On Tue, Jun 05, 2012 at 06:39:57PM +0530, Laxman Dewangan wrote: >> @@ -430,6 +430,13 @@ static irqreturn_t tegra_i2c_isr(int irq, void *dev_id) >> if (i2c_dev->is_dvc) >> dvc_writel(i2c_dev, DVC_STATUS_I2C_DONE_INTR, DVC_STATUS); >> >> + /* >> + * Register write get queued in the PPSB bus and write can >> + * happen later. Read back register to make sure that register >> + * write is completed. >> + */ >> + i2c_readl(i2c_dev, I2C_INT_STATUS); > Does it make sense to put the read into i2c_writel? > We can not put in i2c_writel() as we also do fifo write using this and writing and reading back fifo can drainout the fifo. hence putting this here seems more appropriate. >> + >> if (status& I2C_INT_PACKET_XFER_COMPLETE) { >> BUG_ON(i2c_dev->msg_buf_remaining); >> complete(&i2c_dev->msg_complete); >> @@ -444,6 +451,9 @@ err: >> if (i2c_dev->is_dvc) >> dvc_writel(i2c_dev, DVC_STATUS_I2C_DONE_INTR, DVC_STATUS); >> >> + /* Read back register to make sure that register writes completed */ >> + i2c_readl(i2c_dev, I2C_INT_STATUS); >> + >> complete(&i2c_dev->msg_complete); >> return IRQ_HANDLED; >> } >> @@ -505,6 +515,9 @@ static int tegra_i2c_xfer_msg(struct tegra_i2c_dev *i2c_dev, >> ret = wait_for_completion_timeout(&i2c_dev->msg_complete, TEGRA_I2C_TIMEOUT); >> tegra_i2c_mask_irq(i2c_dev, int_mask); >> >> + /* Read back register to make sure that register writes completed */ >> + i2c_readl(i2c_dev, I2C_INT_MASK); >> + > It definately makes sense to put this read into tegra_i2c_mask_irq()? > Ok, fine with me. I put the read back logic inside mask_irq() and unmask_irq(). Will send the fix in next patch. >> if (WARN_ON(ret == 0)) { >> dev_err(i2c_dev->dev, "i2c transfer timed out\n"); > Regards, > > Wolfram > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/