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
119 set of operations (mainly ioctls). The primary node is always created
133 is, no modesetting or privileged ioctls can be issued on render nodes.
141 per device. No ioctls except PRIME-related ioctls will be allowed on
146 driver-dependent render-only ioctls as DRM_RENDER_ALLOW so render
148 privileged ioctls on render nodes.
158 Besides dropping all modeset/global ioctls, render nodes also drop the
192 disappearance from the device removed uevent, ioctls returning ENODEV
193 (or driver-specific ioctls returning driver-specific things), or open()
216   TEST_ONLY, and any other ioctls either fail with ENODEV or fake
220   is expecting. This applies also to ioctls that faked success.
240   driver-specific ioctls and handling those in userspace drivers, or
283    :doc: driver specific ioctls
440 The DRM core exposes two vertical blank related ioctls: