From: Andy Walls <awalls@md.metrocast.net>
To: Jean Delvare <khali@linux-fr.org>
Cc: Jarod Wilson <jarod@wilsonet.com>,
linux-media@vger.kernel.org, Mike Isely <isely@isely.net>,
Janne Grunau <j@jannau.net>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [GIT PATCHES for 2.6.38] Zilog Z8 IR unit fixes
Date: Wed, 19 Jan 2011 08:24:14 -0500 [thread overview]
Message-ID: <1295443454.4317.6.camel@morgan.silverblock.net> (raw)
In-Reply-To: <20110119134009.1d473320@endymion.delvare>
On Wed, 2011-01-19 at 13:40 +0100, Jean Delvare wrote:
> On Wed, 19 Jan 2011 07:21:58 -0500, Andy Walls wrote:
> > For debugging, you might want to hack in a probe of address 0x70 for
> > your HVR-1950, to ensure the Tx side responds in the bridge driver.
>
> ... keeping in mind that the Z8 doesn't seem to like quick writes, so
> short reads should be used for probing purpose.
>
Noted. Thanks.
Actually, I think that might be due to the controller in the USB
connected devices (hdpvr and pvrusb2). The PCI connected devices, like
cx18 cards, don't have a problem with the Z8, the default I2C probe
method, and i2c-algo-bit.
(A good example of why only bridge drivers should do any required
probing.)
Looking at the code in pvrusb2, it appears to already use a 0 length
read for a probe:
http://git.linuxtv.org/media_tree.git?a=blob;f=drivers/media/video/pvrusb2/pvrusb2-i2c-core.c;h=ccc884948f34b385563ccbf548c5f80b33cd4f08;hb=refs/heads/staging/for_2.6.38-rc1#l542
Regards,
Andy
next prev parent reply other threads:[~2011-01-19 13:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 19:20 [GIT PATCHES for 2.6.38] Zilog Z8 IR unit fixes Andy Walls
2011-01-17 3:29 ` Andy Walls
2011-01-19 5:20 ` Jarod Wilson
2011-01-19 12:21 ` Andy Walls
2011-01-19 12:40 ` Jean Delvare
2011-01-19 13:24 ` Andy Walls [this message]
2011-01-19 13:28 ` Mike Isely
2011-01-19 13:20 ` Mike Isely
2011-01-19 13:38 ` Andy Walls
2011-01-19 13:50 ` Jean Delvare
2011-01-19 17:12 ` Jarod Wilson
2011-01-19 17:39 ` Jarod Wilson
2011-01-19 17:43 ` Jean Delvare
2011-01-19 20:08 ` Jarod Wilson
2011-01-20 4:45 ` Jarod Wilson
2011-01-20 4:52 ` Jarod Wilson
2011-01-20 13:22 ` Andy Walls
2011-01-20 21:49 ` Jarod Wilson
2011-01-21 1:10 ` Andy Walls
2011-01-21 3:58 ` Jarod Wilson
2011-01-19 14:17 ` Mike Isely
2011-01-19 16:42 ` Jarod Wilson
2011-01-19 16:57 ` Mike Isely
2011-01-19 17:07 ` Jarod Wilson
2011-01-19 16:08 ` Jarod Wilson
2011-01-19 16:10 ` Devin Heitmueller
2011-01-19 14:59 ` Jean Delvare
2011-01-19 15:09 ` Mike Isely
2011-01-19 15:18 ` Jean Delvare
-- strict thread matches above, loose matches on Subject: below --
2011-01-19 16:46 Andy Walls
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=1295443454.4317.6.camel@morgan.silverblock.net \
--to=awalls@md.metrocast.net \
--cc=isely@isely.net \
--cc=j@jannau.net \
--cc=jarod@wilsonet.com \
--cc=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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.