Home
last modified time | relevance | path

Searched +full:write +full:- +full:to +full:- +full:read (Results 1 – 25 of 1117) sorted by relevance

12345678910>>...45

/linux-6.12.1/tools/perf/pmu-events/arch/arm64/freescale/imx8mp/sys/
Dmetrics.json3 "BriefDescription": "bytes of all masters read from ddr",
5 "MetricExpr": "imx8_ddr0@axid\\-read\\,axi_mask\\=0xffff\\,axi_id\\=0x0000@",
6 "ScaleUnit": "9.765625e-4KB",
11 "BriefDescription": "bytes of all masters write to ddr",
13 "MetricExpr": "imx8_ddr0@axid\\-write\\,axi_mask\\=0xffff\\,axi_id\\=0x0000@",
14 "ScaleUnit": "9.765625e-4KB",
19 "BriefDescription": "bytes of a53 core read from ddr",
21 "MetricExpr": "imx8_ddr0@axid\\-read\\,axi_mask\\=0x0000\\,axi_id\\=0x0000@",
22 "ScaleUnit": "9.765625e-4KB",
27 "BriefDescription": "bytes of a53 core write to ddr",
[all …]
/linux-6.12.1/drivers/net/ethernet/aquantia/atlantic/macsec/
Dmacsec_api.h1 /* SPDX-License-Identifier: GPL-2.0-only */
48 /*! Read the raw table data from the specified row of the Egress CTL
50 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
51 * table_index - The table row to read (max 23).
57 /*! Pack the fields of rec, and write the packed data into the
59 * rec - [IN] The bitfield values to write to the table row.
60 * table_index - The table row to write(max 23).
66 /*! Read the raw table data from the specified row of the Egress
68 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
69 * table_index - The table row to read (max 47).
[all …]
/linux-6.12.1/Documentation/filesystems/spufs/
Dspufs.rst1 .. 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 …]
/linux-6.12.1/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];
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 …]
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-cti1 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 …]
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
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 …]
Dsysfs-class-bdi14 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 …]
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
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 …]
Dsysfs-driver-xdata1 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 …]
Dconfigfs-spear-pcie-gadget1 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 …]
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
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 …]
/linux-6.12.1/tools/perf/pmu-events/arch/arm64/freescale/imx95/sys/
Dmetrics.json11 "BriefDescription": "bytes of all masters read from ddr",
14 "ScaleUnit": "9.765625e-4KB",
19 "BriefDescription": "bytes of all masters write to ddr",
22 "ScaleUnit": "9.765625e-4KB",
27 "BriefDescription": "bytes of all a55 read from ddr",
30 "ScaleUnit": "9.765625e-4KB",
35 "BriefDescription": "bytes of all a55 write to ddr (part1)",
38 "ScaleUnit": "9.765625e-4KB",
43 "BriefDescription": "bytes of all a55 write to ddr (part2)",
46 "ScaleUnit": "9.765625e-4KB",
[all …]
/linux-6.12.1/drivers/rtc/
Drtc-ds1685.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * An rtc driver for the Dallas/Maxim DS1685/DS1687 and related real-time
6 * Copyright (C) 2011-2014 Joshua Kinard <kumba@gentoo.org>.
7 * Copyright (C) 2009 Matthias Fuchs <matthias.fuchs@esd-electronics.com>.
10 * DS1685/DS1687 3V/5V Real-Time Clocks, 19-5215, Rev 4/10.
11 * DS17x85/DS17x87 3V/5V Real-Time Clocks, 19-5222, Rev 4/10.
12 * DS1689/DS1693 3V/5V Serialized Real-Time Clocks, Rev 112105.
33 /* ----------------------------------------------------------------------- */
35 * Standard read/write
40 * ds1685_read - read a value from an rtc register.
[all …]
/linux-6.12.1/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
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 …]
/linux-6.12.1/arch/parisc/kernel/
Dperf_asm.S1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 /* low-level asm for "intrigue" (PA8500-8700 CPU perf counters)
5 * Copyright (C) 2001 Randolph Chung <tausq at parisc-linux.org>
6 * Copyright (C) 2001 Hewlett-Packard (Grant Grundler)
30 ; The coprocessor only needs to be enabled when
45 ssm 0,0 ; dummy op to ensure completion
71 ssm 0,0 ; dummy op to ensure completion
86 ;* is shifted shifted backup immediately. This is to compensate
91 ;* arg0 : rdr to be read
98 ;* arg0 : rdr to be read
[all …]
/linux-6.12.1/tools/perf/pmu-events/arch/x86/snowridgex/
Duncore-memory.json3 "BriefDescription": "read requests to memory controller. Derived from unc_m_cas_count.rd",
8 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu…
14 "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr",
19 …"PublicDescription": "Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-p…
30 …channel. Activate commands are issued to open up a page on the DRAM devices so that it can be rea…
35 "BriefDescription": "DRAM Activate Count : Activate due to Bypass",
41 …to Bypass : Counts the number of DRAM Activate commands sent on this channel. Activate commands a…
56 "BriefDescription": "All DRAM read CAS commands issued (including underfills)",
61 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu…
66 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre",
[all …]
/linux-6.12.1/tools/testing/selftests/kvm/lib/
Dio.c1 // SPDX-License-Identifier: GPL-2.0-only
10 /* Test Write
12 * A wrapper for write(2), that automatically handles the following
16 * + Write of less than requested amount
17 * + Non-block return (EAGAIN)
19 * For each of the above, an additional write is performed to automatically
21 * There are also many cases where write(2) can return an unexpected
24 * Note, for function signature compatibility with write(2), this function
26 * to the number of requested bytes. All other conditions in this and
27 * future enhancements to this function either automatically issue another
[all …]
/linux-6.12.1/Documentation/locking/
Dseqlock.rst8 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 …]
/linux-6.12.1/include/uapi/linux/
Dvirtio_pci.h4 * This module allows virtio devices to be used over a virtual PCI device.
12 * This header is BSD licensed so anyone can use the definitions to implement
24 * may be used to endorse or promote products derived from this software
27 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
31 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
46 /* A 32-bit r/o bitmask of the features supported by the host */
49 /* A 32-bit r/w bitmask of features activated by the guest */
52 /* A 32-bit r/w PFN for the currently selected queue */
55 /* A 16-bit r/o queue size for the currently selected queue */
58 /* A 16-bit r/w queue selector */
[all …]
/linux-6.12.1/tools/perf/pmu-events/arch/x86/icelakex/
Duncore-memory.json8 …channel. Activate commands are issued to open up a page on the DRAM devices so that it can be rea…
13 "BriefDescription": "DRAM Activate Count : Activate due to Bypass",
19 …to Bypass : Counts the number of DRAM Activate commands sent on this channel. Activate commands a…
34 "BriefDescription": "All DRAM read CAS commands issued (including underfills)",
39 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu…
44 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre",
50 …ommands. : DRAM RD_CAS commands w/auto-pre : DRAM RD_CAS and WR_CAS Commands : Counts the total nu…
66 "BriefDescription": "All DRAM read CAS commands issued (does not include underfills)",
72 …"PublicDescription": "Counts the total number of DRAM Read CAS commands issued on this channel. T…
77 "BriefDescription": "DRAM underfill read CAS commands issued",
[all …]
/linux-6.12.1/tools/perf/pmu-events/arch/arm64/thead/yitian710/sys/
Dali_drw.json3 "BriefDescription": "A Write or Read Op at HIF interface. The unit is 64B.",
10 "BriefDescription": "A Write Op at HIF interface. The unit is 64B.",
17 "BriefDescription": "A Read Op at HIF interface. The unit is 64B.",
24 "BriefDescription": "A Read-Modify-Write Op at HIF interface. The unit is 64B.",
31 "BriefDescription": "A high priority Read at HIF interface. The unit is 64B.",
38 "BriefDescription": "A write data cycle at DFI interface (to DRAM).",
45 "BriefDescription": "A read data cycle at DFI interface (to DRAM).",
52 "BriefDescription": "A high priority read becomes critical.",
59 "BriefDescription": "A low priority read becomes critical.",
66 "BriefDescription": "A write becomes critical.",
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/memory-controllers/
Dti-aemif.txt3 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 …]
/linux-6.12.1/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"
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
/linux-6.12.1/drivers/char/xilinx_hwicap/
Dfifo_icap.c11 * AS A COURTESY TO YOU, SOLELY FOR USE IN DEVELOPING PROGRAMS AND
18 * WARRANTY WHATSOEVER WITH RESPECT TO THE ADEQUACY OF THE
19 * IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
24 * (c) Copyright 2007-2008 Xilinx Inc.
28 * with this program; if not, write to the Free Software Foundation, Inc.,
39 #define XHI_WF_OFFSET 0x100 /* Write FIFO */
40 #define XHI_RF_OFFSET 0x104 /* Read FIFO */
44 #define XHI_WFV_OFFSET 0x114 /* Write FIFO Vacancy Register */
45 #define XHI_RFO_OFFSET 0x118 /* Read FIFO Occupancy Register */
56 * write.
[all …]
/linux-6.12.1/tools/virtio/virtio-trace/
DREADME1 Trace Agent for virtio-trace
4 Trace agent is a user tool for sending trace data of a guest to a Host in low
6 - splice a page of ring-buffer to read_pipe without memory copying
7 - splice the page from write_pipe to virtio-console without memory copying
8 - write trace data to stdout by using -o option
9 - controlled by start/stop orders from a Host
13 2) Create a read/write thread per CPU. Each thread is bound to a CPU.
14 The read/write threads hold it.
17 the controller wake read/write threads.
18 5) The read/write threads start to read trace data from ring-buffers and
[all …]

12345678910>>...45