From: Peter Chen <peter.chen@freescale.com>
To: "Ivan T. Ivanov" <ivan.ivanov@linaro.org>, cw00.choi@samsung.com
Cc: Kumar Gala <galak@codeaurora.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] usb: chipidea: Use extcon framework for VBUS and ID detect
Date: Thu, 16 Apr 2015 15:46:50 +0800 [thread overview]
Message-ID: <20150416074649.GA1709@shlinux2> (raw)
In-Reply-To: <1429104915-11079-1-git-send-email-ivan.ivanov@linaro.org>
On Wed, Apr 15, 2015 at 04:35:15PM +0300, Ivan T. Ivanov wrote:
> On recent Qualcomm platforms VBUS and ID lines are not routed to
> USB PHY LINK controller. Use extcon framework to receive connect
> and disconnect ID and VBUS notification.
>
> Signed-off-by: Ivan T. Ivanov <ivan.ivanov@linaro.org>
> ---
>
> Changes since v0 [1], as per Peter Chen suggestions:
>
> * Moved external connector parsing code to ci_get_platdata()
> * Moved external connector related variables to struct ci_hdrc_platform_data
> * Rename ci_host_notifier() to ci_id_notifier()
> * Fixed device bindings description
> * Use select EXTCON framework, instead of depends on.
Hi Chanwoo,
It seems the CONFIG_EXTCON is better as a hide config.
See below thread for GENERIC_PHY.
http://marc.info/?l=linux-kernel&m=142902133811818&w=2
Peter
next prev parent reply other threads:[~2015-04-16 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 13:35 [PATCH v2] usb: chipidea: Use extcon framework for VBUS and ID detect Ivan T. Ivanov
2015-04-15 14:11 ` Robert Baldyga
[not found] ` <552E7187.3030005-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-04-15 14:54 ` Ivan T. Ivanov
2015-04-16 7:46 ` Peter Chen [this message]
2015-05-26 7:47 ` Ivan T. Ivanov
2015-05-26 9:13 ` Peter Chen
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=20150416074649.GA1709@shlinux2 \
--to=peter.chen@freescale.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ivan.ivanov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.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).