Searched +full:write +full:- +full:to +full:- +full:read (Results 1 – 25 of 882) sorted by relevance
12345678910>>...36
| /Documentation/ABI/testing/ |
| 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-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-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-class-bdi | 14 non-block filesystems which provide their own BDI, such as NFS
17 MAJOR:MINOR-fuseblk
23 The default backing dev, used for non-block device backed
30 Size of the read-ahead window in kilobytes
32 (read-write)
38 total write-back cache that relates to its current average
39 writeout speed in relation to the other devices.
42 percentage of the write-back cache to a particular device.
45 (read-write)
52 total write-back cache that relates to its current average
[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-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 | sysfs-block-zram | 5 The disksize file is read-write and specifies the disk size
14 The initstate file is read-only and shows the initialization
21 The reset file is write-only and allows resetting the
29 The max_comp_streams file is read-write and specifies the
37 The comp_algorithm file is read-write and lets to show
45 The mem_used_max file is write-only and is used to reset
46 the counter of maximum memory zram have consumed to store
47 compressed data. For resetting the value, you should write
48 "0". Otherwise, you could see -EINVAL.
55 The mem_limit file is write-only and specifies the maximum
[all …]
|
| D | debugfs-scmi-raw | 5 Description: SCMI Raw synchronous message injection/snooping facility; write
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
20 Description: SCMI Raw asynchronous message injection/snooping facility; write
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
[all …]
|
| D | sysfs-class-firmware | 5 Description: The data sysfs file is used for firmware-fallback and for
6 firmware uploads. Cat a firmware image to this sysfs file
7 after you echo 1 to the loading sysfs file. When the firmware
8 image write is complete, echo 0 to the loading sysfs file. This
9 sequence will signal the completion of the firmware write and
10 signal the lower-level driver that the firmware data is
17 Description: Write-only. For firmware uploads, write a "1" to this file to
18 request that the transfer of firmware data to the lower-level
20 the update cannot be canceled (e.g. a FLASH write is in
27 Description: Read-only. Returns a string describing a failed firmware
[all …]
|
| D | sysfs-driver-qat_rl | 4 Contact: qat-linux@intel.com
6 (WO) This attribute is used to perform an operation on an SLA.
10 this group before a write to this file.
39 Contact: qat-linux@intel.com
41 (RW) When read, reports the current assigned ring pairs for the
43 When wrote to, configures the ring pairs associated to a new SLA.
45 The value is a 64-bit bit mask and is written/displayed in hex.
49 Selected ring pairs must to be assigned to a single service,
51 assigned to a certain ring pair can be checked by querying
58 * WRITE: add operation
[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
13 Write parses one of 'YyTt1NnFf0', or [oO][NnFf] for "on"
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/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/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
21 message queues. Users that have write permissions on the file system
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
[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
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
[all …]
|
| /Documentation/filesystems/ |
| D | zonefs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ZoneFS - Zone filesystem for Zoned block devices
11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
12 device support (e.g. f2fs), zonefs does not hide the sequential write
13 constraint of zoned block devices to the user. Files representing sequential
14 write zones of the device must be written sequentially starting from the end
17 As such, zonefs is in essence closer to a raw block device access interface
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
21 direct block device file ioctls which may be more obscure to developers. One
22 example of this approach is the implementation of LSM (log-structured merge)
[all …]
|
| D | fuse-io.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 - direct-io
10 - cached
11 + write-through
12 + writeback-cache
14 The direct-io mode can be selected with the FOPEN_DIRECT_IO flag in the
17 In direct-io mode the page cache is completely bypassed for reads and writes.
18 No read-ahead takes place. Shared mmap is disabled by default. To allow shared
22 read-ahead by the kernel to fill the cache. The cache is always kept consistent
23 after any writes to the file. All mmap modes are supported.
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 3 The Async External Memory Interface (EMIF16/AEMIF) controller is intended to
4 provide a glue-less interface to a variety of asynchronous memory devices like
11 Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
12 OMAP-L138 (DA850) - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
13 Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
17 - compatible: "ti,davinci-aemif"
18 "ti,keystone-aemif"
19 "ti,da850-aemif"
21 - reg: contains offset/length value for AEMIF control registers
24 - #address-cells: Must be 2. The partition number has to be encoded in the
[all …]
|
| D | st,stm32-fmc2-ebi-props.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/st,stm32-fmc2-ebi-props.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Christophe Kerello <christophe.kerello@foss.st.com>
11 - Marek Vasut <marex@denx.de>
14 st,fmc2-ebi-cs-transaction-type:
25 8: Synchronous read synchronous write PSRAM.
26 9: Synchronous read asynchronous write PSRAM.
27 10: Synchronous read synchronous write NOR.
[all …]
|
| /Documentation/bpf/ |
| D | prog_cgroup_sysctl.rst | 1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
8 provides cgroup-bpf hook for sysctl.
10 The hook has to be attached to a cgroup and will be called every time a
11 process inside that cgroup tries to read from or write to sysctl knob in proc.
16 ``BPF_CGROUP_SYSCTL`` attach type has to be used to attach
17 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` program to a cgroup.
22 ``BPF_PROG_TYPE_CGROUP_SYSCTL`` provides access to the following context from
26 __u32 write;
30 * ``write`` indicates whether sysctl value is being read (``0``) or written
31 (``1``). This field is read-only.
[all …]
|
| /Documentation/hwmon/ |
| D | oxp-sensors.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
3 Kernel driver oxp-sensors
7 - Derek John Clark <derekjohn.clark@gmail.com>
8 - Joaquín Ignacio Aramendía <samsagax@gmail.com>
11 ------------
27 -----------------
31 - AOKZOE A1
32 - AOKZOE A1 PRO
33 - AYANEO 2
34 - AYANEO 2S
[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/block/ |
| D | stat.rst | 18 each, it would be impossible to guarantee that a set of readings
29 read I/Os requests number of read I/Os processed
30 read merges requests number of read I/Os merged with in-queue I/O
31 read sectors sectors number of sectors read
32 read ticks milliseconds total wait time for read requests
33 write I/Os requests number of write I/Os processed
34 write merges requests number of write I/Os merged with in-queue I/O
35 write sectors sectors number of sectors written
36 write ticks milliseconds total wait time for write requests
41 discard merges requests number of discard I/Os merged with in-queue I/O
[all …]
|
| /Documentation/hid/ |
| D | hiddev.rst | 8 In addition to the normal input type HID devices, USB also uses the
14 To support these disparate requirements, the Linux USB system provides
15 HID events to two separate interfaces:
18 normalised event interface - see Documentation/input/input.rst
24 usb.c ---> hid-core.c ----> hid-input.c ----> [keyboard/mouse/joystick/event]
27 --> hiddev.c ----> POWER / MONITOR CONTROL
57 So you point your hiddev compliant user-space program at the correct
60 Assuming that you have a hiddev compliant user-space program, of
61 course. If you need to write one, read on.
67 This description should be read in conjunction with the HID
[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 …]
|
| /Documentation/devicetree/bindings/bus/ |
| D | qcom,ebi2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 external memory (such as NAND or other memory-mapped peripherals) whereas
14 As it says it connects devices to an external bus interface, meaning address
15 lines (up to 9 address lines so can only address 1KiB external memory space),
17 NOR flash memories), WE (write enable). This on top of 6 different chip selects
22 unused they can be left unconnected or remuxed to be used as GPIO or in some
25 Also CS1 and CS2 has -A and -B signals. Why they have that is unclear to me.
28 memory is referred to as "Chip Peripheral SS FPB0" and is 168MB big.
[all …]
|
12345678910>>...36