| /Documentation/devicetree/bindings/usb/ |
| D | usb-xhci.yaml | 16 usb2-lpm-disable:
17 description: Indicates if we don't want to enable USB2 HW LPM
20 usb3-lpm-capable:
21 description: Determines if platform is USB3 LPM capable
46 usb2-lpm-disable;
47 usb3-lpm-capable;
|
| D | hisilicon,histb-xhci.txt | 26 - usb2-lpm-disable: indicate if we don't want to enable USB2 HW LPM
27 - usb3-lpm-capable: determines if platform is USB3 LPM capable
|
| D | snps,dwc3.yaml | 112 snps,usb2-lpm-disable:
113 description: Indicate if we don't want to enable USB2 HW LPM for host
118 description: Determines if platform is USB3 LPM capable
121 snps,usb2-gadget-lpm-disable:
122 description: Indicate if we don't want to enable USB2 HW LPM for gadget
138 snps,has-lpm-erratum:
139 description: True when DWC3 was configured with LPM Erratum enabled
142 snps,lpm-nyet-threshold:
143 description: LPM NYET threshold
257 snps,gfladj-refclk-lpm-sel-quirk:
|
| D | ti,j721e-usb.yaml | 40 - const: lpm
90 clock-names = "ref", "lpm";
|
| D | fsl,imx8qm-cdns3.yaml | 39 - const: lpm
81 clock-names = "lpm", "bus", "aclk", "ipg", "core";
|
| D | starfive,jh7110-usb.yaml | 47 - const: lpm
97 clock-names = "lpm", "stb", "apb", "axi", "utmi_apb";
|
| D | mediatek,mtk-xhci.yaml | 118 usb3-lpm-capable: true
120 usb2-lpm-disable: true
225 usb3-lpm-capable;
|
| /Documentation/bpf/ |
| D | map_lpm_trie.rst | 18 LPM tries may be created with a maximum prefix length that is a multiple
26 The value type stored in the LPM trie can be any user defined type.
96 A userspace program can iterate through the entries in an LPM trie using
104 ``bpf_map_get_next_key()`` will iterate through the LPM trie elements
112 of LPM trie usage from userspace. The code snippets below demonstrate
118 The following BPF code snippet shows how to declare a new LPM trie for IPv4
157 LPM trie:
171 of an LPM trie:
|
| /Documentation/networking/devlink/ |
| D | devlink-dpipe.rst | 15 For example, the routing longest prefix match (LPM) algorithm used by the
31 One example is the kernel's LPM algorithm which in many cases differs
127 LPM are not supported due to the fact that this is exactly a process we wish
166 LPM section in Abstraction Example
169 The LPM algorithm can be implemented as a list of hash tables. Each hash
177 The ``meta.lpm_prefix`` field is used to connect two LPM tables.
197 In the case of local routes the LPM lookup already resolves the egress
215 In case of remote routes this table does the ECMP. The LPM lookup results in
218 and the packet's hash a local offset is generated. Multiple LPM entries can
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-usb | 97 If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged
98 in to a xHCI host which support link PM, it will perform a LPM
99 test; if the test is passed and host supports USB2 hardware LPM
100 (xHCI 1.0 feature), USB2 hardware LPM will be enabled for the
103 or disable) indicating whether or not USB2 hardware LPM is
113 If CONFIG_PM is set and a USB 3.0 lpm-capable device is plugged
116 the check is passed and the host supports USB3 hardware LPM,
117 USB3 hardware LPM will be enabled for the device and the USB
121 or not USB3 hardware LPM U1 or U2 is enabled for the device.
223 Some USB3.0 devices are not friendly to USB3 LPM. usb3_lpm_permit
[all …]
|
| D | devlink-resource-mlxsw | 7 the chip including L2 FDB, L3 LPM, ECMP and more. The KVD
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 76 [ 1815.999595] usb 4-3: LPM exit latency is zeroed, disabling LPM.
144 [ 79.475003] usb 2-2.1: LPM exit latency is zeroed, disabling LPM.
|
| D | power-management.rst | 529 enabling hardware LPM, the host can automatically put the device into
533 The user interface for controlling hardware LPM is located in the
540 When a USB2 device which support LPM is plugged to a
541 xHCI host root hub which support software LPM, the
542 host will run a software LPM test for it; if the device
544 supports USB2 hardware LPM, this file will show up and
545 driver will enable hardware LPM for the device. You
547 USB2 hardware LPM manually. This is for test purpose mainly.
552 When a USB 3.0 lpm-capable device is plugged in to a
556 supports USB3 hardware LPM, USB3 hardware LPM will be
[all …]
|
| /Documentation/devicetree/bindings/soc/sti/ |
| D | st,sti-syscon.yaml | 24 - st,stih407-lpm-syscfg
|
| /Documentation/devicetree/bindings/regulator/ |
| D | microchip,mcp16502.yaml | 22 lpm-gpios:
24 description: GPIO for LPM pin.
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | hdmi.yaml | 79 qcom,hdmi-tx-mux-lpm-gpios:
82 description: HDMI mux lpm pin
|
| /Documentation/devicetree/bindings/sound/ |
| D | qcom,lpass-cpu.yaml | 223 - const: lpass-rxtx-cdc-dma-lpm
226 - const: lpass-va-cdc-dma-lpm
|
| /Documentation/arch/s390/ |
| D | cds.rst | 209 __u8 lpm,
214 __u8 lpm,
220 __u8 lpm,
226 __u8 lpm,
238 lpm defines the channel path to be used for a specific I/O
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-max77620.txt | 38 gpio, lpm-control-in, fps-out, 32k-out, sd0-dvs-in, sd1-dvs-in,
|
| /Documentation/devicetree/bindings/net/ |
| D | microchip,sparx5-switch.yaml | 21 with up to 18K IPv4/9K IPv6 unicast LPM entries and up to 9K IPv4/3K
|
| /Documentation/networking/ |
| D | switchdev.rst | 346 does a longest prefix match (LPM) on FIB entries matching route prefix and
|
| /Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 697 LPM. The soft lockup timeout is not impacted.
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 3083 * [no]lpm: Enable or disable link power management.
|