public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	i2c@lm-sensors.org, linux-sh@vger.kernel.org,
	ben-linux@fluff.org
Subject: Re: [PATCH] i2c: fix i2c-sh_mobile timing issues
Date: Wed, 27 Aug 2008 17:46:28 +0200	[thread overview]
Message-ID: <20080827174628.3b452f2d@hyperion.delvare> (raw)
In-Reply-To: <20080827144048.GA32530@linux-sh.org>

On Wed, 27 Aug 2008 23:40:48 +0900, Paul Mundt wrote:
> On Wed, Aug 27, 2008 at 06:33:56PM +0900, Magnus Damm wrote:
> > From: Magnus Damm <damm@igel.co.jp>
> > 
> > This patch teaches the i2c-sh_mobile driver to make use of wait irqs.
> > Without this patch only dte irqs are used which may lead to overruns
> > and cases of missing stop and extra bytes being read on the i2c bus.
> > 
> > Use of wait irqs forces the hardware to pause and wait until the cpu
> > is ready. Polling is also reworked in this patch to fix ms delay issues.
> > 
> > Verified with bus analyzer and tested on MigoR and AP325RXA boards.
> > 
> > Signed-off-by: Magnus Damm <damm@igel.co.jp>
> > ---
> > 
> >  Paul, can you merge this for 2.6.27?
> > 
> >  drivers/i2c/busses/i2c-sh_mobile.c |  271 +++++++++++++++++++++++++++---------
> >  1 file changed, 208 insertions(+), 63 deletions(-)
> > 
> I'll add it to my queue if Jean and Ben don't have any issues with the
> patch. If the polling works as is, I would suggest that it is not 2.6.27
> material, but if it's fixing operational bugs then it doesn't make sense
> to leave 2.6.27 in a known broken state.

No objection from me, as this is outside of my jurisdiction.

-- 
Jean Delvare

  reply	other threads:[~2008-08-27 15:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  9:33 [PATCH] i2c: fix i2c-sh_mobile timing issues Magnus Damm
2008-08-27 11:09 ` Jean Delvare
2008-08-28 11:57   ` Magnus Damm
2008-08-27 14:40 ` Paul Mundt
2008-08-27 15:46   ` Jean Delvare [this message]
2008-09-05  5:36     ` Paul Mundt

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=20080827174628.3b452f2d@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=ben-linux@fluff.org \
    --cc=i2c@lm-sensors.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox