Searched refs:fields (Results 1 – 25 of 735) sorted by path
12345678910>>...30
/linux/ |
H A D | CREDITS | 4 scripts. The fields are: name (N), email (E), web-address
|
/linux/Documentation/ABI/ |
H A D | README | 62 The fields should be use a simple notation, compatible with ReST markup.
|
/linux/Documentation/ABI/stable/ |
H A D | sysfs-block | 44 The report contains 2 fields: one for read requests 713 statistics of disk <disk>. They contain 11 fields:
|
/linux/Documentation/ABI/testing/ |
H A D | debugfs-intel-iommu | 87 '-1' and other PASID related fields are invalid.
|
H A D | dev-kmsg | 76 and a flag field. All fields are separated by a ','. 79 the terminating ';'. Unknown fields and values should be
|
H A D | procfs-diskstats | 7 fields: 26 Kernel 4.18+ appends four more fields for discard 36 Kernel 5.5+ appends two more fields for flush requests:
|
H A D | procfs-smaps_rollup | 10 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 D | sysfs-bus-bcma | 30 Each BCMA core is identified by few fields, including class it
|
H A D | sysfs-bus-coresight-devices-etm3x | 25 processor contect ID to trigger on, etc. Individual fields in
|
H A D | sysfs-bus-pci | 46 and Device ID fields are required, the rest are optional. 62 and Class Mask. The Vendor ID and Device ID fields are
|
H A D | sysfs-bus-usb | 41 The vendor ID and device ID fields are required, the
|
H A D | sysfs-bus-usb-devices-usbsevseg | 46 change this fields value to ``k + 10 ** m``.
|
H A D | sysfs-class-net-cdc_ncm | 82 The following read-only attributes all represent fields of the
|
H A D | sysfs-class-usb_power_delivery | 55 Devices containing the attributes (the bit fields) defined for 61 Supply Object. vSafe5V Object has additional fields defined for
|
H A D | sysfs-devices-platform-ipmi | 47 fields, and functionality that are provided by the controller
|
H A D | sysfs-devices-soc | 35 or more eight (8) bit fields, each consisting of seven (7)
|
H A D | sysfs-ibft | 29 that expose the SIGNATURE, OEM_ID, and OEM_TABLE_ID fields of the
|
/linux/Documentation/PCI/endpoint/function/binding/ |
H A D | pci-ntb.rst | 28 NTB EPF specific configurable fields:
|
/linux/Documentation/PCI/endpoint/ |
H A D | pci-ntb-function.rst | 70 The format of Config Region is given below. All the fields here are 32 bits.
|
H A D | pci-ntb-howto.rst | 63 configurable fields::
|
H A D | pci-test-howto.rst | 58 configurable fields::
|
H A D | pci-vntb-howto.rst | 59 configurable fields::
|
/linux/Documentation/PCI/ |
H A D | pci.rst | 99 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 D | pcieaer-howto.rst | 86 fields.
|
/linux/Documentation/RCU/Design/Data-Structures/ |
H A D | Data-Structures.rst | 140 #. 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