All of lore.kernel.org
 help / color / mirror / Atom feed
From: Devin Heitmueller <dheitmueller@kernellabs.com>
To: Andy Walls <awalls@md.metrocast.net>
Cc: Mark Zimmerman <markzimm@frii.com>, linux-media@vger.kernel.org
Subject: Re: [corrected get-bisect results]: DViCO FusionHDTV7 Dual Express I2C write failed
Date: Mon, 14 Feb 2011 09:29:06 -0500	[thread overview]
Message-ID: <AANLkTi=Ke-FFvBAxriTkkt0wJADH5jCj9oafPCNCd8a0@mail.gmail.com> (raw)
In-Reply-To: <1297642614.19186.38.camel@localhost>

On Sun, Feb 13, 2011 at 7:16 PM, Andy Walls <awalls@md.metrocast.net> wrote:
> Devin,
>
> I just checked.  The CX23885 driver *is* setting up to allow slaves to
> stretch the clock.
>
> By analysis, I have confirmed that Jean's sugguested patch that I moved
> forward was wrong for the hardware's behavior.  When the cx23885 I2C
> routines decide to set the I2C_EXTEND flag (and maybe the I2C_NOSTOP
> flag), we most certainly should *not* be expecting an ACK from the
> particular hardware register.  The original commit should certainly be
> reverted.
>
> Checking for slave ACK/NAK will need to be done with a little more care;
> so for now, I'll settle for ignoring them.

Ok, that makes sense.  I just threw out the possibility of it being
related to clock stretch because I've seen that with other bridges and
the xc5000.  I haven't really reviewed the code in question or the
cx23885 datasheet.

Cheers,

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

  reply	other threads:[~2011-02-14 14:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101207190753.GA21666@io.frii.com>
2011-01-10  2:14 ` DViCO FusionHDTV7 Dual Express I2C write failed Mark Zimmerman
2011-01-19 15:59   ` VDR User
2011-01-19 16:13     ` Devin Heitmueller
2011-01-19 17:22       ` VDR User
2011-01-19 17:39         ` Mark Zimmerman
2011-01-24 15:49           ` Mark Zimmerman
2011-01-24 15:57             ` Devin Heitmueller
2011-01-25 14:27               ` Mark Zimmerman
2011-01-19 19:01       ` Timothy D. Lenz
2011-01-17 23:12 ` Timothy D. Lenz
2011-02-12 15:29 ` [get-bisect results]: " Mark Zimmerman
2011-02-12 16:27   ` Andy Walls
2011-02-12 16:36     ` Mark Zimmerman
2011-02-12 16:46       ` Andy Walls
2011-02-12 17:03         ` Mark Zimmerman
2011-02-12 19:05         ` Mark Zimmerman
2011-02-12 20:48           ` Andy Walls
2011-02-13 14:47   ` [corrected get-bisect " Mark Zimmerman
2011-02-13 14:52     ` Devin Heitmueller
2011-02-13 20:26       ` Mark Zimmerman
2011-02-13 21:26         ` Andy Walls
2011-02-14  0:16           ` Andy Walls
2011-02-14 14:29             ` Devin Heitmueller [this message]
2011-02-14  0:37           ` Mark Zimmerman
2011-02-14  8:05     ` 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='AANLkTi=Ke-FFvBAxriTkkt0wJADH5jCj9oafPCNCd8a0@mail.gmail.com' \
    --to=dheitmueller@kernellabs.com \
    --cc=awalls@md.metrocast.net \
    --cc=linux-media@vger.kernel.org \
    --cc=markzimm@frii.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.