···11-Analog Device ADV7123 Video DAC22--------------------------------11+Analog Devices ADV7123 Video DAC22+--------------------------------3344The ADV7123 is a digital-to-analog converter that outputs VGA signals from a55parallel video input.
···11-Analog Device ADV7511(W)/13/33/35 HDMI Encoders22------------------------------------------11+Analog Devices ADV7511(W)/13/33/35 HDMI Encoders22+------------------------------------------------3344The ADV7511, ADV7511W, ADV7513, ADV7533 and ADV7535 are HDMI audio and video55transmitters compatible with HDMI 1.4 and DVI 1.0. They support color space
···11-* Analog Device AD5755 IIO Multi-Channel DAC Linux Driver11+* Analog Devices AD5755 IIO Multi-Channel DAC Linux Driver2233Required properties:44 - compatible: Has to contain one of the following:
···29293030Optional properties for compatible string qcom,wcn399x-bt:31313232- - max-speed: see Documentation/devicetree/bindings/serial/slave-device.txt3232+ - max-speed: see Documentation/devicetree/bindings/serial/serial.yaml3333 - firmware-name: specify the name of nvm firmware to load3434 - clocks: clock provided to the controller3535
···5252the node is not important. The content of the node is defined in dwc3.txt.53535454Phy documentation is provided in the following places:5555-Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt - USB3 QMP PHY5656-Documentation/devicetree/bindings/phy/qcom-qusb2-phy.txt - USB2 QUSB2 PHY5555+Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt - USB3 QMP PHY5656+Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml - USB2 QUSB2 PHY57575858Example device nodes:5959
···1616the node is not important. The content of the node is defined in dwc3.txt.17171818Phy documentation is provided in the following places:1919-Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt - USB2.0 PHY1919+Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.yaml - USB2.0 PHY2020Documentation/devicetree/bindings/phy/phy-rockchip-typec.txt - Type-C PHY21212222Example device nodes:
···33/plugin/;4455/*66- * &electric_1/motor-1 and &spin_ctrl_1 are the same node:77- * /testcase-data-2/substation@100/motor-166+ * &electric_1/motor-1/electric and &spin_ctrl_1/electric are the same node:77+ * /testcase-data-2/substation@100/motor-1/electric88 *99 * Thus the property "rpm_avail" in each fragment will1010 * result in an attempt to update the same property twice.1111 * This will result in an error and the overlay apply1212 * will fail.1313+ *1414+ * The previous version of this test did not include the extra1515+ * level of node 'electric'. That resulted in the 'rpm_avail'1616+ * property being located in the pre-existing node 'motor-1'.1717+ * Modifying a property results in a WARNING that a memory leak1818+ * will occur if the overlay is removed. Since the overlay apply1919+ * fails, the memory leak does actually occur, and kmemleak will2020+ * further report the memory leak if CONFIG_DEBUG_KMEMLEAK is2121+ * enabled. Adding the overlay node 'electric' avoids the2222+ * memory leak and thus people who use kmemleak will not2323+ * have to debug this non-problem again.1324 */14251526&electric_1 {16271728 motor-1 {1818- rpm_avail = < 100 >;2929+ electric {3030+ rpm_avail = < 100 >;3131+ };1932 };2033};21342235&spin_ctrl_1 {2323- rpm_avail = < 100 200 >;3636+ electric {3737+ rpm_avail = < 100 200 >;3838+ };2439};