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: Thu, 22 Aug 2013 10:44:31 +0530 [thread overview]
Message-ID: <52159E37.90501@ti.com> (raw)
In-Reply-To: <5214FA64.3040902@wwwdotorg.org>
On 8/21/2013 11:05 PM, Stephen Warren wrote:
> On 08/21/2013 07:06 AM, George Cherian wrote:
>> Hi Stephen,
>>
>> On 8/20/2013 10:23 PM, Stephen Warren wrote:
>>>>> 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.
>>> In that case, the PCF8575 node needs to be a GPIO controller and an IRQ
>>> controller, as does the driver for the PCF8575. This binding should have
>>> a single entry in the gpios property, and the driver can call
>>> gpio_to_irq() on that so it knows which IRQ to request.
>> You meant some thing like this?
>>
>> pcf_usb: pcf8575@21 {
>> compatible = "ti,pcf8575";
>> reg = <0x21>;
>> gpio-controller;
>> #gpio-cells = <2>;
>> interrupt-parent = <&gpio6>;
>> interrupts = <11 2>;
>> interrupt-controller;
>> #interrupt-cells = <2>;
>> };
>>
>> usb_vid_gpio {
>> compatible = "ti,dra7xx-usb";
>> gpios = <&pcf_usb 1 0>;
>> };
> Yes.
>
> Except that the compatible value for the usb_vid_gpio node still looks
> wrong, since I think that node isn't anything to do with any particular SoC.
Yes will fix that too in v2.
--
-George
next prev parent reply other threads:[~2013-08-22 5:14 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
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 [this message]
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=52159E37.90501@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).