Re: [Intel-gfx] [PATCH v2] drm/i915: cope with large i2c transfers

2015-04-23 Thread Jani Nikula
On Thu, 23 Apr 2015, Daniel Vetter wrote: > On Tue, Apr 21, 2015 at 10:12:19AM -0700, Linus Torvalds wrote: >> On Tue, Apr 21, 2015 at 9:49 AM, Dmitry Torokhov >> wrote: >> > The hardware, according to the specs, is limited to 256 byte transfers, >> > and current driver has no protections in case

Re: [Intel-gfx] [PATCH v2] drm/i915: cope with large i2c transfers

2015-04-23 Thread Daniel Vetter
On Tue, Apr 21, 2015 at 10:12:19AM -0700, Linus Torvalds wrote: > On Tue, Apr 21, 2015 at 9:49 AM, Dmitry Torokhov > wrote: > > The hardware, according to the specs, is limited to 256 byte transfers, > > and current driver has no protections in case users attempt to do larger > > transfers. The co

Re: [Intel-gfx] [PATCH v2] drm/i915: cope with large i2c transfers

2015-04-21 Thread Linus Torvalds
On Tue, Apr 21, 2015 at 9:49 AM, Dmitry Torokhov wrote: > The hardware, according to the specs, is limited to 256 byte transfers, > and current driver has no protections in case users attempt to do larger > transfers. The code will just stomp over status register and mayhem > ensues. Thanks, look

[Intel-gfx] [PATCH v2] drm/i915: cope with large i2c transfers

2015-04-21 Thread Dmitry Torokhov
The hardware, according to the specs, is limited to 256 byte transfers, and current driver has no protections in case users attempt to do larger transfers. The code will just stomp over status register and mayhem ensues. Let's split larger transfers into digestable chunks. Doing this allows Atmel