public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
To: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c-intel-mid: I2C FIFO buffer size setting and fragmentation
Date: Thu, 27 Jan 2011 10:34:10 +0000	[thread overview]
Message-ID: <20110127103410.4f615557@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20110127004759.GJ15795-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>

On Thu, 27 Jan 2011 00:47:59 +0000
Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org> wrote:

> On Tue, Jan 25, 2011 at 02:28:07PM +0000, Alan Cox wrote:
> > From: Major Lee <major_lee-8+ZHUTgF1KZBDgjK7y7TUQ@public.gmane.org>
> > 
> > The FIFO buffer size is different with different CPU stepping.
> > Define it as 32-byte; it is safe for all CPU stepping.
> > 
> > There is a problem when xfer size is greater then FIFO buffer size.
> > Implement software fragmentation in host bus driver so that the
> > I²C slave device drivers need not to be modified or to know about the
> > limits.
> 
> This is quite a big change, does it need to go into a -rc, or can it
> wait for the next kernel merge window?

I was submitting it for next merge window.

Alan

      parent reply	other threads:[~2011-01-27 10:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 14:28 [PATCH] i2c-intel-mid: I2C FIFO buffer size setting and fragmentation Alan Cox
     [not found] ` <20110125142728.10001.85888.stgit-Z/y2cZnRghHXmaaqVzeoHQ@public.gmane.org>
2011-01-27  0:47   ` Ben Dooks
     [not found]     ` <20110127004759.GJ15795-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2011-01-27 10:34       ` Alan Cox [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=20110127103410.4f615557@lxorguk.ukuu.org.uk \
    --to=alan-qbu/x9rampvanceybjwyrvxrex20p6io@public.gmane.org \
    --cc=ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox