public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <walle@corscience.de>
To: Jean Delvare <khali@linux-fr.org>
Cc: ben-linux@fluff.org, ddaney@caviumnetworks.com,
	ralf@linux-mips.org, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: octeon: Make the timeout 1*HZ instead of 1 jiffy
Date: Mon, 24 Jan 2011 13:37:36 +0100	[thread overview]
Message-ID: <4D3D7290.9050203@corscience.de> (raw)
In-Reply-To: <20110124131405.4583a7af@endymion.delvare>

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

Hi Jean,

Am 24.01.2011 13:14, schrieb Jean Delvare:
>>  	.owner = THIS_MODULE,
>>  	.name = "OCTEON adapter",
>>  	.algo = &octeon_i2c_algo,
>> -	.timeout = 2,
>> +	.timeout = HZ,
>>  };
> 
> This is a large timeout value, much larger than any value the
> i2c-octeon driver was using today for any possible value of HZ.
> Wouldn't it make more sense to set it to HZ / 50, which is 2 for HZ =
> 100, leaving the setting unchanged for this common case at least?

To be honest, I had problems with timeout=2 that go away with
timeout=HZ. But I cannot be sure that this is a problem with my hardware
that is not present with other devices.

The drivers that use HZ are i2c-mpc.c and i2c-pca-platform.c, but I
don't know the hardware that much so that I really can compare the values.

So yes, you're right. A patch modifying the timeout value should be an
extra patch, so I will resend the current patch to use HZ/50.


Regards,
Bernhard


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2011-01-24 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 12:05 [PATCH] i2c: octeon: Make the timeout 1*HZ instead of 1 jiffy Bernhard Walle
2011-01-24 12:14 ` Jean Delvare
2011-01-24 12:37   ` Bernhard Walle [this message]
2011-01-24 12:40     ` [PATCH] i2c: octeon: Make the timeout independent of CONFIG_HZ Bernhard Walle
2011-01-24 14:00       ` Jean Delvare
2011-03-16 13:32         ` Jean Delvare

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=4D3D7290.9050203@corscience.de \
    --to=walle@corscience.de \
    --cc=ben-linux@fluff.org \
    --cc=ddaney@caviumnetworks.com \
    --cc=khali@linux-fr.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.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