Searched +full:read +full:- +full:to +full:- +full:read (Results 1 – 25 of 1022) sorted by relevance
12345678910>>...41
| /Documentation/userspace-api/media/v4l/ |
| D | func-read.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _func-read:
7 V4L2 read()
13 v4l2-read - Read from a V4L2 device
18 .. code-block:: c
22 .. c:function:: ssize_t read( int fd, void *buf, size_t count )
31 Buffer to be filled
34 Max number of bytes to read
39 :c:func:`read()` attempts to read up to ``count`` bytes from file
42 section, see ##. If ``count`` is zero, :c:func:`read()` returns zero
[all …]
|
| /Documentation/filesystems/spufs/ |
| D | spufs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 spufs - the SPU file system
17 Broadband Engine Architecture in order to access Synergistic Processor
20 The file system provides a name space similar to posix shared memory or
22 can use spu_create(2) to establish SPU contexts in the spufs root.
26 logical SPU. Users can change permissions on those files, but not actu-
43 The files in spufs mostly follow the standard behavior for regular sys-
44 tem calls like read(2) or write(2), but often support only a subset of
49 All files that support the read(2) operation also support readv(2) and
55 All files support the chmod(2)/fchmod(2) and chown(2)/fchown(2) opera-
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-dfl-port | 1 What: /sys/bus/platform/devices/dfl-port.0/id
5 Description: Read-only. It returns id of this port. One DFL FPGA device
6 may have more than one port. Userspace could use this id to
9 What: /sys/bus/platform/devices/dfl-port.0/afu_id
13 Description: Read-only. User can program different PR bitstreams to FPGA
15 returns uuid which could be used to identify which PR bitstream
18 What: /sys/bus/platform/devices/dfl-port.0/power_state
22 Description: Read-only. It reports the APx (AFU Power) state, different APx
24 returns "0" - Normal / "1" - AP1 / "2" - AP2 / "6" - AP6.
26 What: /sys/bus/platform/devices/dfl-port.0/ap1_event
[all …]
|
| D | sysfs-bus-coresight-devices-tmc | 5 Description: (RW) Disables write access to the Trace RAM by stopping the
8 driver are expected to be added as it matures.
14 Description: (Read) Defines the size, in 32-bit words, of the local RAM buffer.
15 The value is read directly from HW register RSZ, 0x004.
21 Description: (Read) Shows the value held by the TMC status register. The value
22 is read directly from HW register STS, 0x00C.
28 Description: (Read) Shows the value held by the TMC RAM Read Pointer register
29 that is used to read entries from the Trace RAM over the APB
30 interface. The value is read directly from HW register RRP,
37 Description: (Read) Shows the value held by the TMC RAM Write Pointer register
[all …]
|
| D | sysfs-platform-dfl-fme | 1 What: /sys/bus/platform/devices/dfl-fme.0/ports_num
5 Description: Read-only. One DFL FPGA device may have more than 1
7 number of ports on the FPGA device when read it.
9 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_id
13 Description: Read-only. It returns Bitstream (static FPGA region)
17 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_metadata
21 Description: Read-only. It returns Bitstream (static FPGA region) meta
25 What: /sys/bus/platform/devices/dfl-fme.0/cache_size
29 Description: Read-only. It returns cache size of this FPGA device.
31 What: /sys/bus/platform/devices/dfl-fme.0/fabric_version
[all …]
|
| D | configfs-spear-pcie-gadget | 1 What: /config/pcie-gadget
7 Interface is used to configure selected dual mode PCIe controller
8 as device and then program its various registers to configure it
10 This interfaces can be used to show spear's PCIe device capability.
12 Nodes are only visible when configfs is mounted. To mount configfs
15 # mount -t configfs none /config/
17 For nth PCIe Device Controller /config/pcie-gadget.n/:
20 link used to enable ltssm and read its status.
21 int_type used to configure and read type of supported interrupt
22 no_of_msi used to configure number of MSI vector needed and
[all …]
|
| D | sysfs-bus-coresight-devices-etb10 | 16 Description: (RW) Disables write access to the Trace RAM by stopping the
18 following the trigger event. The number of 32-bit words written
19 into the Trace RAM following the trigger event is equal to the
20 value stored in this register+1 (from ARM ETB-TRM).
26 Description: (Read) Defines the depth, in words, of the trace RAM in powers of
27 2. The value is read directly from HW register RDP, 0x004.
33 Description: (Read) Shows the value held by the ETB status register. The value
34 is read directly from HW register STS, 0x00C.
40 Description: (Read) Shows the value held by the ETB RAM Read Pointer register
41 that is used to read entries from the Trace RAM over the APB
[all …]
|
| D | sysfs-driver-xdata | 1 What: /sys/class/misc/drivers/dw-xdata-pcie.<device>/write
5 Description: Allows the user to enable the PCIe traffic generator which
6 will create write TLPs frames - from the Root Complex to the
7 Endpoint direction or to disable the PCIe traffic generator
10 Write y/1/on to enable, n/0/off to disable
13 echo 1 > /sys/class/misc/dw-xdata-pcie.<device>/write
15 echo 0 > /sys/class/misc/dw-xdata-pcie.<device>/write
17 The user can read the current PCIe link throughput generated
21 cat /sys/class/misc/dw-xdata-pcie.<device>/write
24 The file is read and write.
[all …]
|
| D | sysfs-bus-coresight-devices-cti | 1 What: /sys/bus/coresight/devices/<cti-name>/enable
7 What: /sys/bus/coresight/devices/<cti-name>/powered
11 Description: (Read) Indicate if the CTI hardware is powered.
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
17 Description: (Read) Display the associated CTM ID
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
29 Description: (Read) Name of connected device <N>
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
[all …]
|
| D | sysfs-class-watchdog | 5 It is a read only file. It contains status of the watchdog
6 device at boot. It is equivalent to WDIOC_GETBOOTSTATUS of
13 It is a read only file. It contains options of watchdog device.
19 It is a read only file. It contains firmware version of
26 It is a read only file. It contains identity string of
33 It is a read/write file. While reading, it gives '1'
35 it gives '0'. Writing a '1' to the file enables the
45 It is a read only file. It gives active/inactive status of
52 It is a read only file. It contains watchdog device's
53 internal status bits. It is equivalent to WDIOC_GETSTATUS
[all …]
|
| D | sysfs-driver-w1_therm | 5 (RW) read or write TH and TL (Temperature High an Low) alarms.
7 (typical -55 degC to 125 degC), if not values will be trimmed
8 to device min/max capabilities. Values are integer as they are
10 automatically put to TL. Once set, alarms could be search at
11 master level, refer to Documentation/w1/w1-generic.rst for
13 Users: any user space application which wants to communicate with
22 device data to its embedded EEPROM, either restore data
26 * 'save': save device RAM to EEPROM
29 Users: any user space application which wants to communicate with
41 * '-xx': xx is kernel error when reading power status
[all …]
|
| D | debugfs-scmi-raw | 7 in little-endian binary format to have it sent to the configured
9 Any subsequently received response can be read from this same
11 Each write to the entry causes one command request to be built
12 and sent while the replies are read back one message at time
22 in little-endian binary format to have it sent to the configured
24 Any subsequently received response can be read from this same
26 Any additional delayed response received afterwards can be read
29 Each write to the entry causes one command request to be built
30 and sent while the replies are read back one message at time
38 Description: SCMI Raw message errors facility; any kind of timed-out or
[all …]
|
| /Documentation/filesystems/ |
| D | netfs_library.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - Overview.
10 - Per-inode context.
11 - Inode context helper functions.
12 - Buffered read helpers.
13 - Read helper functions.
14 - Read helper structures.
15 - Read helper operations.
16 - Read helper procedure.
17 - Read helper cache API.
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-nvmem | 6 This read/write attribute allows users to set read-write
7 devices as read-only and back to read-write from userspace.
8 This can be used to unlock and relock write-protection of
11 Read returns '0' or '1' for read-write or read-only modes
23 This file allows user to read/write the raw NVMEM contents.
24 Permissions for write to this file depends on the nvmem
46 This read-only attribute allows user to read the NVMEM
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
4 .. _lirc-read:
7 LIRC read()
13 lirc-read - Read from a LIRC device
18 .. code-block:: c
22 .. c:function:: ssize_t read( int fd, void *buf, size_t count )
31 Buffer to be filled
34 Max number of bytes to read
39 :c:func:`read()` attempts to read up to ``count`` bytes from file
41 :c:func:`read()` returns zero and has no other results. If ``count``
[all …]
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 5 mount -t ufs -o ufstype=type_of_ufs device dir
14 some implementations are undocumented, so its hard to recognize
20 default value, supported as read-only
24 supported as read-write
28 supported as read-write
35 supported as read-write
39 supported as read-write
42 used in HP-UX
43 supported as read-only
47 supported as read-only
[all …]
|
| /Documentation/wmi/devices/ |
| D | msi-wmi-platform.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
4 MSI WMI Platform Features driver (msi-wmi-platform)
24 guid("{ABBC0F60-8EA1-11d1-00A0-C90629100000}")]
26 [WmiDataId(1), read, write, Description("16 bytes of data")] uint8 Bytes[16];
31 guid("{ABBC0F63-8EA1-11d1-00A0-C90629100000}")]
33 [WmiDataId(1), read, write, Description("32 bytes of data")] uint8 Bytes[32];
37 Description("Class used to operate methods on a package"),
38 guid("{ABBC0F6E-8EA1-11d1-00A0-C90629100000}")]
40 [key, read] string InstanceName;
41 [read] boolean Active;
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-lineinfo-changed-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-lineinfo-changed-read.rst.
16 GPIO_LINEINFO_CHANGED_READ - Read line info change events for watched lines
22 ``int read(int chip_fd, void *buf, size_t count)``
31 The buffer to contain the :c:type:`events<gpioline_info_changed>`.
40 Read line info change events for watched lines from the chip.
46 These events relate to changes in a line's request state or configuration,
47 not its value. Use gpio-lineevent-data-read.rst to receive events when a
50 A line must be watched using gpio-get-lineinfo-watch-ioctl.rst to generate
55 from where they can be read by userspace at its convenience using `read()`.
[all …]
|
| D | gpio-v2-lineinfo-changed-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINEINFO_CHANGED_READ - Read line info changed events for watched
18 ``int read(int chip_fd, void *buf, size_t count)``
27 The buffer to contain the :c:type:`events<gpio_v2_line_info_changed>`.
36 Read line info changed events for watched lines from the chip.
42 These events relate to changes in a line's request state or configuration,
43 not its value. Use gpio-v2-line-event-read.rst to receive events when a
46 A line must be watched using gpio-v2-get-lineinfo-watch-ioctl.rst to generate
51 from where they can be read by userspace at its convenience using `read()`.
55 The buffer may overflow if bursts of events occur quicker than they are read
[all …]
|
| D | gpio-lineevent-data-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-line-event-read.rst.
16 GPIO_LINEEVENT_DATA_READ - Read edge detection events from a line event.
21 ``int read(int event_fd, void *buf, size_t count)``
28 :c:type:`request.fd<gpioevent_request>` by gpio-get-lineevent-ioctl.rst.
31 The buffer to contain the :c:type:`events<gpioevent_data>`.
40 Read edge detection events for a line from a line event.
47 Edges are defined in terms of changes to the logical line value, so an inactive
48 to active transition is a rising edge. If ``GPIOHANDLE_REQUEST_ACTIVE_LOW`` is
50 ``GPIOEVENT_REQUEST_RISING_EDGE`` then corresponds to a falling physical edge.
[all …]
|
| D | gpio-v2-line-event-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINE_EVENT_READ - Read edge detection events for lines from a request.
17 ``int read(int req_fd, void *buf, size_t count)``
24 :c:type:`request.fd<gpio_v2_line_request>` by gpio-v2-get-line-ioctl.rst.
27 The buffer to contain the :c:type:`events<gpio_v2_line_event>`.
36 Read edge detection events for lines from a request.
43 Edges are defined in terms of changes to the logical line value, so an inactive
44 to active transition is a rising edge. If ``GPIO_V2_LINE_FLAG_ACTIVE_LOW`` is
46 ``GPIO_V2_LINE_FLAG_EDGE_RISING`` then corresponds to a falling physical edge.
48 The kernel captures and timestamps edge events as close as possible to their
[all …]
|
| /Documentation/arch/s390/ |
| D | monreader.rst | 2 Linux API for read access to z/VM Monitor Records
5 Date : 2004-Nov-26
15 usable from user space and allows read access to the z/VM Monitor Records
21 The z/VM guest on which you want to access this API needs to be configured in
22 order to allow IUCV connections to the `*MONITOR` service, i.e. it needs the
23 IUCV `*MONITOR` statement in its user entry. If the monitor DCSS to be used is
25 This item will use the IUCV device driver to access the z/VM services, so you
28 There are two options for being able to load the monitor DCSS (examples assume
33 See also "CP Command and Utility Reference" (SC24-6081-00) for more information
35 and Administration" (SC24-6116-00) for more information on DCSSes.
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-region.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ``devlink`` regions enable access to driver defined address regions using
13 Region snapshots are collected by the driver, and can be accessed via read
17 Snapshot identifiers are scoped to the devlink instance, not a region.
19 correspond to the same event.
21 The major benefit to creating a region is to provide access to internal
22 address regions that are otherwise inaccessible to the user.
24 Regions may also be used to provide an additional way to debug complex error
25 states, but see also Documentation/networking/devlink/devlink-health.rst
28 ``DEVLINK_CMD_REGION_NEW`` netlink message. A driver wishing to allow
[all …]
|
| /Documentation/locking/ |
| D | seqlock.rst | 8 Sequence counters are a reader-writer consistency mechanism with
9 lockless readers (read-only retry loops), and no writer starvation. They
10 are used for data that's rarely written to (e.g. system time), where the
11 reader wants a consistent set of information and is willing to retry if
15 read side critical section is even and the same sequence count value is
16 read again at the end of the critical section. The data in the set must
17 be copied out inside the read side critical section. If the sequence
23 is odd and indicates to the readers that an update is in progress. At
28 or interrupted by read side sections. Otherwise the reader will spin for
29 the entire scheduler tick due to the odd sequence count value and the
[all …]
|
| /Documentation/w1/slaves/ |
| D | w1_therm.rst | 16 -----------
32 read sequence will initiate a temperature conversion, then provide two
34 read along with a calculated crc value and YES or NO if it matched.
39 Alternatively, temperature can be read using ``temperature`` sysfs, it
42 A bulk read of all devices on the bus could be done writing ``trigger``
43 to ``therm_bulk_read`` entry at w1_bus_master level. This will
44 send the convert command to all devices on the bus, and if parasite
49 -1 if at least one sensor still in conversion, 1 if conversion is complete
50 but at least one sensor value has not been read yet. Result temperature is
53 read is sent but one sensor is not read immediately, the next access to
[all …]
|
12345678910>>...41