Lines Matching refs:ioctls
10 drivers & device-aware applications through ioctls and sysfs files.
16 Cover generic ioctls and sysfs layout here. We only need high-level
128 set of operations (mainly ioctls). The primary node is always created
142 is, no modesetting or privileged ioctls can be issued on render nodes.
150 per device. No ioctls except PRIME-related ioctls will be allowed on
152 complete list of driver-independent ioctls that can be used on render
153 nodes, see the ioctls marked DRM_RENDER_ALLOW in drm_ioctl.c Render
157 driver-dependent render-only ioctls as DRM_RENDER_ALLOW so render
159 privileged ioctls on render nodes.
169 Besides dropping all modeset/global ioctls, render nodes also drop the
203 disappearance from the device removed uevent, ioctls returning ENODEV
204 (or driver-specific ioctls returning driver-specific things), or open()
227 TEST_ONLY, and any other ioctls either fail with ENODEV or fake
231 is expecting. This applies also to ioctls that faked success.
251 driver-specific ioctls and handling those in userspace drivers, or
294 :doc: driver specific ioctls
451 The DRM core exposes two vertical blank related ioctls: