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)
70 lines
1.3 KiB
ReStructuredText
70 lines
1.3 KiB
ReStructuredText
.. -*- coding: utf-8; mode: rst -*-
|
|
|
|
.. _media-func-open:
|
|
|
|
************
|
|
media open()
|
|
************
|
|
|
|
Name
|
|
====
|
|
|
|
media-open - Open a media device
|
|
|
|
|
|
Synopsis
|
|
========
|
|
|
|
.. code-block:: c
|
|
|
|
#include <fcntl.h>
|
|
|
|
|
|
.. c:function:: int open( const char *device_name, int flags )
|
|
:name: mc-open
|
|
|
|
Arguments
|
|
=========
|
|
|
|
``device_name``
|
|
Device to be opened.
|
|
|
|
``flags``
|
|
Open flags. Access mode must be either ``O_RDONLY`` or ``O_RDWR``.
|
|
Other flags have no effect.
|
|
|
|
|
|
Description
|
|
===========
|
|
|
|
To open a media device applications call :ref:`open() <media-func-open>` with the
|
|
desired device name. The function has no side effects; the device
|
|
configuration remain unchanged.
|
|
|
|
When the device is opened in read-only mode, attempts to modify its
|
|
configuration will result in an error, and ``errno`` will be set to
|
|
EBADF.
|
|
|
|
|
|
Return Value
|
|
============
|
|
|
|
:ref:`open() <func-open>` returns the new file descriptor on success. On error,
|
|
-1 is returned, and ``errno`` is set appropriately. Possible error codes
|
|
are:
|
|
|
|
EACCES
|
|
The requested access to the file is not allowed.
|
|
|
|
EMFILE
|
|
The process already has the maximum number of files open.
|
|
|
|
ENFILE
|
|
The system limit on the total number of open files has been reached.
|
|
|
|
ENOMEM
|
|
Insufficient kernel memory was available.
|
|
|
|
ENXIO
|
|
No device corresponding to this device special file exists.
|