From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
myungjoo.ham@samsung.com, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] extcon-usb-gpio: add enable pin support
Date: Fri, 11 Dec 2015 14:44:45 +0000 [thread overview]
Message-ID: <566AE15D.1020506@cogentembedded.com> (raw)
In-Reply-To: <566A4B97.7080801@samsung.com>
Hello.
On 12/11/2015 07:05 AM, Chanwoo Choi wrote:
>> Sometimes there's a real OTG chip behind the USB ID signal mapped to a GPIO
>> pin: in my case it's Maxim Integrated MAX3355E which integrates Vbus charge
>> pump and comparators and passes thru the ID signal from an OTG connector.
>
> s/thru/through ?
"Thru" is valid English.
>> This chip also has the SHDN# pin which should be driven high for the normal
>> operation and low to save power; it is connected to a GPIO pin as well on,
>> hence we'll have to teach the driver to parse the new optional device tree
>> property, "enable-gpio"...
> This patch description includes the double space between words. Also, I think
So what?
> you need to write the patch description again for formal style.
Not sure I understand you.
> This patch adds the specific 'enable-gpio' pin to express the SHDN#pin for MAX3355E.
> I think it is not regular and standard case because maybe USB specification
> don't include the SHDN#pin information.
Certainly, it's not a USB pin.
> I think it not appropriate way.
> Instead, you better to make the MAX3355 extcon driver to support this case.
OK, just didn't want to duplicate most of this driver there...
> Thanks,
> Chanwoo
MBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Chanwoo Choi <cw00.choi@samsung.com>,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
myungjoo.ham@samsung.com, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] extcon-usb-gpio: add enable pin support
Date: Fri, 11 Dec 2015 17:44:45 +0300 [thread overview]
Message-ID: <566AE15D.1020506@cogentembedded.com> (raw)
In-Reply-To: <566A4B97.7080801@samsung.com>
Hello.
On 12/11/2015 07:05 AM, Chanwoo Choi wrote:
>> Sometimes there's a real OTG chip behind the USB ID signal mapped to a GPIO
>> pin: in my case it's Maxim Integrated MAX3355E which integrates Vbus charge
>> pump and comparators and passes thru the ID signal from an OTG connector.
>
> s/thru/through ?
"Thru" is valid English.
>> This chip also has the SHDN# pin which should be driven high for the normal
>> operation and low to save power; it is connected to a GPIO pin as well on,
>> hence we'll have to teach the driver to parse the new optional device tree
>> property, "enable-gpio"...
> This patch description includes the double space between words. Also, I think
So what?
> you need to write the patch description again for formal style.
Not sure I understand you.
> This patch adds the specific 'enable-gpio' pin to express the SHDN#pin for MAX3355E.
> I think it is not regular and standard case because maybe USB specification
> don't include the SHDN#pin information.
Certainly, it's not a USB pin.
> I think it not appropriate way.
> Instead, you better to make the MAX3355 extcon driver to support this case.
OK, just didn't want to duplicate most of this driver there...
> Thanks,
> Chanwoo
MBR, Sergei
next prev parent reply other threads:[~2015-12-11 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 23:07 [PATCH] extcon-usb-gpio: add enable pin support Sergei Shtylyov
2015-12-10 23:07 ` Sergei Shtylyov
2015-12-11 3:53 ` Rob Herring
2015-12-11 3:53 ` Rob Herring
2015-12-11 18:33 ` Sergei Shtylyov
2015-12-11 18:33 ` Sergei Shtylyov
2015-12-11 4:05 ` Chanwoo Choi
2015-12-11 4:05 ` Chanwoo Choi
2015-12-11 14:44 ` Sergei Shtylyov [this message]
2015-12-11 14:44 ` Sergei Shtylyov
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=566AE15D.1020506@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.