From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Kurtz <djkurtz@chromium.org>,
Daniel Vetter <daniel@ffwll.ch>,
Keith Packard <keithp@keithp.com>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: Benson Leung <bleung@chromium.org>,
Yufeng Shen <miletus@chromium.org>,
Daniel Kurtz <djkurtz@chromium.org>
Subject: Re: [PATCH 14/14 v5] drm/i915/intel_i2c: remove POSTING_READ() from gmbus transfers
Date: Wed, 28 Mar 2012 14:05:13 +0100 [thread overview]
Message-ID: <1332939924_127442@CP5-2952> (raw)
In-Reply-To: <1332939117-6513-15-git-send-email-djkurtz@chromium.org>
On Wed, 28 Mar 2012 20:51:57 +0800, Daniel Kurtz <djkurtz@chromium.org> wrote:
> The POSTING_READ() calls were originally added to make sure the writes
> were flushed before any timing delays and across loops.
> However, the normal I915_READ() and I915_WRITE() macros already call
> readl() / writel(), which already have an explicit mb().
>
> Now that the code has settled a bit, let's remove them.
>
> Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
> ---
> drivers/gpu/drm/i915/intel_i2c.c | 5 -----
> 1 files changed, 0 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_i2c.c b/drivers/gpu/drm/i915/intel_i2c.c
> index 2865313..be2852e 100644
> --- a/drivers/gpu/drm/i915/intel_i2c.c
> +++ b/drivers/gpu/drm/i915/intel_i2c.c
> @@ -131,7 +131,6 @@ static void set_clock(void *data, int state_high)
> GPIO_CLOCK_VAL_MASK;
>
> I915_WRITE_NOTRACE(bus->gpio_reg, reserved | clock_bits);
> - POSTING_READ(bus->gpio_reg);
We do need the write flush here (and set_data) as the next action is a
udelay loop which is not per-se a mb.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-28 13:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 12:51 [PATCH 00/14 v5] fix gmbus writes and related issues Daniel Kurtz
2012-03-28 12:51 ` [PATCH 01/14 v5] drm/i915/intel_i2c: refactor gmbus_xfer Daniel Kurtz
2012-03-28 12:51 ` [PATCH 02/14 v5] drm/i915/intel_i2c: cleanup error messages and comments Daniel Kurtz
2012-03-28 12:51 ` [PATCH 03/14 v5] drm/i915/intel_i2c: assign HDMI port D to pin pair 6 Daniel Kurtz
2012-03-28 12:51 ` [PATCH 04/14 v5] drm/i915/intel_i2c: use i2c pre/post_xfer functions to setup gpio xfers Daniel Kurtz
2012-03-28 12:51 ` [PATCH 05/14 v5] drm/i915/intel_i2c: refactor using intel_gmbus_get_adapter Daniel Kurtz
2012-03-28 12:51 ` [PATCH 06/14 v5] drm/i915/intel_i2c: gmbus disabled and reserved ports are invalid Daniel Kurtz
2012-03-28 12:51 ` [PATCH 07/14 v5] drm/i915/intel_i2c: allocate gmbus array as part of drm_i915_private Daniel Kurtz
2012-03-28 12:51 ` [PATCH 08/14 v5] drm/i915/intel_i2c: handle zero-length writes Daniel Kurtz
2012-03-28 12:51 ` [PATCH 09/14 v5] drm/i915/intel_i2c: use double-buffered writes Daniel Kurtz
2012-03-28 12:51 ` [PATCH 10/14 v5] drm/i915/intel_i2c: always wait for IDLE before clearing NAK Daniel Kurtz
2012-03-28 12:51 ` [PATCH 11/14 v5] drm/i915/intel_i2c: use WAIT cycle, not STOP Daniel Kurtz
2012-03-28 12:51 ` [PATCH 12/14 v5] drm/i915/intel_i2c: use INDEX cycles for i2c read transactions Daniel Kurtz
2012-03-28 12:51 ` [PATCH 13/14 v5] drm/i915/intel_i2c: reuse GMBUS2 value read in polling loop Daniel Kurtz
2012-03-28 12:51 ` [PATCH 14/14 v5] drm/i915/intel_i2c: remove POSTING_READ() from gmbus transfers Daniel Kurtz
2012-03-28 13:05 ` Chris Wilson [this message]
2012-03-28 13:21 ` Daniel Kurtz
2012-03-28 14:30 ` Chris Wilson
2012-03-28 14:46 ` Daniel Vetter
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=1332939924_127442@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=bleung@chromium.org \
--cc=daniel@ffwll.ch \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miletus@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox