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,
linux-kernel@vger.kernel.org
Cc: linux-sh@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] extcon: add Maxim MAX3355 driver
Date: Tue, 15 Dec 2015 22:11:47 +0300 [thread overview]
Message-ID: <567065F3.6010009@cogentembedded.com> (raw)
In-Reply-To: <566F6AEC.1030903@samsung.com>
On 12/15/2015 04:20 AM, Chanwoo Choi wrote:
>> Maxim Integrated MAX3355E chip integrates a charge pump and comparators to
> ^^ ^^
>> enable a system with an integrated USB OTG dual-role transceiver to function
>> as an USB OTG dual-role device. In addition to sensing/controlling Vbus,
> ^^ ^^ ^^ ^^
>> the chip also passes thru the ID signal from the USB OTG connector.
> ^^
>> On some Renesas boards, this signal is just fed into the SoC thru a GPIO
> ^^ ^^
>> pin -- there's no real OTG controller, only host and gadget USB controllers
> ^^ ^^
>> sharing the same USB bus; however, we'd like to allow host or gadget drivers
> ^^
>> to be loaded depending on the cable type, hence the need for the MAX3355
> ^^
>> extcon driver. The Vbus status signals are also wired to GPIOs (however, we
>> aren't currently interested in them), the OFFVBUS# signal is controlled by
> ^^ ^^
>> the host controllers, there's also the SHDN# signal wired to a GPIO, it
> ^^
>> should be driven high for the normal operation.
> ^^
> As above '^' expression, you used the double space between words.
> You should fix it.
OK, since so many people seem to be offended by that, I'll fix it.
Meanwhile, please comment on the patch itself.
> Thanks,
> Chanwoo Choi
[...]
MBR, Sergei
prev parent reply other threads:[~2015-12-15 19:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 23:22 [PATCH v2] extcon: add Maxim MAX3355 driver Sergei Shtylyov
2015-12-14 1:24 ` Rob Herring
2015-12-14 17:36 ` Sergei Shtylyov
[not found] ` <566EFE0A.4000104-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-12-14 22:21 ` Rob Herring
2015-12-14 22:29 ` Sergei Shtylyov
2015-12-14 23:44 ` Greg KH
2015-12-15 11:24 ` Sergei Shtylyov
[not found] ` <566FF888.8060200-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-12-15 11:28 ` Geert Uytterhoeven
2015-12-15 11:54 ` Sergei Shtylyov
2015-12-15 12:12 ` Geert Uytterhoeven
2015-12-15 18:51 ` Greg KH
[not found] ` <20151215185156.GD16129-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-12-15 19:09 ` Sergei Shtylyov
2015-12-15 1:20 ` Chanwoo Choi
2015-12-15 19:11 ` Sergei Shtylyov [this message]
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=567065F3.6010009@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 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).