| /Documentation/netlink/specs/ |
| D | ethtool.yaml | 23 attributes:
36 attributes:
48 attributes:
53 nested-attributes: bitset-bit
56 attributes:
66 nested-attributes: bitset-bits
70 attributes:
79 attributes:
84 nested-attributes: string
87 attributes:
[all …]
|
| D | devlink.yaml | 23 attributes:
35 # TODO: fill in the attributes in between
42 # TODO: fill in the attributes in between
54 # TODO: fill in the attributes in between
61 # TODO: fill in the attributes in between
68 # TODO: fill in the attributes in between
75 # TODO: fill in the attributes in between
88 nested-attributes: dl-info-version
93 nested-attributes: dl-info-version
98 nested-attributes: dl-info-version
[all …]
|
| D | ovs_vport.yaml | 60 attributes:
71 attributes:
83 attributes:
101 nested-attributes: vport-options
122 nested-attributes: upcall-stats
134 attributes:
148 attributes:
160 attributes:
164 attributes:
|
| D | ovs_flow.yaml | 339 MPLS tunnel attributes.
375 attributes:
379 nested-attributes: key-attrs
381 Nested attributes specifying the flow key. Always present in
386 nested-attributes: action-attrs
388 Nested attributes specifying the actions to take for packets that
393 nested attributes must be given.
426 nested-attributes: key-attrs
428 Nested attributes specifying the mask bits for wildcarded flow
464 attributes:
[all …]
|
| D | handshake.yaml | 34 attributes:
43 attributes:
69 nested-attributes: x509
76 attributes:
101 attributes:
104 attributes:
118 attributes:
|
| D | rt_link.yaml | 727 attributes:
786 nested-attributes: linkinfo-attrs
799 nested-attributes: vfinfo-attrs
807 nested-attributes: vf-ports-attrs
811 nested-attributes: port-self-attrs
815 nested-attributes: af-spec-attrs
867 nested-attributes: xdp-attrs
895 nested-attributes: link-attrs
936 attributes:
941 nested-attributes: ifla-attrs
[all …]
|
| D | rt_route.yaml | 83 attributes:
112 nested-attributes: rta-metrics
182 attributes:
250 attributes:
265 attributes: &all-route-attrs
305 attributes:
309 attributes: *all-route-attrs
318 attributes: *all-route-attrs
327 attributes: *all-route-attrs
|
| D | rt_addr.yaml | 81 attributes:
134 attributes: &ifaddr-all
151 attributes:
166 attributes:
170 attributes: *ifaddr-all
|
| /Documentation/driver-api/driver-model/ |
| D | device.rst | 38 Attributes chapter
51 Attributes of devices can be exported by a device driver through sysfs.
56 As explained in Documentation/core-api/kobject.rst, device attributes must be
60 Attributes are declared using a macro called DEVICE_ATTR::
76 names 'dev_attr_type' and 'dev_attr_power'. These two attributes can be
106 device attributes and the device_unregister() function will use this pointer
107 to remove the device attributes.
111 strict expectations on when attributes get created. When a new device is
113 udev) that a new device is available. If attributes are added after the
115 not know about the new attributes.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-firmware-attributes | 1 What: /sys/class/firmware-attributes/*/attributes/*/
12 Unless otherwise specified in an attribute description all attributes are optional
88 On Dell systems the following additional attributes are available:
111 Enumeration attributes also support the following:
117 dependent attributes value.
137 On HP systems the following additional attributes are available:
149 What: /sys/class/firmware-attributes/*/authentication/
160 reset or cleared using these attributes.
208 setting attributes when a system or admin password is set
229 On Dell, Lenovo and HP systems, if Admin password is set, then all BIOS attributes
[all …]
|
| D | evm | 6 EVM protects a file's security extended attributes(xattrs)
8 HMAC-sha1 value across the extended attributes, storing the
101 Shows the set of extended attributes used to calculate or
102 validate the EVM signature, and allows additional attributes
104 additional attributes are added (and on files possessing those
105 additional attributes) will only be valid if the same
106 additional attributes are configured on system boot. Writing
|
| /Documentation/netlabel/ |
| D | lsm_interface.rst | 12 NetLabel is a mechanism which can set and retrieve security attributes from
18 NetLabel Security Attributes
22 it uses the concept of security attributes to refer to the packet's security
23 labels. The NetLabel security attributes are defined by the
25 NetLabel subsystem converts the security attributes to and from the correct
28 security attributes into whatever security identifiers are in use for their
47 LSM has received a packet, used NetLabel to decode its security attributes,
48 and translated the security attributes into a LSM internal identifier the LSM
|
| /Documentation/userspace-api/netlink/ |
| D | specs.rst | 36 Each next level inherits the attributes of the previous level, meaning that
41 - ``genetlink-c`` - superset of ``genetlink`` with extra attributes allowing
60 - attributes
81 Attributes listed directly at the root level of the spec file.
151 This property contains information about netlink attributes of the family.
159 referred to with a ``nested-attributes`` property of the container.
163 which attributes are allowed in a nest or refining the validation criteria.
170 Uniquely identifies the attribute set, operations and nested attributes
178 or even types of attributes depending on the nest in which they
182 attributes subsection
[all …]
|
| /Documentation/hwmon/ |
| D | mp2888.rst | 39 The driver provides the next attributes for the current:
44 The driver exports the following attributes via the 'sysfs' files, where:
58 The driver provides the next attributes for the voltage:
64 The driver exports the following attributes via the 'sysfs' files, where
84 The driver provides the next attributes for the power:
89 The driver exports the following attributes via the 'sysfs' files, where
107 The driver provides the next attributes for the temperature:
|
| D | mp5023.rst | 33 The driver exports the following attributes via the 'sysfs' files
48 The driver provides the following attributes for output voltage:
56 The driver provides the following attributes for output current:
66 The driver provides the following attributes for input power:
74 The driver provides the following attributes for temperature:
|
| D | hwmon-kernel-api.rst | 48 It creates the standard sysfs attributes in the hardware monitoring core,
50 of having to bother with sysfs attributes. The parent device parameter
139 is optional, but must be provided if any readable attributes exist.
143 optional, but must be provided if any writeable attributes exist.
161 hwmon_chip A virtual sensor type, used to describe attributes
176 describing the attributes supposed by a single sensor.
240 HWMON_C_xxxx Chip attributes, for use with hwmon_chip.
241 HWMON_T_xxxx Temperature attributes, for use with hwmon_temp.
242 HWMON_I_xxxx Voltage attributes, for use with hwmon_in.
243 HWMON_C_xxxx Current attributes, for use with hwmon_curr.
[all …]
|
| D | mp2975.rst | 50 The driver provides the next attributes for the current:
55 attributes.
57 The driver exports the following attributes via the 'sysfs' files, where
73 The driver provides the next attributes for the voltage:
80 The driver exports the following attributes via the 'sysfs' files, where
98 The driver provides the next attributes for the power:
103 The driver exports the following attributes via the 'sysfs' files, where
117 The driver provides the next attributes for the temperature (only from page 0):
|
| /Documentation/filesystems/ext4/ |
| D | attributes.rst | 3 Extended Attributes
6 Extended attributes (xattrs) are typically stored in a separate data
8 The first use of extended attributes seems to have been for storing file
10 option it is possible for users to store extended attributes so long as
14 There are two places where extended attributes can be found. The first
19 where extended attributes can be found is in the block pointed to by
29 Extended attributes, when stored after the inode, have a header
72 - Hash value of all attributes.
92 Attributes stored inside an inode do not need be stored in sorted order.
114 Multiple attributes can share the same value. For an inode attribute
[all …]
|
| /Documentation/power/ |
| D | power_supply_class.rst | 10 It defines core set of attributes, which should be applicable to (almost)
11 every power supply out there. Attributes are available via sysfs and uevent
15 the attributes provided are believed to be universally applicable to any
19 Power supply class is extensible, and allows to define drivers own attributes.
32 Attributes/properties
34 Power supply class has predefined set of attributes, this eliminates code
36 predefined attributes *and* their units.
38 So, userspace gets predictable set of attributes and their units for any
44 and handle attributes.
57 Attributes/properties detailed
[all …]
|
| /Documentation/netlink/ |
| D | genetlink-legacy.yaml | 47 …description: Makes the number of attributes and commands be specified by a define, not an enum val…
148 required: [ name, attributes ]
157 Prefix for the C enum name of the attributes. Default family[name]-set[name]-a-
168 a limited group of attributes which are used in a nest.
172 … description: The explicit name for constant holding the count of attributes (last attr + 1).
178 attributes:
179 description: List of attributes in the space.
207 nested-attributes:
217 form while specific attributes may request to convert the values into a bitfield.
290 genetlink headers and before any attributes.
[all …]
|
| D | genetlink-c.yaml | 47 …description: Makes the number of attributes and commands be specified by a define, not an enum val…
110 required: [ name, attributes ]
119 Prefix for the C enum name of the attributes. Default family[name]-set[name]-a-
130 a limited group of attributes which are used in a nest.
134 … description: The explicit name for constant holding the count of attributes (last attr + 1).
140 attributes:
141 description: List of attributes in the space.
168 nested-attributes:
178 form while specific attributes may request to convert the values into a bitfield.
265 Attribute space from which attributes directly in the requests and replies
[all …]
|
| D | netlink-raw.yaml | 48 …description: Makes the number of attributes and commands be specified by a define, not an enum val…
139 form while specific attributes may request to convert the values into a bitfield.
155 required: [ name, attributes ]
164 Prefix for the C enum name of the attributes. Default family[name]-set[name]-a-
175 a limited group of attributes which are used in a nest.
179 … description: The explicit name for constant holding the count of attributes (last attr + 1).
185 attributes:
186 description: List of attributes in the space.
214 nested-attributes:
224 form while specific attributes may request to convert the values into a bitfield.
[all …]
|
| D | genetlink.yaml | 91 required: [ name, attributes ]
100 Prefix for the C enum name of the attributes. Default family[name]-set[name]-a-
111 a limited group of attributes which are used in a nest.
113 attributes:
114 description: List of attributes in the space.
141 nested-attributes:
151 form while specific attributes may request to convert the values into a bitfield.
234 Attribute space from which attributes directly in the requests and replies
257 attributes:
259 Names of attributes from the attribute-set (not full attribute
[all …]
|
| /Documentation/driver-api/iio/ |
| D | core.rst | 52 Attributes are sysfs files used to expose chip info and also allowing
54 index X, attributes can be found under /sys/bus/iio/iio:deviceX/ directory.
55 Common attributes are:
62 * Available standard attributes for IIO devices are described in the
91 Channel sysfs attributes exposed to userspace are specified in the form of
92 bitmasks. Depending on their shared info, attributes can be set in one of the
95 * **info_mask_separate**, attributes will be specific to
97 * **info_mask_shared_by_type**, attributes are shared by all channels of the
99 * **info_mask_shared_by_dir**, attributes are shared by all channels of the same
101 * **info_mask_shared_by_all**, attributes are shared by all channels
[all …]
|
| /Documentation/admin-guide/mm/ |
| D | numaperf.rst | 70 the system provides these attributes, the kernel exports them under the
71 node sysfs hierarchy by appending the attributes directory under the
76 These attributes apply only when accessed from nodes that have the
89 The bandwidth attributes are provided in MiB/second.
91 The latency attributes are provided in nanoseconds.
127 An application does not need to know about caching attributes in order
129 attributes in order to maximize the performance out of such a setup.
132 the kernel will append these attributes to the NUMA node memory target.
142 The attributes for each level of cache is provided under its cache
149 Each cache level's directory provides its attributes. For example, the
[all …]
|