Home
last modified time | relevance | path

Searched +full:write +full:- +full:only (Results 1 – 25 of 909) sorted by relevance

12345678910>>...37

/Documentation/ABI/stable/
Dsysfs-bus-nvmem6 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"
15 Note: This file is only present if CONFIG_NVMEM_SYSFS
23 This file allows user to read/write the raw NVMEM contents.
24 Permissions for write to this file depends on the nvmem
26 Note: This file is only present if CONFIG_NVMEM_SYSFS
46 This read-only attribute allows user to read the NVMEM
[all …]
/Documentation/ABI/testing/
Dsysfs-block-zram5 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
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
64 The compact file is write-only and trigger compaction for
[all …]
Dsysfs-platform-dfl-port1 What: /sys/bus/platform/devices/dfl-port.0/id
5 Description: Read-only. It returns id of this port. One DFL FPGA device
9 What: /sys/bus/platform/devices/dfl-port.0/afu_id
13 Description: Read-only. User can program different PR bitstreams to FPGA
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
30 Description: Read-write. Read this file for AP1 (AFU Power State 1) event.
31 It's used to indicate transient AP1 state. Write 1 to this
[all …]
Dsysfs-platform-dfl-fme1 What: /sys/bus/platform/devices/dfl-fme.0/ports_num
5 Description: Read-only. One DFL FPGA device may have more than 1
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
35 Description: Read-only. It returns fabric version of this FPGA device.
[all …]
Dconfigfs-most7 Attributes are visible only when configfs is mounted. To mount
9 # mount -t configfs none /sys/kernel/config/
22 configure the sub-buffer size for this channel
40 for MediaLB communication only)
46 communication only)
58 write '1' to this attribute to trigger the
60 configuration, the creation is post-poned until
64 write '1' to this attribute to destroy an
77 configure the sub-buffer size for this channel
95 for MediaLB communication only)
[all …]
Dsysfs-class-firmware5 Description: The data sysfs file is used for firmware-fallback and for
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
31 following: "hw-error", "timeout", "user-abort", "device-busy",
32 "invalid-file-size", "read-write-error", "flash-wearout". The
[all …]
Dsysfs-driver-qat_rl4 Contact: qat-linux@intel.com
10 this group before a write to this file.
34 This attribute is only available for qat_4xxx devices.
39 Contact: qat-linux@intel.com
45 The value is a 64-bit bit mask and is written/displayed in hex.
58 * WRITE: add operation
68 ## Write
71 This attribute is only available for qat_4xxx devices.
76 Contact: qat-linux@intel.com
80 This is valid only for the following operations: update, rm,
[all …]
Dconfigfs-spear-pcie-gadget1 What: /config/pcie-gadget
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/:
24 inta write 1 to assert INTA and 0 to de-assert.
25 send_msi write MSI vector to be sent.
26 vendor_id used to write and read vendor id (hex)
27 device_id used to write and read device id (hex)
28 bar0_size used to write and read bar0_size
29 bar0_address used to write and read bar0 mapped area in hex.
[all …]
Dsysfs-ptp41 Write integer to re-configure it.
76 use. By default, the value is 0 meaning that only the
110 This write-only file enables or disables external
111 timestamps. To enable external timestamps, write the
113 To disable external timestamps, write the channel
128 This write-only file enables or disables periodic
129 outputs. To enable a periodic output, write five
139 This write-only file enables or disables delivery of
141 events, write a "1" into the file. To disable events,
142 write a "0" into the file.
/Documentation/filesystems/
Dzonefs.rst1 .. 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
14 write zones of the device must be written sequentially starting from the end
15 of the file (append only writes).
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
22 example of this approach is the implementation of LSM (log-structured merge)
31 -------------------
38 conventional zones. Any read or write access can be executed, similarly to a
[all …]
/Documentation/admin-guide/
Dufs.rst5 mount -t ufs -o ufstype=type_of_ufs device dir
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
49 nextstep-cd
[all …]
/Documentation/hwmon/
Doxp-sensors.rst1 .. 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 …]
Dltc2947.rst1 Kernel drivers ltc2947-i2c and ltc2947-spi
10 Addresses scanned: -
14 https://www.analog.com/media/en/technical-documentation/data-sheets/LTC2947.pdf
26 independently to have setups like: energy1 accumulates always and enrgy2 only
37 The following attributes are supported. Limits are read-write, reset_history
38 is write-only and all the other attributes are read-only.
41 in0_input VP-VM voltage (mV).
46 in0_reset_history Write 1 to reset in1 history
49 in0_label Channel label (VP-VM)
56 in1_reset_history Write 1 to reset in2 history
[all …]
/Documentation/filesystems/spufs/
Dspufs.rst1 .. SPDX-License-Identifier: GPL-2.0
10 spufs - the SPU file system
21 message queues. Users that have write permissions on the file system
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
50 all files that support the write(2) operation also support writev(2).
52 only the st_mode, st_nlink, st_uid and st_gid fields of struct stat
55 All files support the chmod(2)/fchmod(2) and chown(2)/fchown(2) opera-
68 read(2), pread(2), write(2), pwrite(2), lseek(2)
[all …]
/Documentation/devicetree/bindings/memory-controllers/
Dti-aemif.txt4 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
25 first address cell and it may accept values 0..N-1
[all …]
Dst,stm32-fmc2-ebi-props.yaml1 # 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/
Dprog_cgroup_sysctl.rst1 .. SPDX-License-Identifier: (LGPL-2.1 OR BSD-2-Clause)
8 provides cgroup-bpf hook for sysctl.
11 process inside that cgroup tries to read from or write to sysctl knob in proc.
26 __u32 write;
30 * ``write`` indicates whether sysctl value is being read (``0``) or written
31 (``1``). This field is read-only.
34 or written. This field is read-write. Writing to the field sets the starting
35 position in sysctl proc file ``read(2)`` will be reading from or ``write(2)``
37 whole sysctl value by ``bpf_sysctl_set_new_value()`` on ``write(2)`` even
38 when it's called by user space on ``file_pos > 0``. Writing non-zero
[all …]
/Documentation/wmi/devices/
Dmsi-wmi-platform.rst1 .. 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];
38 guid("{ABBC0F6E-8EA1-11d1-00A0-C90629100000}")]
43 [WmiMethodId(1), Implemented, read, write, Description("Return the contents of a package")]
46 [WmiMethodId(2), Implemented, read, write, Description("Set the contents of a package")]
49 [WmiMethodId(3), Implemented, read, write, Description("Return the contents of a package")]
[all …]
/Documentation/w1/masters/
Dds2490.rst13 -----------
16 which allows to build USB <-> W1 bridges.
18 DS9490(R) is a USB <-> W1 bus master device
20 low-level operational chip.
24 - The weak pullup current is a minimum of 0.9mA and maximum of 6.0mA.
25 - The 5V strong pullup is supported with a minimum of 5.9mA and a
27 - The hardware will detect when devices are attached to the bus on the
28 next bus (reset?) operation, however only a message is printed as
31 - The number of USB bus transactions could be reduced if w1_reset_send
33 a write buffer and a read buffer (along with sizes) as arguments.
[all …]
/Documentation/driver-api/md/
Draid5-cache.rst7 caches data to the RAID disks. The cache can be in write-through (supported
8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since
9 3.4) has a new option '--write-journal' to create array with cache. Please
11 in write-through mode. A user can switch it to write-back mode by::
13 echo "write-back" > /sys/block/md0/md/journal_mode
15 And switch it back to write-through mode by::
17 echo "write-through" > /sys/block/md0/md/journal_mode
22 write-through mode
25 This mode mainly fixes the 'write hole' issue. For RAID 4/5/6 array, an unclean
27 and parity don't match. The reason is that a stripe write involves several RAID
[all …]
Draid5-ppl.rst10 array or using it is as degraded - data calculated from parity for array blocks
11 that have not been touched by a write request during the unclean shutdown can
12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
15 Partial parity for a write operation is the XOR of stripe data chunks not
16 modified by this write. It is just enough data needed for recovering from the
17 write hole. XORing partial parity with the modified chunks produces parity for
18 the stripe, consistent with its state before the write operation, regardless of
23 the array. Because of this, using write-intent bitmap and PPL together is not
26 When handling a write request PPL writes partial parity before new data and
27 parity are dispatched to disks. PPL is a distributed log - it is stored on
[all …]
/Documentation/admin-guide/device-mapper/
Dwritecache.rst14 1. type of the cache device - "p" or "s"
15 - p - persistent memory
16 - s - SSD
25 offset from the start of cache device in 512-byte sectors
45 applicable only to persistent memory - use the FUA flag
49 applicable only to persistent memory - don't use the FUA
53 - some underlying devices perform better with fua, some
64 dm-writecache target and replace it with dm-linear or
71 only metadata is promoted to the cache. This option
74 pause writeback if there was some write I/O redirected to
[all …]
/Documentation/driver-api/mmc/
Dmmc-dev-parts.rst15 Read and write access is provided to the two MMC boot partitions. Due to
18 platform, write access is disabled by default to reduce the chance of
21 To enable write access to /dev/mmcblkXbootY, disable the forced read-only
26 To re-enable read-only access::
30 The boot partitions can also be locked read only until the next power on,
37 feature has been disabled on the card, the file will be read-only.
/Documentation/devicetree/bindings/w1/
Dw1-uart.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/w1/w1-uart.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: UART 1-Wire Bus
10 - Christoph Winklhofer <cj.winklhofer@gmail.com>
13 UART 1-wire bus. Utilizes the UART interface via the Serial Device Bus
14 to create the 1-Wire timing patterns.
16 The UART peripheral must support full-duplex and operate in open-drain
18 baud-rate and transmitted byte, which corresponds to a 1-Wire read bit,
[all …]
/Documentation/i2c/
Dgpio-fault-injection.rst12 'i2c-fault-injector' subdirectory in the Kernel debugfs filesystem, usually
15 injection. They will be described now along with their intended use-cases.
21 -----
31 -----
56 --------------------------
58 This file is write only and you need to write the address of an existing I2C
68 -----------------------
70 Similar to above, this file is write only and you need to write the address of
77 a) the message sent out will be a write message
80 This is a highly delicate state, the device is set up to write any data to
[all …]

12345678910>>...37