Searched full:eud (Results 1 – 7 of 7) sorted by relevance
| /linux-6.12.1/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,eud.yaml | 4 $id: http://devicetree.org/schemas/soc/qcom/qcom,eud.yaml#
20 - qcom,sc7280-eud
21 - const: qcom,eud
25 - description: EUD Base Register Region
26 - description: EUD Mode Manager Register
29 description: EUD interrupt
57 eud@88e0000 {
58 compatible = "qcom,sc7280-eud", "qcom,eud";
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-driver-eud | 6 USB Debugger(EUD). This enables and disables the
7 EUD based on a 1 or a 0 value. By enabling EUD,
9 EUD for debug and trace capabilities.
|
| /linux-6.12.1/drivers/usb/misc/ |
| D | qcom_eud.c | 98 ATTRIBUTE_GROUPS(eud);
115 * disconnected and we need to detach the pet to check if EUD is in safe in pet_eud()
120 /* Detach & Attach pet for EUD */ in pet_eud()
130 /* Attach pet for EUD */ in pet_eud()
235 { .compatible = "qcom,eud" },
251 MODULE_DESCRIPTION("QTI EUD driver");
|
| D | Kconfig | 148 tristate "QCOM Embedded USB Debugger(EUD) Driver"
153 Embedded USB Debugger (EUD). The EUD is a control peripheral
|
| /linux-6.12.1/Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-dummy-sink.yaml | 18 kernel don't have permission to access or configure, e.g., CoreSight EUD on
22 created in the driver. Then the trace flow would be transferred to EUD via
48 dummy sink, such as Embedded USB debugger(EUD).
|
| /linux-6.12.1/arch/arm64/boot/dts/qcom/ |
| D | sc7280.dtsi | 4020 eud: eud@88e0000 { label
4021 compatible = "qcom,sc7280-eud", "qcom,eud";
|
| /linux-6.12.1/ |
| D | MAINTAINERS | 18763 QCOM EMBEDDED USB DEBUGGER (EUD)
18767 F: Documentation/ABI/testing/sysfs-driver-eud
18768 F: Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
|