From: Manu Abraham <manu@kromtek.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com, js@linuxtv.org,
kraxel@bytesex.org
Subject: [PATCH] Re: [PATCH] Fix dst i2c read/write timeout failure.
Date: Thu, 05 May 2005 01:27:34 +0400 [thread overview]
Message-ID: <42793E46.3070007@kromtek.com> (raw)
In-Reply-To: <20050504135735.713e99ba.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
Andrew Morton wrote:
> Manu Abraham <manu@kromtek.com> wrote:
>
>>User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
>>
>
>
> uh-oh.
>
>
>>Attached is a patch to bttv which fixes the following problems.
>
>
> Mozilla space-stuffed it. Please resend as an attachment.
>
>
>
Oh, i am sorry, resending it ..
Attached is a patch to bttv which fixes the following problems.
Affected cards and problems:
~~~~~~~~~~~~~~~~~~~~~~~~
o VP-1020 (200103A) Tuning problems, device detection.
o VP-1020 (DST-MOT) Errors during tuning, device detection fails in a while.
o VP-1030 (DST-CI) Tuning sometimes fails after CI commands.
o VP-2031 (DCT-CI) Tuning problems
The timeout happens before the actual timeout occured in the MCU
on the board, and hence the problems.
Changes: (bttv-i2c.diff)
~~~~~~~~~~~~~~~~~~~~~~~~
o Changed the custom wait queue to wait_event_interruptible_timeout()
- Suggestion by Johannes Stezenbach.
o Fixed the wait queue timeout problem
- This fixes the timeout problem on various cards.
- This problem was visible as many
* Cannot tune to channels, when signal levels are very low.
* app_info does not work in some conditions for CI based cards
- Smaller values worked good for newer cards, but the older cards
suffered, settled down to the worst case values that could happen in any
eventuality.
Signed-off-by: Manu Abraham <manu@kromtek.com>
[-- Attachment #2: bttv-i2c.diff --]
[-- Type: text/x-patch, Size: 939 bytes --]
--- linux-2.6.12-rc3.orig/drivers/media/video/bttv-i2c.c 2005-05-03 16:04:28.000000000 +0400
+++ linux-2.6.12-rc3/drivers/media/video/bttv-i2c.c 2005-05-05 00:01:00.000000000 +0400
@@ -29,6 +29,7 @@
#include <linux/moduleparam.h>
#include <linux/init.h>
#include <linux/delay.h>
+#include <linux/jiffies.h>
#include <asm/io.h>
#include "bttvp.h"
@@ -130,17 +131,14 @@ static u32 functionality(struct i2c_adap
static int
bttv_i2c_wait_done(struct bttv *btv)
{
- DECLARE_WAITQUEUE(wait, current);
int rc = 0;
- add_wait_queue(&btv->i2c_queue, &wait);
- if (0 == btv->i2c_done)
- msleep_interruptible(20);
- remove_wait_queue(&btv->i2c_queue, &wait);
-
- if (0 == btv->i2c_done)
- /* timeout */
- rc = -EIO;
+ /* timeout */
+ if (wait_event_interruptible_timeout(btv->i2c_queue,
+ btv->i2c_done, msecs_to_jiffies(85)) == -ERESTARTSYS)
+
+ rc = -EIO;
+
if (btv->i2c_done & BT848_INT_RACK)
rc = 1;
btv->i2c_done = 0;
next prev parent reply other threads:[~2005-05-04 21:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 20:44 [PATCH] Fix dst i2c read/write timeout failure Manu Abraham
2005-05-04 20:57 ` Andrew Morton
2005-05-04 21:27 ` Manu Abraham [this message]
2005-05-04 22:20 ` [PATCH] " Randy.Dunlap
2005-05-05 15:00 ` Manu Abraham
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=42793E46.3070007@kromtek.com \
--to=manu@kromtek.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=js@linuxtv.org \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@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 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.