From: Craig Matsuura <cmatsuura-/SMLdF/PHsZWk0Htik3J/w@public.gmane.org>
To: Philby John <pjohn-k0rHJ+Hhz/SB+jHODAdFcQ@public.gmane.org>
Cc: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH/RFC 1/1] recover from davinci i2c time out conditions
Date: Mon, 21 Sep 2009 07:41:21 -0600 [thread overview]
Message-ID: <200909210741.22154.cmatsuura@control4.com> (raw)
In-Reply-To: <1253514660.4507.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 3800 bytes --]
Philby,
Sorry, I forgot to mention, I did correct a problem with accessing a regs, it
is where yo usend a NACK. I changed the read from DAVINCI_I2C_IMR_REG to
DAVINCI_I2C_MDR_REG.
+ flag = davinci_i2c_read_reg(dev, DAVINCI_I2C_IMR_REG);
+ flag |= DAVINCI_I2C_MDR_NACK;
+ /* write the data into mode register */
+ davinci_i2c_write_reg(dev, DAVINCI_I2C_MDR_REG, flag);
Craig
On Monday 21 September 2009 12:31:00 am Philby John wrote:
> Hello Craig,
>
> Good to know. With out any modifications on a DM6443?
>
> Regards,
> Philby
>
> On Fri, 2009-09-18 at 23:12 -0600, Craig Matsuura wrote:
> > The patch submitted appears specific to the dm355. The changes are
> > very similar to the 2.6.10 kernel from mv. If the correct gpio's and
> > pinmux are disabled/enabled it should work for the dm644x.
> >
> >
> >
> > I took the patch from Philby and tried it on our dm6443 platform (on a
> > 2.6.28 kernel) and it appears to work for the problem we have when the
> > i2c appears to lock up.
> >
> >
> >
> > Craig
> >
> > On Wednesday 22 July 2009 5:14:35 am Philby John wrote:
> > > On Wed, 2009-07-22 at 04:03 -0700, Nitin Mahajan wrote:
> > > > Hello,
> > > >
> > > > ----- Original Message ----
> > > >
> > > > > From: Philby John <pjohn-k0rHJ+Hhz/SB+jHODAdFcQ@public.gmane.org>
> > > > > To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> > > > > Cc: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org;
> >
> > davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org
> >
> > > > > Sent: Wednesday, July 15, 2009 13:04:27
> > > > > Subject: [PATCH/RFC 1/1] recover from davinci i2c time out
> >
> > conditions
> >
> > > > > >From dbe7e824d576636bb15b82a20fd2557fddc9a8f7 Mon Sep 17
> >
> > 00:00:00 2001
> >
> > > > > From: Philby John
> > > > > Date: Tue, 14 Jul 2009 21:46:47 +0530
> > > > > Subject: [PATCH] Reset i2c bus to come out of time out
> >
> > conditions
> >
> > > > > Get out of i2c time out condition by resetting
> > > > > the i2c bus. The kernel must be robust enough to
> > > > > gracefully recover from i2c bus failure without having
> > > > > to reset the machine. This is done by first NACKing the slave
> > > > > and then resetting the i2c bus after a certain timeout.
> > > > >
> > > > > Signed-off-by: Philby John
> > > >
> > > > I tried this on DM6443 based board with 2.6.18 kernel. The result
> >
> > I am
> >
> > > > posting below. It gives controller time out again and again.
> > > >
> > > > dhcppc9 login: i2c_davinci i2c_davinci.1: controller timed out
> > > > i2c_davinci i2c_davinci.1: initiating i2c bus recovery
> > > > i2c_davinci i2c_davinci.1: controller timed out
> > > > i2c_davinci i2c_davinci.1: initiating i2c bus recovery
> > >
> > > There is something gravely wrong about this patch and I would submit
> >
> > a
> >
> > > fix shortly incorporating the review comments. But please be aware
> >
> > that
> >
> > > I do not guarantee a definitive time line for a fix cause I have
> >
> > much at
> >
> > > hand at the moment.
> > >
> > >
> > > Regards,
> > > Philby
> > >
> > >
> > > _______________________________________________
> > > Davinci-linux-open-source mailing list
> > > Davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org
> >
> > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
> >
> > --
> >
> >
> >
> >
> >
> > ______________________________________________________________________
> >
> >
> > Craig Matsuura - Principal Engineer
> > Control4
> > 11734 South Election Road - Suite 200
> > Salt Lake City, UT 84020-6432
> > PH: 801-523-3161
> > FX: 801-523-3199
--
Craig Matsuura - Principal Engineer
Control4
11734 South Election Road - Suite 200
Salt Lake City, UT 84020-6432
PH: 801-523-3161
FX: 801-523-3199
[-- Attachment #1.2: Type: text/html, Size: 6740 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2009-09-21 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 7:34 [PATCH/RFC 1/1] recover from davinci i2c time out conditions Philby John
[not found] ` <1247643267.5981.82.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-07-15 12:34 ` Sergei Shtylyov
[not found] ` <4A5DCCBD.909-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2009-11-23 15:23 ` Philby John
2009-07-15 17:10 ` David Brownell
[not found] ` <200907151010.18709.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-11-23 15:23 ` Philby John
2009-07-15 17:15 ` Troy Kisky
[not found] ` <4A5E0E98.2030108-Q5RJGjKts06CY9SHAMCTRUEOCMrvLtNR@public.gmane.org>
2009-07-24 14:34 ` Karicheri, Muralidharan
[not found] ` <A69FA2915331DC488A831521EAE36FE40144FDB54B-UmuGNrFEPrGIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-07-24 18:14 ` Troy Kisky
2009-11-23 15:24 ` Philby John
2009-07-22 11:03 ` Nitin Mahajan
[not found] ` <218571.29671.qm-LK+a5U5w+t2B9c0Qi4KiSl5cfvJIxWXgQQ4Iyu8u01E@public.gmane.org>
2009-07-22 11:14 ` Philby John
[not found] ` <1248261275.4077.4.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-09-19 5:12 ` Craig Matsuura
[not found] ` <200909182312.58018.cmatsuura-/SMLdF/PHsZWk0Htik3J/w@public.gmane.org>
2009-09-21 6:31 ` Philby John
[not found] ` <1253514660.4507.2.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-09-21 13:34 ` Craig Matsuura
2009-09-21 13:41 ` Craig Matsuura [this message]
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=200909210741.22154.cmatsuura@control4.com \
--to=cmatsuura-/smldf/phszwk0htik3j/w@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pjohn-k0rHJ+Hhz/SB+jHODAdFcQ@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.