From: Jean Delvare <khali@linux-fr.org>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH 2/2] sfc: Reduce I2C udelay to 5 resulting in a clock frequency of 100 kHz
Date: Sat, 31 May 2008 13:19:43 +0200 [thread overview]
Message-ID: <20080531131943.46ba0332@hyperion.delvare> (raw)
In-Reply-To: <20080530212745.GH1743@solarflare.com>
On Fri, 30 May 2008 22:27:46 +0100, Ben Hutchings wrote:
>
> Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
> ---
> drivers/net/sfc/falcon.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/sfc/falcon.c b/drivers/net/sfc/falcon.c
> index 8acd53d..8cb5798 100644
> --- a/drivers/net/sfc/falcon.c
> +++ b/drivers/net/sfc/falcon.c
> @@ -222,7 +222,7 @@ static struct i2c_algo_bit_data falcon_i2c_bit_operations = {
> .setscl = falcon_setscl,
> .getsda = falcon_getsda,
> .getscl = falcon_getscl,
> - .udelay = 100,
> + .udelay = 5,
> /*
> * This is the number of system clock ticks after which
> * i2c-algo-bit gives up waiting for SCL to become high.
Acked-by: Jean Delvare <khali@linux-fr.org>
--
Jean Delvare
prev parent reply other threads:[~2008-05-31 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1212182201.git.bhutchings@solarflare.com>
2008-05-30 21:27 ` [PATCH 1/2] sfc: Use kernel I2C system and i2c-algo-bit driver Ben Hutchings
2008-05-31 2:19 ` Jeff Garzik
2008-05-31 11:18 ` Jean Delvare
2008-05-31 11:27 ` Ben Hutchings
2008-05-31 15:07 ` Jean Delvare
2008-05-30 21:27 ` [PATCH 2/2] sfc: Reduce I2C udelay to 5 resulting in a clock frequency of 100 kHz Ben Hutchings
2008-05-31 11:19 ` Jean Delvare [this message]
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=20080531131943.46ba0332@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=bhutchings@solarflare.com \
--cc=jgarzik@pobox.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.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).