From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
"khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org"
<khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
"ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org"
<ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
"olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org"
<olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-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 10:07:03 -0600 [thread overview]
Message-ID: <4FD76927.8040702@wwwdotorg.org> (raw)
In-Reply-To: <4FD71709.9040208-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 06/12/2012 04:16 AM, Laxman Dewangan wrote:
> 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.
You can put it inside i2c_writel(), but make the read-back conditional
depending on which register was just written. The Tegra SD driver has
similar conditional code in readl/writel to WAR some HW quirks.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
"khali@linux-fr.org" <khali@linux-fr.org>,
"ben-linux@fluff.org" <ben-linux@fluff.org>,
"olof@lixom.net" <olof@lixom.net>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@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 10:07:03 -0600 [thread overview]
Message-ID: <4FD76927.8040702@wwwdotorg.org> (raw)
In-Reply-To: <4FD71709.9040208@nvidia.com>
On 06/12/2012 04:16 AM, Laxman Dewangan wrote:
> 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.
You can put it inside i2c_writel(), but make the read-back conditional
depending on which register was just written. The Tegra SD driver has
similar conditional code in readl/writel to WAR some HW quirks.
next prev parent reply other threads:[~2012-06-12 16:07 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
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 [this message]
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
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
[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
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=4FD76927.8040702@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@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=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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.