Dmitry Osipenko 0f563a4bf6 gpu: host1x: Forbid unrelated SETCLASS opcode in the firewall ... Several channels could be made to write the same unit concurrently via the SETCLASS opcode, trusting userspace is a bad idea. It should be possible to drop the per-client channel reservation and add a per-unit locking by inserting MLOCK's to the command stream to re-allow the SETCLASS opcode, but it will be much more work. Let's forbid the unit-unrelated class changes for now. Signed-off-by: Dmitry Osipenko <digetx@gmail.com> Reviewed-by: Erik Faye-Lund <kusmabite@gmail.com> Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com> Signed-off-by: Thierry Reding <treding@nvidia.com>		2017-06-15 14:23:50 +02:00
..
drm	gpu: host1x: Forbid unrelated SETCLASS opcode in the firewall	2017-06-15 14:23:50 +02:00
host1x	gpu: host1x: Forbid unrelated SETCLASS opcode in the firewall	2017-06-15 14:23:50 +02:00
ipu-v3	gpu: ipu-v3: don't depend on DRM being enabled	2017-04-04 10:58:56 +02:00
vga	Pointer for Markus's image conversion work.	2017-03-14 15:07:33 +01:00
Makefile