linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linuxzsc@gmail.com (Richard Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] i2c: imx: only imx1 needs disable delay
Date: Thu,  1 Oct 2009 09:13:31 +0800	[thread overview]
Message-ID: <1254359613-21210-2-git-send-email-linuxzsc@gmail.com> (raw)
In-Reply-To: <1254359613-21210-1-git-send-email-linuxzsc@gmail.com>

check cpu_is_mx1() when set disable_delay.

Signed-off-by: Richard Zhao <linuxzsc@gmail.com>

diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
index 156cc95..c1e541c 100644
--- a/drivers/i2c/busses/i2c-imx.c
+++ b/drivers/i2c/busses/i2c-imx.c
@@ -254,14 +254,16 @@ static void __init i2c_imx_set_clk(struct imx_i2c_struct *i2c_imx,
 	/* Write divider value to register */
 	writeb(i2c_clk_div[i][1], i2c_imx->base + IMX_I2C_IFDR);
 
-	/*
-	 * There dummy delay is calculated.
-	 * It should be about one I2C clock period long.
-	 * This delay is used in I2C bus disable function
-	 * to fix chip hardware bug.
-	 */
-	i2c_imx->disable_delay = (500000U * i2c_clk_div[i][0]
-		+ (i2c_clk_rate / 2) - 1) / (i2c_clk_rate / 2);
+	if (cpu_is_mx1()) {
+		/*
+		 * There dummy delay is calculated.
+		 * It should be about one I2C clock period long.
+		 * This delay is used in I2C bus disable function
+		 * to fix chip hardware bug.
+		 */
+		i2c_imx->disable_delay = (500000U * i2c_clk_div[i][0]
+			+ (i2c_clk_rate / 2) - 1) / (i2c_clk_rate / 2);
+	}
 
 	/* dev_dbg() can't be used, because adapter is not yet registered */
 #ifdef CONFIG_I2C_DEBUG_BUS
-- 
1.6.0.4

  reply	other threads:[~2009-10-01  1:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01  1:13 [PATCH 1/4] i2c: imx: check busy bit when START/STOP Richard Zhao
2009-10-01  1:13 ` Richard Zhao [this message]
2009-10-01  1:13   ` [PATCH 3/4] i2c: imx: add macros and printk to make debug easy Richard Zhao
2009-10-01  1:13     ` [PATCH 4/4] i2c: imx: disable clock when it's possible to save power Richard Zhao
2009-10-01  7:34       ` Sascha Hauer
2009-10-01  7:56         ` Richard Zhao
2009-10-01  8:00           ` Sascha Hauer
2009-10-04 12:30             ` Richard Zhao
2009-10-01  7:29     ` [PATCH 3/4] i2c: imx: add macros and printk to make debug easy Sascha Hauer
2009-10-01  8:01       ` Richard Zhao
2009-10-01  8:26         ` Sascha Hauer
2009-10-01  9:30           ` Richard Zhao
2009-10-04 12:23             ` Richard Zhao
2009-10-01  7:26   ` [PATCH 2/4] i2c: imx: only imx1 needs disable delay Sascha Hauer
2009-10-01  7:52     ` Richard Zhao
2009-10-01  7:57       ` Sascha Hauer
2009-10-01  8:03 ` [PATCH 1/4] i2c: imx: check busy bit when START/STOP Richard Zhao
2009-10-01  8:38   ` Sascha Hauer
2009-10-01  9:11     ` Richard Zhao
2009-10-01  9:52       ` Sascha Hauer
2009-10-01 14:54         ` Richard Zhao
2009-10-01 16:37           ` Wolfram Sang
2009-10-02  0:57             ` Richard Zhao
2009-10-02  7:26               ` Sascha Hauer
2009-10-02  8:17                 ` Richard Zhao
2009-10-02 14:11                   ` Wolfram Sang
2009-10-04 12:22                     ` Richard Zhao

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=1254359613-21210-2-git-send-email-linuxzsc@gmail.com \
    --to=linuxzsc@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).