From: Guenter Roeck <linux@roeck-us.net>
To: George Cherian <george.cherian@ti.com>,
cw00.choi@samsung.com, myungjoo.ham@samsung.com,
grant.likely@linaro.org, rdunlap@infradead.org,
galak@codeaurora.org, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, robh+dt@kernel.org,
pawel.moll@arm.com
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] extcon: extcon-dra7xx: Add Extcon driver for DRA7xx
Date: Mon, 16 Jun 2014 07:15:49 -0700 [thread overview]
Message-ID: <539EFC15.8000304@roeck-us.net> (raw)
In-Reply-To: <539E8399.80902@ti.com>
On 06/15/2014 10:41 PM, George Cherian wrote:
> On 6/16/2014 10:29 AM, Guenter Roeck wrote:
>> On 06/15/2014 07:42 PM, George Cherian wrote:
>>> This is the driver for the USB ID pin detection. This driver
>>> handles only the USB ID pin changes generated by cable
>>> insertion/removal.
>>>
>>> Signed-off-by: George Cherian <george.cherian@ti.com>
>>
>> Hi George,
>>
>> Curious: Why can't you use extcon-gpio ?
> Main reason being missing dt support.
Then why not add dt support to it ?
>>
>> Also, I thought that Linux specific bindings would be unacceptable.
>> "ti,dra7xx-extcon" looks very linux specific to me. Did the rules change ?
>>
> Then how about "ti,extcon-usbid" ?
"extcon" seems very linux specific to me.
Anyway, not arguing, just asking, since I wondered. If the extcon maintainer
and the dt folks are happy with your driver, so am I.
Guenter
next prev parent reply other threads:[~2014-06-16 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 2:42 [PATCH] extcon: extcon-dra7xx: Add Extcon driver for DRA7xx George Cherian
2014-06-16 4:59 ` Guenter Roeck
2014-06-16 5:41 ` George Cherian
2014-06-16 5:48 ` Chanwoo Choi
2014-06-17 12:26 ` George Cherian
2014-06-16 14:15 ` Guenter Roeck [this message]
2014-06-17 12:28 ` George Cherian
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=539EFC15.8000304@roeck-us.net \
--to=linux@roeck-us.net \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=george.cherian@ti.com \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.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