From: pheragu@codeaurora.org
To: Rob Herring <robh@kernel.org>
Cc: linux-arm-msm@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tsoni@codeaurora.org, ckadabi@codeaurora.org,
bryanh@codeaurora.org, psodagud@codeaurora.org,
satyap@codeaurora.org
Subject: Re: [PATCH 1/2] dt-bindings: Documentation for qcom,eud
Date: Thu, 02 Aug 2018 11:44:50 -0700 [thread overview]
Message-ID: <4d6732e9172431bbf24ff470be345481@codeaurora.org> (raw)
In-Reply-To: <CABGGiswcMicPypOz2eW01NosuAHUw2B3KVxzrOfanEfT=Srf9A@mail.gmail.com>
On 2018-08-01 07:04, Rob Herring wrote:
> On Tue, Jul 31, 2018 at 12:22 PM Prakruthi Deepak Heragu
> <pheragu@codeaurora.org> wrote:
>>
>> Documentation for Embedded USB Debugger (EUD) device tree bindings.
>
> If you want bindings reviewed, send them to the correct list and
> people (hint: run get_maintainers.pl).
>
> New bindings should not use extcon.
>
Why should we not use extcon? Are there any alternatives which you
would suggest? We were looking at graphs instead of extcon.
>>
>> Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
>> Signed-off-by: Prakruthi Deepak Heragu <pheragu@codeaurora.org>
>> ---
>> .../devicetree/bindings/soc/qcom/qcom,msm-eud.txt | 28
>> ++++++++++++++++++++++
>> 1 file changed, 28 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..ea63f1c
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,msm-eud.txt
>> @@ -0,0 +1,28 @@
>> +* 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.
>> +
>> +Required properties:
>> +
>> + - compatible: Should be "qcom,msm-eud"
>> + - interrupts: Interrupt number
>> + - reg: Should be address and size of EUD register space
>> +
>> +Driver notifies clients via extcon for VBUS attach/detach
>> +and charger enable/disable events. Clients registered for these
>> +notifications should have extcon property set to eud.
>> +
>> +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>;
>> + };
>> +
>> +An example for EUD extcon client:
>> +
>> + usb3 {
>> + extcon = <&eud>;
>> + };
>> --
>> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
>> Forum,
>> a Linux Foundation Collaborative Project
>>
next prev parent reply other threads:[~2018-08-02 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 18:22 [PATCH 0/2] Add Embedded USB Debugger (EUD) driver Prakruthi Deepak Heragu
2018-07-31 18:22 ` [PATCH 1/2] dt-bindings: Documentation for qcom,eud Prakruthi Deepak Heragu
2018-08-01 14:04 ` Rob Herring
2018-08-02 18:44 ` pheragu [this message]
2018-08-02 21:23 ` Rob Herring
2018-07-31 18:22 ` [PATCH 2/2] Embedded USB Debugger (EUD) driver Prakruthi Deepak Heragu
2018-07-31 19:29 ` Trilok Soni
2018-07-31 19:32 ` pheragu
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=4d6732e9172431bbf24ff470be345481@codeaurora.org \
--to=pheragu@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=ckadabi@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psodagud@codeaurora.org \
--cc=robh@kernel.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