All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Ditto <mditto-Vjf7OWgA3BLqlBn2x/YWAg@public.gmane.org>
To: Laurent Pinchart
	<laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Erratic MPC8248 CPM2 I2C behaviour
Date: Tue, 02 Dec 2008 17:44:51 -0800	[thread overview]
Message-ID: <4935E493.9050402@consentry.com> (raw)
In-Reply-To: <200812021207.06140.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>

Hi, Laurent,

> While the problem seems to be similar to CPM98, I don't understand how it 
> could happen on the first character of the first I2C transfer.

I agree, that is hard to explain given that i2c-cpm keeps the controller
shut off until the very moment of the first transfer.  Can you check that
the bus is really idle (SCL is high) when the timeout happens?  If one of
the slave devices is in a bad state and pulling SCL low, I think the
behavior you see is expected (CPM will wait forever for the bus to be
idle).  The same is probably true if a GPIO pin is mis-configured.

> As explained in my previous mail to Joakim, I spent some more time last Friday 
> investigating the problem, and it seems the baud rate generator configuration 
> plays an important role. The default configuration (60kHz nominal => 65.104kHz 
> using a 25MHz brg clock and a /32 predivider) leads to timeouts, while I 
> haven't been able to reproduce the problem with the i2c-mpc8260.c 
> configuration (100kHz nominal => 104.167kHz using a 25MHz brg clock and a /8 
> predivider).

It would be interesting to try each driver with the other's clock settings.

					-=] Mike [=-

WARNING: multiple messages have this Message-ID (diff)
From: Mike Ditto <mditto@consentry.com>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org
Subject: Re: Erratic MPC8248 CPM2 I2C behaviour
Date: Tue, 02 Dec 2008 17:44:51 -0800	[thread overview]
Message-ID: <4935E493.9050402@consentry.com> (raw)
In-Reply-To: <200812021207.06140.laurentp@cse-semaphore.com>

Hi, Laurent,

> While the problem seems to be similar to CPM98, I don't understand how it 
> could happen on the first character of the first I2C transfer.

I agree, that is hard to explain given that i2c-cpm keeps the controller
shut off until the very moment of the first transfer.  Can you check that
the bus is really idle (SCL is high) when the timeout happens?  If one of
the slave devices is in a bad state and pulling SCL low, I think the
behavior you see is expected (CPM will wait forever for the bus to be
idle).  The same is probably true if a GPIO pin is mis-configured.

> As explained in my previous mail to Joakim, I spent some more time last Friday 
> investigating the problem, and it seems the baud rate generator configuration 
> plays an important role. The default configuration (60kHz nominal => 65.104kHz 
> using a 25MHz brg clock and a /32 predivider) leads to timeouts, while I 
> haven't been able to reproduce the problem with the i2c-mpc8260.c 
> configuration (100kHz nominal => 104.167kHz using a 25MHz brg clock and a /8 
> predivider).

It would be interesting to try each driver with the other's clock settings.

					-=] Mike [=-

  parent reply	other threads:[~2008-12-03  1:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.569.1227903153.29923.linuxppc-dev@ozlabs.org>
     [not found] ` <mailman.569.1227903153.29923.linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
2008-12-01 23:28   ` Erratic MPC8248 CPM2 I2C behaviour Mike Ditto
2008-12-01 23:28     ` Mike Ditto
2008-12-02  8:39     ` Joakim Tjernlund
2008-12-02  8:39       ` Joakim Tjernlund
     [not found]       ` <1228207199.9867.69.camel-/EMGr9iCeazgSi9v3i4K4Pmbkio/vSLMs0AfqQuZ5sE@public.gmane.org>
2008-12-02 10:50         ` Laurent Pinchart
2008-12-02 10:50           ` Laurent Pinchart
     [not found]           ` <200812021150.26233.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
2008-12-02 11:45             ` Joakim Tjernlund
2008-12-02 11:45               ` Joakim Tjernlund
2008-12-03  2:27         ` Mike Ditto
2008-12-03  2:27           ` Mike Ditto
     [not found]     ` <49347317.5080600-Vjf7OWgA3BLqlBn2x/YWAg@public.gmane.org>
2008-12-02 11:07       ` Laurent Pinchart
2008-12-02 11:07         ` Laurent Pinchart
     [not found]         ` <200812021207.06140.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
2008-12-03  1:44           ` Mike Ditto [this message]
2008-12-03  1:44             ` Mike Ditto
2008-12-01 23:30   ` Mike Ditto
2008-12-01 23:30     ` Mike Ditto
2008-12-02  0:51   ` Mike Ditto
2008-12-02  0:51     ` Mike Ditto
2008-12-01  9:52 Laurent Pinchart
  -- strict thread matches above, loose matches on Subject: below --
2008-11-28 16:24 Laurent Pinchart
2008-11-29  5:41 ` Wolfram Sang
     [not found]   ` <20081129054153.GA22692-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-12-01  9:56     ` Laurent Pinchart
2008-12-01  9:56       ` Laurent Pinchart
     [not found] ` <200811281724.49620.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
2008-12-04 15:37   ` Jochen Friedrich
2008-12-04 15:37     ` Jochen Friedrich

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=4935E493.9050402@consentry.com \
    --to=mditto-vjf7owga3blqlbn2x/ywag@public.gmane.org \
    --cc=laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.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.