threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
72 lines
1.3 KiB
ReStructuredText
72 lines
1.3 KiB
ReStructuredText
.. -*- coding: utf-8; mode: rst -*-
|
|
|
|
.. _FE_GET_EVENT:
|
|
|
|
************
|
|
FE_GET_EVENT
|
|
************
|
|
|
|
Name
|
|
====
|
|
|
|
FE_GET_EVENT
|
|
|
|
.. attention:: This ioctl is deprecated.
|
|
|
|
|
|
Synopsis
|
|
========
|
|
|
|
.. c:function:: int ioctl(int fd, FE_GET_EVENT, struct dvb_frontend_event *ev)
|
|
:name: FE_GET_EVENT
|
|
|
|
|
|
Arguments
|
|
=========
|
|
|
|
``fd``
|
|
File descriptor returned by :c:func:`open() <dvb-fe-open>`.
|
|
|
|
``ev``
|
|
Points to the location where the event, if any, is to be stored.
|
|
|
|
|
|
Description
|
|
===========
|
|
|
|
This ioctl call returns a frontend event if available. If an event is
|
|
not available, the behavior depends on whether the device is in blocking
|
|
or non-blocking mode. In the latter case, the call fails immediately
|
|
with errno set to ``EWOULDBLOCK``. In the former case, the call blocks until
|
|
an event becomes available.
|
|
|
|
|
|
Return Value
|
|
============
|
|
|
|
On success 0 is returned.
|
|
|
|
On error -1 is returned, and the ``errno`` variable is set
|
|
appropriately.
|
|
|
|
|
|
.. flat-table::
|
|
:header-rows: 0
|
|
:stub-columns: 0
|
|
|
|
|
|
- .. row 1
|
|
|
|
- ``EWOULDBLOCK``
|
|
|
|
- There is no event pending, and the device is in non-blocking mode.
|
|
|
|
- .. row 2
|
|
|
|
- ``EOVERFLOW``
|
|
|
|
- Overflow in event queue - one or more events were lost.
|
|
|
|
Generic error codes are described at the
|
|
:ref:`Generic Error Codes <gen-errors>` chapter.
|