[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+55aFyw4oOY4oVs=uTD98XPC2WuWhgYYStH+R5P2y=wV8mONg@mail.gmail.com>
Date: Tue, 21 Apr 2015 09:16:47 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Chris Wilson <chris@...is-wilson.co.uk>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel.vetter@...el.com>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Ville Syrjälä <ville.syrjala@...ux.intel.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Olof Johansson <olof@...om.net>,
Nick Dyer <nick.dyer@...ev.co.uk>,
intel-gfx <intel-gfx@...ts.freedesktop.org>,
DRI <dri-devel@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/i915: cope with large i2c transfers
On Tue, Apr 21, 2015 at 12:24 AM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>
> Though I am tempted to say we should impose the 256 byte limit for
> stable@
If the docs say 256, I'd suggest using that not just for stable, but
for anything. Maybe 511 bytes work everywhere and the docs are just
wrong. And maybe it doesn't. I'd rather start out conservative, and if
somebody can show that it really matters, and that 511 bytes really is
always safe, we can do it then. But I don't imagine that the
difference between "chunk it up to max 511 bytes" is really noticeably
faster than "chunk it up to 256 bytes max".
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists