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 v3] extcon: add Maxim MAX3355 driver
Date: Thu, 17 Dec 2015 21:20:25 +0000 [thread overview]
Message-ID: <56732719.7020301@cogentembedded.com> (raw)
In-Reply-To: <56721F31.5060608@samsung.com>
Hello.
On 12/17/2015 05:34 AM, Chanwoo Choi wrote:
>> On 2015년 12월 17일 03:07, Sergei Shtylyov 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.
>>>
>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>>
>>> ---
>>> Changes in version 3:
>>> - reformatted the change log.
>>>
>>> Changes in version 2:
>>> - added the USB gadget cable support;
>>> - added the remove() driver method which drives SHDN# GPIO low to save power;
>>> - dropped vendor prefix from the ID GPIO property name;
>>> - changed the GPIO property name suffix to "-gpios";
>>> - switched to usign extcon_set_cable_state_() API;
>>> - switched to using the gpiod/sleeping 'gpiolib' APIs;
>>> - addded error messages to max3355_probe();
>>> - added IRQF_NO_SUSPEND flasg to the devm_request_threaded_irq() call;
>>> - renamed 'ret' variable to 'err' in max3355_probe();
>>> - expanded the Kconfig entry help text;
>>> - added vendor name to the patch summary, the bindings document, the Kconfig
>>> entry, the driver heading comment, the module description, and the change log;
>>> - fixed up and reformatted the change log.
>>>
>>> Documentation/devicetree/bindings/extcon/extcon-max3355.txt | 21 +
>>> drivers/extcon/Kconfig | 8
>>> drivers/extcon/Makefile | 1
>>> drivers/extcon/extcon-max3355.c | 153 ++++++++++++
>>> 4 files changed, 183 insertions(+)
>>>
>
> [snip]
>
>>> + return 0;
>>> +}
>>> +
>>> +static int max3355_remove(struct platform_device *pdev)
>>> +{
>>> + struct max3355_data *data = platform_get_drvdata(pdev);
>>> +
>>> + gpiod_set_value_cansleep(data->shdn_gpiod, 0);
>
> Don't need to handle the 'shdn' gpio on resume/suspend funtcion?
>
> But, if the interrput of id gpio is used for wakeup source,
> there is no reason to handle it for suspend mode.
You told me to pass IRQF_NO_SUSPEND to devm_request_threaded_irq(), didn't
you?
> [snip]
> Thanks,
> Chanwoo Choi
MBR, Sergei
next prev parent reply other threads:[~2015-12-17 21:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 18:07 [PATCH v3] extcon: add Maxim MAX3355 driver Sergei Shtylyov
2015-12-17 0:53 ` Krzysztof Kozlowski
2015-12-17 14:36 ` Sergei Shtylyov
[not found] ` <5672C884.3000603-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-12-18 0:19 ` Krzysztof Kozlowski
2015-12-18 13:45 ` Sergei Shtylyov
[not found] ` <2473780.4IzuWX8hE2-gHKXc3Y1Z8zGSmamagVegGFoWSdPRAKMAL8bYrjMMd8@public.gmane.org>
2015-12-17 2:16 ` Chanwoo Choi
[not found] ` <56721AFE.9020103-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-12-17 2:34 ` Chanwoo Choi
2015-12-17 21:20 ` Sergei Shtylyov [this message]
[not found] ` <56732719.7020301-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2015-12-18 1:04 ` 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=56732719.7020301@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).