diff options
| author | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2015-04-21 09:49:11 -0700 |
|---|---|---|
| committer | Jani Nikula <jani.nikula@intel.com> | 2015-04-23 23:48:18 +0300 |
| commit | 9535c4757b881e06fae72a857485ad57c422b8d2 (patch) | |
| tree | 6362a8d89171fba94539c0475d6b2ccb2ea9e7f2 /drivers/powercap | |
| parent | 37ef01ab5d24d1d520dc79f6a98099d451c2a901 (diff) | |
| download | linux-9535c4757b881e06fae72a857485ad57c422b8d2.tar.bz2 | |
drm/i915: cope with large i2c transfers
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 MXT driver on Pixel 1 function properly (it hasn't since commit
9d8dc3e529a19e427fd379118acd132520935c5d "Input: atmel_mxt_ts -
implement T44 message handling" which tries to consume multiple
touchscreen/touchpad reports in a single transaction).
Cc: stable@vger.kernel.org
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'drivers/powercap')
0 files changed, 0 insertions, 0 deletions