From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org,
olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] i2c: tegra: make sure register writes completes
Date: Tue, 12 Jun 2012 09:54:22 +0200 [thread overview]
Message-ID: <20120612075422.GB9230@pengutronix.de> (raw)
In-Reply-To: <1338901800-23968-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2512 bytes --]
On Tue, Jun 05, 2012 at 06:39:57PM +0530, Laxman Dewangan wrote:
> The Tegra PPSB (an peripheral bus) queues writes transactions.
> In order to guarantee that writes have completed before a
> certain time, a read transaction to a register on the same
> bus must be executed.
> This is necessary in situations such as when clearing an
> interrupt status or enable, so that when returning from an
> interrupt handler, the HW has already de-asserted its
> interrupt status output, which will avoid spurious interrupts.
>
> Signed-off-by: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> ---
> drivers/i2c/busses/i2c-tegra.c | 13 +++++++++++++
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index 8b2e555..fa92396 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -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?
> +
> 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()?
> if (WARN_ON(ret == 0)) {
> dev_err(i2c_dev->dev, "i2c transfer timed out\n");
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <w.sang@pengutronix.de>
To: Laxman Dewangan <ldewangan@nvidia.com>
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
Date: Tue, 12 Jun 2012 09:54:22 +0200 [thread overview]
Message-ID: <20120612075422.GB9230@pengutronix.de> (raw)
In-Reply-To: <1338901800-23968-2-git-send-email-ldewangan@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
On Tue, Jun 05, 2012 at 06:39:57PM +0530, Laxman Dewangan wrote:
> The Tegra PPSB (an peripheral bus) queues writes transactions.
> In order to guarantee that writes have completed before a
> certain time, a read transaction to a register on the same
> bus must be executed.
> This is necessary in situations such as when clearing an
> interrupt status or enable, so that when returning from an
> interrupt handler, the HW has already de-asserted its
> interrupt status output, which will avoid spurious interrupts.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> drivers/i2c/busses/i2c-tegra.c | 13 +++++++++++++
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index 8b2e555..fa92396 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -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?
> +
> 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()?
> if (WARN_ON(ret == 0)) {
> dev_err(i2c_dev->dev, "i2c transfer timed out\n");
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-06-12 7:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 13:09 [PATCH 0/4] i2c: tegra: Bug fixes, cleanups and M_NOSTART support Laxman Dewangan
2012-06-05 13:09 ` Laxman Dewangan
2012-06-05 13:09 ` [PATCH 1/4] i2c: tegra: make sure register writes completes Laxman Dewangan
2012-06-05 13:09 ` Laxman Dewangan
[not found] ` <1338901800-23968-2-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-12 7:54 ` Wolfram Sang [this message]
2012-06-12 7:54 ` Wolfram Sang
[not found] ` <20120612075422.GB9230-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-06-12 10:16 ` Laxman Dewangan
2012-06-12 10:16 ` Laxman Dewangan
[not found] ` <4FD71709.9040208-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-12 16:07 ` Stephen Warren
2012-06-12 16:07 ` Stephen Warren
2012-06-05 13:09 ` [PATCH 2/4] i2c: tegra: add PROTOCOL_MANGLING as supported functionality Laxman Dewangan
2012-06-05 13:09 ` Laxman Dewangan
[not found] ` <1338901800-23968-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-05 13:09 ` [PATCH 3/4] i2c: tegra: support for I2C_M_NOSTART functionality Laxman Dewangan
2012-06-05 13:09 ` Laxman Dewangan
2012-06-05 16:14 ` [PATCH 0/4] i2c: tegra: Bug fixes, cleanups and M_NOSTART support Stephen Warren
2012-06-05 16:14 ` Stephen Warren
[not found] ` <4FCE3078.1030008-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-06-05 17:07 ` Laxman Dewangan
2012-06-05 17:07 ` Laxman Dewangan
[not found] ` <4FCE3CD8.8060502-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-12 8:50 ` Wolfram Sang
2012-06-12 8:50 ` Wolfram Sang
[not found] ` <20120612085040.GC9230-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-06-12 16:05 ` Stephen Warren
2012-06-12 16:05 ` Stephen Warren
2012-06-05 13:10 ` [PATCH 4/4] i2c: tegra: make all resource allocation through devm_* Laxman Dewangan
2012-06-05 13:10 ` Laxman Dewangan
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=20120612075422.GB9230@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
/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.