From: George Cherian <george.cherian@ti.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: balbi@ti.com, myungjoo.ham@samsung.com, cw00.choi@samsung.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, grant.likely@linaro.org,
rob@landley.net, ian.campbell@citrix.com, mark.rutland@arm.com,
pawel.moll@arm.com, rob.herring@calxeda.com,
linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
bcousson@baylibre.com
Subject: Re: [PATCH 1/2] extcon: extcon-dra7xx: Add extcon driver for USB ID detection
Date: Tue, 20 Aug 2013 12:25:08 +0530 [thread overview]
Message-ID: <521312CC.8060003@ti.com> (raw)
In-Reply-To: <52127284.6030506@wwwdotorg.org>
Hi Stephen,
Thanks for your review.
On 8/20/2013 1:01 AM, Stephen Warren wrote:
> On 08/16/2013 04:13 AM, George Cherian wrote:
>> Adding extcon driver for USB ID detection to dynamically
>> configure USB Host/Peripheral mode.
>> diff --git a/Documentation/devicetree/bindings/extcon/extcon-dra7xx.txt b/Documentation/devicetree/bindings/extcon/extcon-dra7xx.txt
>> +EXTCON FOR DRA7xx
>> +
>> +Required Properties:
> Please at lest explain what a DRA7xxx is, and the purpose of the HW
> module this binding describes.
DRA7xx is the SoC name and the USB VID detection is implemented via gpio's
Basically it does only ID detection via GPIO and there is no VBUS
detection in h/w.
>
>> + - compatible : Should be "ti,dra7xx-usb"
> If this is a USB VID detector rather than a full USB host controller,
> then "usb" in the binding is a bit over-reaching. Perhaps "-usb-vid" or
> "-usb-vid-detector" would be more accurate.
This will be renamed to dra7xx-extcon.
>
>> + - gpios : phandle to ID pin and interrupt gpio.
> This isn't just a phandle; it's phandle+args, or a GPIO specifier. Some
> reference should be made to ../gpio/gpio.txt for the format.
okay
> Why does the interrupt line need to be included in a list of GPIOs?
ID pins are connected to pcf8575, and the pcf8575's interrupt line is
inturn connected to
gpio bank6 pin 11, we use this gpio interrupt to detect the ID pin change.
> If the DRA7xxx is a VID detector, why does it even need/have any GPIOs
> associated with it; surely it has a dedicated VID input pin. Can you
> provide more details re: how the HW is structured.
>
>> +Optional Properties:
>> + - interrupt-parent : interrupt controller phandle
>> + - interrupts : interrupt number
>> +
>> +
> It's typical insert the following between those two blank lines:
>
> Example:
>
> ... or delete one of the blank lines.
>
>> +dra7x_extcon1 {
>> + compatible = "ti,dra7xx-usb";
>> + gpios = <&pcf_usb 1 0>,
>> + <&gpio6 11 2>;
>> + interrupt-parent = <&gpio6>;
>> + interrupts = <11>;
>> + };
>> +
> No need for that trailing blank line.
okay
>
--
-George
next prev parent reply other threads:[~2013-08-20 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1376648029-30659-1-git-send-email-george.cherian@ti.com>
[not found] ` <1376648029-30659-2-git-send-email-george.cherian@ti.com>
2013-08-19 19:31 ` [PATCH 1/2] extcon: extcon-dra7xx: Add extcon driver for USB ID detection Stephen Warren
2013-08-20 6:55 ` George Cherian [this message]
2013-08-20 16:53 ` Stephen Warren
2013-08-21 13:06 ` George Cherian
2013-08-21 17:35 ` Stephen Warren
2013-08-22 5:14 ` George Cherian
2013-08-25 5:30 ` Guenter Roeck
2013-08-30 0:20 ` Chanwoo Choi
2013-08-30 4:33 ` Guenter Roeck
2013-08-20 0:24 ` Chanwoo Choi
2013-08-20 9:36 ` George Cherian
2013-08-20 10:29 ` Chanwoo Choi
2013-08-20 13:24 ` George Cherian
2013-08-20 23:07 ` Chanwoo Choi
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=521312CC.8060003@ti.com \
--to=george.cherian@ti.com \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).