Searched full:provided (Results 1 – 25 of 902) sorted by relevance
12345678910>>...37
| /Documentation/devicetree/bindings/clock/ |
| D | mvebu-core-clock.txt | 7 The following is a list of provided IDs and clock names on Armada 370/XP:
14 The following is a list of provided IDs and clock names on Armada 375:
20 The following is a list of provided IDs and clock names on Armada 380/385:
26 The following is a list of provided IDs and clock names on Armada 39x:
34 The following is a list of provided IDs and clock names on 98dx3236:
40 The following is a list of provided IDs and clock names on Kirkwood and Dove:
46 The following is a list of provided IDs and clock names on Orion5x:
|
| D | mvebu-gated-clock.txt | 10 The following is a list of provided IDs for Armada 370:
27 The following is a list of provided IDs for Armada 375:
54 The following is a list of provided IDs for Armada 380/385:
81 The following is a list of provided IDs for Armada 39x:
95 The following is a list of provided IDs for Armada XP:
122 The following is a list of provided IDs for 98dx3236:
132 The following is a list of provided IDs for Dove:
155 The following is a list of provided IDs for Kirkwood:
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-input-exc3000 | 4 Description: Reports the firmware version provided by the touchscreen, for example "00_T6" on a …
13 Description: Reports the model identification provided by the touchscreen, for example "Orion_13…
22 Description: Reports the type identification provided by the touchscreen, for example "PCAP82H80 Se…
|
| D | sysfs-secvar | 21 On powernv/OPAL, this value is provided by the OPAL firmware
71 Currently only provided by PLPKS on the pseries platform.
84 Currently only provided by PLPKS on the pseries platform.
92 Currently only provided by PLPKS on the pseries platform.
100 Currently only provided by PLPKS on the pseries platform.
109 Currently only provided by PLPKS on the pseries platform.
119 Currently only provided by PLPKS on the pseries platform.
|
| D | sysfs-bus-event_source-devices-hv_24x7 | 24 this value will be provided by user while running this event.
30 Provides access to the binary "24x7 catalog" provided by the
41 also extractable from the provided binary "catalog" sysfs entry.
48 extractable from the provided binary "catalog" sysfs entry.
82 Provides the description of a particular event as provided by
94 provided by the firmware. If firmware does not provide a
|
| D | sysfs-class-rtc | 21 (RO) RTC-provided date in YYYY-MM-DD format
28 (RO) 1 if the RTC provided the system time at boot via the
59 (RO) RTC-provided time as the number of seconds since the epoch
66 (RO) RTC-provided time in 24-hour notation (hh:mm:ss)
|
| D | sysfs-platform-mellanox-bootctl | 95 provided on a board-level label.
103 This value is provided on a board-level label.
111 This value is provided on a board-level label.
119 This value is provided on a board-level label.
127 This value is provided on a board-level label.
135 This value is provided by the manufacturing team.
143 This value is provided on a board-level label.
|
| D | sysfs-firmware-memmap | 10 However, on most architectures that firmware-provided memory
16 kexec needs the raw firmware-provided memory map to setup the
31 The maximum depends on the number of memory map entries provided
|
| /Documentation/devicetree/bindings/phy/ |
| D | qcom,usb-snps-femto-v2.yaml | 68 provided input will be chosen as the override value for this param.
77 provided input will be chosen as the override value for this param.
85 provided input will be chosen as the override value for this param.
97 provided input will be chosen as the override value for this param.
109 provided input will be chosen as the override value for this param.
117 provided input will be chosen as the override value for this param.
126 provided input will be chosen as the override value for this param.
136 value closest to the provided input will be chosen as the override value
147 provided input will be chosen as the override value for this param.
|
| D | transmit-amplitude.yaml | 21 'tx-p2p-microvolt-names' property must be provided and contain
27 property. Required only if multiple voltages are provided.
29 If a value of 'default' is provided, the system should use it for any PHY
30 mode that is otherwise not defined here. If 'default' is not provided, the
|
| /Documentation/driver-api/ |
| D | vme.rst | 12 be provided to the registration function. Along with the maximum number of
43 A function is also provided to unregister the driver from the VME core called
51 Once a driver has registered with the VME core the provided match routine will
73 transfers to be provided in the route attributes. This is typically VME-to-MEM
78 Functions are also provided to free window allocations once they are no longer
81 provided during resource allocation.
108 In addition to simple reads and writes, :c:func:`vme_master_rmw` is provided to
136 Functions are provided to allow the user to allocate
163 The function :c:func:`vme_new_dma_list` is provided to create and
222 pointer parameter is provided, the value of which is passed to the callback
[all …]
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | qcom,qfprom.yaml | 48 # needs to be provided. If the QFPROM is writable then all 4 regions
49 # must be provided.
59 # Clock must be provided if QFPROM is writable from the OS image.
65 # Supply reference must be provided if QFPROM is writable from the OS image.
|
| /Documentation/devicetree/bindings/firmware/ |
| D | fsl,scu.yaml | 40 OCOTP controller node provided by the SCU
45 Keys provided by the SCU
118 Pin controller provided by the SCU
129 RTC controller provided by the SCU
134 Thermal sensor provided by the SCU
139 Watchdog controller provided by the SCU
|
| /Documentation/devicetree/bindings/power/ |
| D | power-domain.yaml | 20 their PM domains provided by PM domain providers. A PM domain provider can be
47 Phandles to the OPP tables of power domains provided by a power domain
49 the power domains provided by the provider have identical OPP tables,
66 consumer binding is used. When provided, all domains created
102 // domain provided by the 'parent' power controller.
|
| /Documentation/admin-guide/mm/ |
| D | numaperf.rst | 16 are provided as memory only nodes. While memory only nodes do not provide
89 The bandwidth attributes are provided in MiB/second.
91 The latency attributes are provided in nanoseconds.
105 system physical addresses memory initiators are aware of are provided
113 cache provided by the system.
142 The attributes for each level of cache is provided under its cache
167 The "size" is the number of bytes provided by this cache level.
|
| /Documentation/scsi/ |
| D | LICENSE.FlashPoint | 29 modification, are permitted provided that the following conditions are
44 documentation and/or other materials provided with the distribution.
50 THIS SOFTWARE IS PROVIDED BY MYLEX CORP. ``AS IS'' AND ANY EXPRESS OR
|
| /Documentation/virt/coco/ |
| D | sev-guest.rst | 23 from the SEV firmware. For each ioctl, the following information is provided
80 provided by the SEV-SNP firmware to query the attestation report.
97 The ioctl uses the SNP_GUEST_REQUEST (MSG_KEY_REQ) command provided by the
114 The certificate data returned is being provided by the hypervisor through the
117 The ioctl uses the SNP_GUEST_REQUEST (MSG_REPORT_REQ) command provided by the SEV-SNP
142 a non-CPUID encrypted page will change the measurement provided by the
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci-msi.txt | 79 * The sideband data provided to the MSI controller is
107 * The sideband data provided to the MSI controller is
136 * The sideband data provided to the MSI controller is
166 * The sideband data provided to the MSI controller is
210 * The sideband data provided to MSI controller a is the
212 * The sideband data provided to MSI controller b is the
|
| /Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 6 to use the distro-provided policies, or install the
12 testing, you can do using ``mdp`` provided under
|
| /Documentation/driver-api/surface_aggregator/ |
| D | client.rst | 45 are non-discoverable and instead need to be explicitly provided by some
93 If a device does not already exist/is not already provided via conventional
94 means, it should be provided as |ssam_device| via the SSAM client device
99 default, the parent of the device is set to the controller device provided
103 setup provided through the parent-child relation, are preserved. If
170 EC is provided in little-endian format and, similarly, any response payload
256 said function. In this example, the argument is provided via the ``arg``
258 the stack. Thus, if the argument provided via the request is large, these
263 provided in the non-macro example above.
275 these macros, a special variant is provided, which targets request types
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | as3711.txt | 13 be provided:
18 be provided:
22 Additionally one of these properties must be provided to select the type of
|
| /Documentation/arch/arm/ |
| D | firmware.rst | 21 There is a default, empty set of operations provided, so there is no need to
24 To call a firmware operation, a helper macro is provided::
29 the macro checks if the operation is provided and calls it or otherwise returns
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-peripheral-props.yaml | 65 If 0 is provided, then no RX will be possible on this device.
82 If 0 is provided, then no TX will be possible on this device.
98 each chip should be provided as members of the array.
111 be provided as members of the array.
|
| /Documentation/core-api/ |
| D | debug-objects.rst | 31 the object type. Optional functions can and should be provided to fixup
37 The debug calls provided by debugobjects are:
77 structure if provided by the caller. The fixup function can correct the
100 structure if provided by the caller. The fixup function can correct the
124 structure if provided by the caller. The fixup function can correct the
164 provided by the caller. The fixup function can correct the problem
179 the object type description structure if provided by the caller. The
194 fixup_assert_init of the object type description structure provided by
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 48 There are several different mechanisms provided for communicating between VMs.
58 directly provided by the hypervisor as well as core virtual platform devices
75 Services/resources provided by the Gunyah hypervisor are accessible to a
89 Capability IDs is provided by RM as a higher level service to VMs.
130 manager. This is provided to VMs via a 'hypervisor' device tree node which is
|
12345678910>>...37