On Fri, Aug 18, 2017 at 07:43:28PM +0200, Daniel Vetter wrote:
> We're not super-consistent about these, but I think it's worth to
> document at least the commmon patterns.
>
> v2:
> - Add a not about ENOTTY (it's just a confusing name, but used
> exactly what it's meant for in DRM) (Chris).
> - U
We're not super-consistent about these, but I think it's worth to
document at least the commmon patterns.
v2:
- Add a not about ENOTTY (it's just a confusing name, but used
exactly what it's meant for in DRM) (Chris).
- Unconfuse the text for ENODEV (Daniel)
- Move text undert the IOCTL heading (C
Hi,
On 18 August 2017 at 10:21, Daniel Vetter wrote:
> +Recommended IOCTL Return Values
> +===
> +
> +In theory a driver's IOCTL callback is only allowed to return very few error
> +codes. In practice it's good to abuse a few more. This section documents
> common
> +p
Quoting Daniel Vetter (2017-08-18 10:21:24)
> We're not super-consistent about these, but I think it's worth to
> document at least the commmon patterns.
>
> Cc: Joonas Lahtinen
> Cc: Chris Wilson
> Cc: "Zhang, Tina"
> Signed-off-by: Daniel Vetter
One extra used outside of i915 is ENOSYS. Per
We're not super-consistent about these, but I think it's worth to
document at least the commmon patterns.
Cc: Joonas Lahtinen
Cc: Chris Wilson
Cc: "Zhang, Tina"
Signed-off-by: Daniel Vetter
---
Documentation/gpu/drm-uapi.rst | 53 ++
1 file changed, 53
