Home
last modified time | relevance | path

Searched full:open (Results 1 – 25 of 750) sorted by relevance

12345678910>>...30

/Documentation/userspace-api/media/mediactl/
Dmedia-func-open.rst4 .. _media-func-open:
7 media open()
13 media-open - Open a media device
22 .. c:function:: int open( const char *device_name, int flags )
31 Open flags. Access mode must be either ``O_RDONLY`` or ``O_RDWR``.
37 To open a media device applications call :c:func:`open()` with the
48 :c:func:`open()` returns the new file descriptor on success. On error,
56 The process already has the maximum number of files open.
59 The system limit on the total number of open files has been reached.
/Documentation/userspace-api/media/v4l/
Dfunc-open.rst4 .. _func-open:
7 V4L2 open()
13 v4l2-open - Open a V4L2 device
22 .. c:function:: int open( const char *device_name, int flags )
31 Open flags. Access mode must be ``O_RDWR``. This is just a
47 To open a V4L2 device applications call :c:func:`open()` with the
50 remain unchanged. At the first :c:func:`open()` call after loading the
57 On success :c:func:`open()` returns the new file descriptor. On error
75 The process already has the maximum number of files open.
78 The limit on the total number of files open on the system has been
/Documentation/userspace-api/media/cec/
Dcec-func-open.rst4 .. _cec-func-open:
7 cec open()
13 cec-open - Open a cec device
22 .. c:function:: int open( const char *device_name, int flags )
31 Open flags. Access mode must be ``O_RDWR``.
46 To open a cec device applications call :c:func:`open()` with the
57 :c:func:`open()` returns the new file descriptor on success. On error,
65 The process already has the maximum number of files open.
68 The system limit on the total number of open files has been reached.
/Documentation/devicetree/bindings/i2c/
Di2c-gpio.yaml23 active high using open drain with (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)
25 open drain.
31 active high using open drain with (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)
33 open drain.
56 i2c-gpio,sda-open-drain:
60 the GPIO line used for SDA into open drain mode, and that something is
63 i2c-gpio,scl-open-drain:
67 GPIO line used for SCL into open drain mode, and that something is not
73 Therefore disable open-drain. This property is mutually-exclusive
74 with i2c-gpio,sda-open-drain.
[all …]
/Documentation/userspace-api/media/dvb/
Dfrontend_f_open.rst7 Digital TV frontend open()
13 fe-open - Open a frontend device
22 .. c:function:: int open( const char *device_name, int flags )
31 Open flags. Access can either be ``O_RDWR`` or ``O_RDONLY``.
36 Only one open is allowed in ``O_RDWR``. In this mode, all ioctls are
50 thing to do after a successful open is to find out the frontend type
58 multiple devices cannot be open in read/write mode simultaneously. As
59 long as a front-end device is opened in read/write mode, other open()
65 When an open() call has succeeded, the device will be ready for use in
73 On success :c:func:`open()` returns the new file descriptor.
[all …]
Dca-fopen.rst7 Digital TV CA open()
13 Digital TV CA open()
18 .. c:function:: int open(const char *name, int flags)
43 - open in non-blocking mode
52 When an ``open()`` call has succeeded, the device will be ready for use. The
55 affect the semantics of the ``open()`` call itself. A device opened in
59 Only one user can open the CA Device in ``O_RDWR`` mode. All other
60 attempts to open the device in this mode will fail, and an error code
Ddmx-fopen.rst7 Digital TV demux open()
13 Digital TV demux open()
18 .. c:function:: int open(const char *deviceName, int flags)
46 - open in non-blocking mode
65 affect the semantics of the ``open()`` call itself. A device opened
85 - "Too many open files", i.e. no more filters available.
Dlegacy_dvb_audio.rst480 - File descriptor returned by a previous call to `open()`_.
531 - File descriptor returned by a previous call to `open()`_.
583 to `open()`_.
636 to `open()`_.
689 to `open()`_.
751 to `open()`_.
825 to `open()`_.
896 to `open()`_.
970 to `open()`_.
1032 to `open()`_.
[all …]
/Documentation/devicetree/bindings/reserved-memory/
Dgoogle,open-dice.yaml4 $id: http://devicetree.org/schemas/reserved-memory/google,open-dice.yaml#
7 title: Open Profile for DICE
11 generated by the Open Profile for DICE protocol.
13 See https://pigweed.googlesource.com/open-dice/
23 const: google,open-dice
42 compatible = "google,open-dice";
/Documentation/devicetree/bindings/interrupt-controller/
Dopen-pic.txt1 * Open PIC Binding
4 representation of an Open PIC compliant interrupt controller. This binding is
5 based on the binding defined for Open PIC in [1] and is a superset of that
14 shall be <string> and the value shall include "open-pic".
20 as an Open PIC. No property value shall be defined.
55 * An Open PIC interrupt controller
62 // this Open PIC node do not need a parent address specifier.
71 // Compatible with Open PIC.
72 compatible = "open-pic";
81 * An interrupt generating device that is wired to an Open PIC.
/Documentation/driver-api/gpio/
Dintro.rst39 other value (notably, "open drain" signaling).
80 Open Drain and Open Source
82 Sometimes shared signals need to use "open drain" (where only the low signal
83 level is actually driven), or "open source" (where only the high signal level is
84 driven) signaling. That term applies to CMOS transistors; "open collector" is
89 One common example of an open drain signal is a shared active-low IRQ line.
90 Also, bidirectional data bus signals sometimes use open drain signals.
92 Some GPIO controllers directly support open drain and open source outputs; many
93 don't. When you need open drain signaling but your hardware doesn't directly
103 The same logic can be applied to emulate open source signaling, by driving the
[all …]
Ddriver.rst97 - Single-ended modes (open drain/open source)
132 GPIO lines with open drain/source support
135 Open drain (CMOS) or open collector (TTL) means the line is not actively driven
137 is not open, it will present a high-impedance (tristate) to the external rail::
190 either transistor will go totally numb if this switch is open. The totem-pole
192 high or low respectively. That is usually how software-controlled open
195 Some GPIO hardware come in open drain / open source configuration. Some are
196 hard-wired lines that will only support open drain or open source no matter
198 by flipping a bit in a register the output can be configured as open drain
199 or open source, in practice by flicking open the switches labeled "OD" and "OS"
[all …]
Dconsumer.rst33 some open coding of error handling should be expected when you do this.
73 to be electrically used with open drain.
75 to be electrically used with open drain.
81 The two last flags are used for use cases where open drain is mandatory, such
82 as I2C: if the line is not already configured as open drain in the mappings
83 (see board.rst), then open drain will be enforced anyway and a warning will be
226 open-drain signaling and output latencies.
263 The active low and open drain semantics
272 The same is applicable for open drain or open source output lines: those do not
273 actively drive their output high (open drain) or low (open source), they just
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-iio-adc-hi84357 Could be either "GND-Open" or "Supply-Open" mode. Y is a
19 is separately set for "GND-Open" and "Supply-Open" modes.
38 is separately set for "GND-Open" and "Supply-Open" modes.
Dsysfs-bus-iio-thermocouple16 Open-circuit fault. The detection of open-circuit faults,
/Documentation/filesystems/
Ddlmfs.rst83 and write(2) against the fd obtained via your open(2) call. The
94 domain directory. Locking against them is done via the open(2) system
97 The open(2) call will not return until your lock has been granted or
101 open(2) with O_CREAT to ensure the resource inode is created - dlmfs does
105 Open Flag Lock Request Type
113 Open Flag Resulting Locking Behavior
121 could not lock the resource then open(2) will return ETXTBUSY.
125 Modes passed to mkdir(2) or open(2) are adhered to locally. Chown is
131 write(2) only when open in Exclusive mode.
Dinotify.rst18 What is the design decision behind not tying the watch to the open fd of
22 Watches are associated with an open inotify device, not an open file.
23 This solves the primary problem with dnotify: keeping the file open pins
26 unmounted. Watching a file should not require that it be open.
37 A watch consumes less memory than an open file, separating the number
88 interfaces. The only real difference was whether we wanted to use open(2)
/Documentation/devicetree/bindings/serio/
Dps2-gpio.yaml19 active high using open drain with (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)
20 from <dt-bindings/gpio/gpio.h> since the signal is open drain by
27 active high using open drain with (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)
28 from <dt-bindings/gpio/gpio.h> since the signal is open drain by
/Documentation/filesystems/ext4/
Dmmp.rst11 open continues. If the sequence number is EXT4_MMP_SEQ_FSCK, then
12 fsck is (hopefully) running, and open fails immediately. Otherwise, the
13 open code will wait for twice the specified MMP check interval and check
15 filesystem is active on another machine and the open fails. If the MMP
28 an open operation succeeds. The MMP code does not use these values; they
/Documentation/devicetree/bindings/pwm/
Dnxp,pca9685-pwm.txt13 - open-drain (bool): boolean to configure outputs with open-drain structure;
26 open-drain;
/Documentation/driver-api/media/
Dv4l2-fh.rst20 structure and ``file->private_data`` is set to it in the driver's ``open()``
26 #) :c:func:`v4l2_fh_init` and :c:func:`v4l2_fh_add` in ``open()``
83 :c:type:`v4l2_file_operations`->open() handler.
119 These two functions can be plugged into the v4l2_file_operation's ``open()``
124 whether the :c:type:`v4l2_fh` struct is the only open filehandle of the
130 - Returns 1 if the file handle is the only open file handle, else 0.
/Documentation/devicetree/bindings/watchdog/
Dxlnx,versal-wwdt.yaml14 Window watchdog timer(WWDT) contains closed(first) and open(second)
18 restarted within the open window time. If software tries to restart
19 WWDT outside of the open window time period, it generates a reset.
/Documentation/filesystems/nfs/
Dclient-identifier.rst8 instances in order to maintain file open and lock state during
26 The server collects each client's file open and lock state under
34 the NFSv4 protocol allows the server to remove the client's open
36 restarts, it indicates to servers that open and lock state
44 sending fresh OPEN and LOCK requests. This enables file locks to
100 Neither client can maintain open or lock state in this scenario.
111 the client's previous open and lock state. This blocks access to
116 client to reclaim its open and lock state, and may give those locks
202 Once a client establishes open and lock state, the NFSv4 protocol
/Documentation/arch/powerpc/
Dbooting.rst19 of a device-tree whose format is defined after Open Firmware specification.
41 a) Boot from Open Firmware. If your firmware is compatible
42 with Open Firmware (IEEE 1275) or provides an OF compatible
54 extract the device-tree and other information from open
63 called directly by a bootloader that does not support the Open
67 details in this document, as method a) is simply standard Open
/Documentation/hwmon/
Dg762.rst5 and performs closed-loop or open-loop control of the fan speed. Two
50 speed control (open-loop) via pwm1 described below, 2 for
58 get or set PWM fan control value in open-loop mode. This is an
63 when current fan speed control mode is open-loop ('pwm1_enable' set to 1),

12345678910>>...30