Home
last modified time | relevance | path

Searched refs:fields (Results 1 – 25 of 735) sorted by path

12345678910>>...30

/linux/
H A DCREDITS4 scripts. The fields are: name (N), email (E), web-address
/linux/Documentation/ABI/
H A DREADME62 The fields should be use a simple notation, compatible with ReST markup.
/linux/Documentation/ABI/stable/
H A Dsysfs-block44 The report contains 2 fields: one for read requests
713 statistics of disk <disk>. They contain 11 fields:
/linux/Documentation/ABI/testing/
H A Ddebugfs-intel-iommu87 '-1' and other PASID related fields are invalid.
H A Ddev-kmsg76 and a flag field. All fields are separated by a ','.
79 the terminating ';'. Unknown fields and values should be
H A Dprocfs-diskstats7 fields:
26 Kernel 4.18+ appends four more fields for discard
36 Kernel 5.5+ appends two more fields for flush requests:
H A Dprocfs-smaps_rollup10 fields from all the maps in /proc/pid/smaps.
11 Additionally, the fields Pss_Anon, Pss_File and Pss_Shmem
12 are not present in /proc/pid/smaps. These fields represent
H A Dsysfs-bus-bcma30 Each BCMA core is identified by few fields, including class it
H A Dsysfs-bus-coresight-devices-etm3x25 processor contect ID to trigger on, etc. Individual fields in
H A Dsysfs-bus-pci46 and Device ID fields are required, the rest are optional.
62 and Class Mask. The Vendor ID and Device ID fields are
H A Dsysfs-bus-usb41 The vendor ID and device ID fields are required, the
H A Dsysfs-bus-usb-devices-usbsevseg46 change this fields value to ``k + 10 ** m``.
H A Dsysfs-class-net-cdc_ncm82 The following read-only attributes all represent fields of the
H A Dsysfs-class-usb_power_delivery55 Devices containing the attributes (the bit fields) defined for
61 Supply Object. vSafe5V Object has additional fields defined for
H A Dsysfs-devices-platform-ipmi47 fields, and functionality that are provided by the controller
H A Dsysfs-devices-soc35 or more eight (8) bit fields, each consisting of seven (7)
H A Dsysfs-ibft29 that expose the SIGNATURE, OEM_ID, and OEM_TABLE_ID fields of the
/linux/Documentation/PCI/endpoint/function/binding/
H A Dpci-ntb.rst28 NTB EPF specific configurable fields:
/linux/Documentation/PCI/endpoint/
H A Dpci-ntb-function.rst70 The format of Config Region is given below. All the fields here are 32 bits.
H A Dpci-ntb-howto.rst63 configurable fields::
H A Dpci-test-howto.rst58 configurable fields::
H A Dpci-vntb-howto.rst59 configurable fields::
/linux/Documentation/PCI/
H A Dpci.rst99 All fields are passed in as hexadecimal values (no leading 0x).
100 The vendor and device fields are mandatory, the others are optional. Users
101 need pass only as many optional fields as necessary:
103 - subvendor and subdevice fields default to PCI_ANY_ID (FFFFFFFF)
104 - class and classmask fields default to 0
302 Some drivers will need specific "capability" fields programmed
463 If you access fields in the standard portion of the config header, please
H A Dpcieaer-howto.rst86 fields.
/linux/Documentation/RCU/Design/Data-Structures/
H A DData-Structures.rst140 #. The fields in ``rcu_data`` are private to the corresponding CPU,
203 in groups, in the following sections. The more specialized fields are
262 All of these fields are constant once initialization is complete, and
282 There are ``->gp_seq`` fields in the ``rcu_node`` and ``rcu_data``
305 These fields are used for diagnostic and tracing purposes.
352 later. Finally, the ``->grplo`` and ``->grphi`` fields contain the
356 All of these fields are constant, and thus do not require any
368 This field is used to protect the remaining fields in this structure,
421 This portion of the ``rcu_node`` structure has fields as follows:
812 tree. These two fields are constant and therefore do not require
[all …]

12345678910>>...30