From: Mike Ditto <mditto-Vjf7OWgA3BLqlBn2x/YWAg@public.gmane.org>
To: joakim.tjernlund-SNLAxHN9vbcOP4wsBPIw7w@public.gmane.org
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
Laurent Pinchart
<laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Erratic MPC8248 CPM2 I2C behaviour
Date: Tue, 02 Dec 2008 18:27:23 -0800 [thread overview]
Message-ID: <4935EE8B.80708@consentry.com> (raw)
In-Reply-To: <1228207199.9867.69.camel-/EMGr9iCeazgSi9v3i4K4Pmbkio/vSLMs0AfqQuZ5sE@public.gmane.org>
Jocke,
> The I2C_CHIP_ERRATA is mine and refers to mpc8xx, mpc860 in my case. The
> driver was adapted by me some years ago in 2.4 and now someone has
> ported it to 2.6 it seems.
Thanks for the background info. Any idea which particular errata it
was meant to fix? I took a quick look at MPC860 errata document and it
seems that CPM5 and CPM6 both suggest this workaround.
I don't think any of the 8xx CPM errata are present on 82xx, but it
would be good to enable the same or similar workaround on CPM2 for
82xx erratum CPM98, probably even when I2C_CHIP_ERRATA is not defined.
-=] Mike [=-
WARNING: multiple messages have this Message-ID (diff)
From: Mike Ditto <mditto@consentry.com>
To: joakim.tjernlund@transmode.se
Cc: linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org
Subject: Re: Erratic MPC8248 CPM2 I2C behaviour
Date: Tue, 02 Dec 2008 18:27:23 -0800 [thread overview]
Message-ID: <4935EE8B.80708@consentry.com> (raw)
In-Reply-To: <1228207199.9867.69.camel@gentoo-jocke.transmode.se>
Jocke,
> The I2C_CHIP_ERRATA is mine and refers to mpc8xx, mpc860 in my case. The
> driver was adapted by me some years ago in 2.4 and now someone has
> ported it to 2.6 it seems.
Thanks for the background info. Any idea which particular errata it
was meant to fix? I took a quick look at MPC860 errata document and it
seems that CPM5 and CPM6 both suggest this workaround.
I don't think any of the 8xx CPM errata are present on 82xx, but it
would be good to enable the same or similar workaround on CPM2 for
82xx erratum CPM98, probably even when I2C_CHIP_ERRATA is not defined.
-=] Mike [=-
next prev parent reply other threads:[~2008-12-03 2:27 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 [this message]
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
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=4935EE8B.80708@consentry.com \
--to=mditto-vjf7owga3blqlbn2x/ywag@public.gmane.org \
--cc=joakim.tjernlund-SNLAxHN9vbcOP4wsBPIw7w@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.