Searched full:form (Results 1 – 25 of 385) sorted by relevance
12345678910>>...16
| /Documentation/arch/powerpc/ |
| D | associativity.rst | 14 grouping details to the OS. These are referred to as Form 0, Form 1 and Form2
15 associativity grouping. Form 0 is the oldest format and is now considered deprecated.
17 Hypervisor indicates the type/form of associativity used via "ibm,architecture-vec-5 property".
18 Bit 0 of byte 5 in the "ibm,architecture-vec-5" property indicates usage of Form 0 or Form 1.
19 A value of 1 indicates the usage of Form 1 associativity. For Form 2 associativity
22 Form 0
24 Form 0 associativity supports only two NUMA distances (LOCAL and REMOTE).
26 Form 1
28 With Form 1 a combination of ibm,associativity-reference-points, and ibm,associativity
47 Form 2
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-powernv.txt | 9 form of a sub-node.
13 in the form of string array.
|
| /Documentation/w1/slaves/ |
| D | w1_ds2406.rst | 16 not supported. In TSOC-6 form, the DS2406 provides two switch outputs and
17 can be provided with power on a dedicated input. In TO-92 form, it provides
|
| /Documentation/networking/ |
| D | ipsec.rst | 22 form. To clarify: If an IP datagram is sent non-compressed, no
32 original form without attempting compression. The numeric threshold
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,integrator.yaml | 28 pre-packaged in a PC Tower form factor called Integrator/PP1 or a
33 a compact form factor and mainly consists of the bare minimum
|
| D | microchip,sparx5.yaml | 34 - description: The Sparx5 pcb134 is a pizzabox form factor
41 - description: The Sparx5 pcb135 is a pizzabox form factor
|
| D | primecell.yaml | 24 in the form "arm,pl???"
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller-model.rst | 38 entities form a single logical unit. For example this could represent the
39 fact that a particular camera sensor and lens controller form a single
|
| /Documentation/ABI/stable/ |
| D | thermal-notification | 4 The notification is in the form of a netlink event.
|
| /Documentation/devicetree/bindings/memory-controllers/ddr/ |
| D | jedec,lpddr-props.yaml | 22 (e.g. elpida,ECB240ABACN), or generated strings of the form
26 The latter form can be useful when LPDDR nodes are created at runtime by
|
| /Documentation/hwmon/ |
| D | ibm-cffps.rst | 6 * IBM Common Form Factor power supply
13 This driver supports IBM Common Form Factor (CFF) power supplies. This driver
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpic-msgr.txt | 10 block. The type shall be <string-list> and the value shall be of the form
36 may require aliases to be present. Aliases are of the form
|
| /Documentation/ABI/testing/ |
| D | sysfs-pps | 22 and the assert sequence number of the X-th source in the form:
34 and the clear sequence number of the X-th source in the form:
|
| D | sysfs-devices-supplier | 7 name of the supplier in that device link and is of the form
|
| D | sysfs-devices-consumer | 7 name of the consumer in that device link and is of the form
|
| D | sysfs-kernel-mm-hugepages | 6 of the form hugepages-<size>kB, where <size> is the page size
|
| D | sysfs-kernel-mm-transparent-hugepage | 14 - subdirectories of the form hugepages-<size>kB, where <size>
|
| D | sysfs-dev | 9 the form "<major>:<minor>". These links point to the
|
| /Documentation/security/keys/ |
| D | ecryptfs.rst | 31 encrypted form.
37 threats of malicious software, because it is available in clear form only at
|
| /Documentation/devicetree/bindings/pci/ |
| D | fsl,pci.txt | 4 is prevented from enumerating the bus. The PrPMC form-factor requires
|
| /Documentation/devicetree/bindings/media/ |
| D | st,stih4xx.txt | 25 Each BDISP should have a numbered alias in the aliases node, in the form of
|
| /Documentation/mm/ |
| D | page_owner.rst | 166 order. Mixed use of abbreviated and complete-form of keys is allowed.
179 <rules> is a single argument in the form of a comma-separated list,
184 complete-form of keys is allowed.
202 <pidlist>, <tgidlist>, <cmdlist> are single arguments in the form of a comma-separated list,
|
| /Documentation/pcmcia/ |
| D | driver.rst | 24 and the card ID (form the manf_id and card_id file in the device tree).
|
| /Documentation/security/ |
| D | ipe.rst | 40 there must be some form of selector to determine whether a read should
154 the policy has to be some form of string representation (be it structured,
157 is necessary to write the policy from the human readable form, to the binary
158 form, and a deserializer is needed to interpret the binary form into a data
162 back into the human-readable form with as much information preserved. This is because a
175 human-readable form to the data structure in kernel, saving on code maintenance,
|
| /Documentation/devicetree/bindings/net/ |
| D | sff,sfp.yaml | 7 title: Small Form Factor (SFF) Committee Small Form-factor Pluggable (SFP)
|
12345678910>>...16