From: Bryan O'Donoghue <pure.logic@nexus-software.ie>
To: Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ckadabi@codeaurora.org,
tsoni@codeaurora.org, bryanh@codeaurora.org,
psodagud@codeaurora.org, rnayak@codeaurora.org,
satyap@codeaurora.org, pheragu@codeaurora.org
Subject: Re: [PATCH v4 1/2] dt-bindings: Documentation for qcom,eud
Date: Tue, 4 Feb 2020 02:51:31 +0000 [thread overview]
Message-ID: <9483dfa0-15ea-e9ed-79ee-3dcf97e98136@nexus-software.ie> (raw)
In-Reply-To: <1580445811-15948-2-git-send-email-akdwived@codeaurora.org>
On 31/01/2020 04:43, Avaneesh Kumar Dwivedi wrote:
> Documentation for Embedded USB Debugger (EUD) device tree bindings.
>
> Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
> Signed-off-by: Prakruthi Deepak Heragu <pheragu@codeaurora.org>
> Signed-off-by: Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
> ---
> .../devicetree/bindings/soc/qcom/qcom,msm-eud.txt | 43 ++++++++++++++++++++++
> 1 file changed, 43 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/qcom/qcom,msm-eud.txt
>
> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,msm-eud.txt b/Documentation/devicetree/bindings/soc/qcom/qcom,msm-eud.txt
> new file mode 100644
> index 0000000..57476ce
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,msm-eud.txt
> @@ -0,0 +1,43 @@
> +* Qualcomm Technologies Inc Embedded USB Debugger (EUD)
> +
> +The EUD (Embedded USB Debugger) is a mini-USB hub implemented
> +on chip to support the USB-based debug and trace capabilities.
on chip to support USB-based debug and trace capabilities.
> +
> +Required properties:
> +
> + - compatible: Should be "qcom,msm-eud"
> + - interrupts: Interrupt number
> + - reg: Should be address and size of EUD register space
> +
> +EUD notifies clients for VBUS attach/detach and charger enable/disable
> +events. The link between event consumer(i.e.USB controller for vbus
missing space
consumer (i.e.
> +attach/detach event) and EUD is established via a directed graph. EUD
> +act
The EUD acts
> as an output link and clients of EUD as input link of this directed
> +graph. Events flows through the directed graph only during debug mode.
Probably this is a very obvious question but, you mean debug and trace
events or do you mean VBUS/charger events?
> +
> +An example for EUD device node:
> +
> + eud: qcom,msm-eud@88e0000 {
> + compatible = "qcom,msm-eud";
> + interrupts = <GIC_SPI 492 IRQ_TYPE_LEVEL_HIGH>;
> + reg = <0x88e0000 0x4000>;
> + usb_con: connector {
> + compatible = "usb-c-connector";
> + label = "USB-C";
> + port {
> + eud_usb_output: endpoint {
> + remote-endpoint = <&eud_usb3_input>;
> + };
> + };
> + };
> + };
> +
> +An example for EUD client:
> +
> + usb3 {
> + port {
> + eud_usb3_input: endpoint {
> + remote-endpoint = <&eud_usb_output>;
> + };
> + };
> + };
>
next prev parent reply other threads:[~2020-02-04 2:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 4:43 [PATCH v4 0/2] Add Embedded USB Debugger (EUD) driver Avaneesh Kumar Dwivedi
2020-01-31 4:43 ` [PATCH v4 1/2] dt-bindings: Documentation for qcom,eud Avaneesh Kumar Dwivedi
2020-02-04 2:51 ` Bryan O'Donoghue [this message]
2020-02-16 13:11 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-04 3:17 ` Bryan O'Donoghue
2020-02-16 13:14 ` Dwivedi, Avaneesh Kumar (avani)
2020-01-31 4:43 ` [PATCH v4 2/2] Embedded USB Debugger (EUD) driver Avaneesh Kumar Dwivedi
2020-02-03 19:35 ` Bjorn Andersson
2020-02-04 3:10 ` Bryan O'Donoghue
2020-02-16 16:07 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-17 19:44 ` Bryan O'Donoghue
2020-02-18 13:23 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-18 14:48 ` Bryan O'Donoghue
2020-04-04 14:12 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-16 14:14 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-18 3:35 ` Bjorn Andersson
2020-02-18 13:00 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-07 10:04 ` Greg KH
2020-02-16 16:22 ` Dwivedi, Avaneesh Kumar (avani)
2020-02-16 16:35 ` Greg KH
2020-02-17 7:21 ` Dwivedi, Avaneesh Kumar (avani)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9483dfa0-15ea-e9ed-79ee-3dcf97e98136@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=akdwived@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=ckadabi@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pheragu@codeaurora.org \
--cc=psodagud@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=satyap@codeaurora.org \
--cc=tsoni@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®