From: Felipe Balbi <balbi@kernel.org>
To: Baolin Wang <baolin.wang@linaro.org>, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org, neilb@suse.com, jun.li@nxp.com,
peter.chen@freescale.com, broonie@kernel.org,
baolin.wang@linaro.org
Subject: Re: [PATCH v2 1/2] usb: phy: Introduce one extcon device into usb phy
Date: Tue, 28 Mar 2017 16:40:44 +0300 [thread overview]
Message-ID: <8737dxh63n.fsf@linux.intel.com> (raw)
In-Reply-To: <0b16763df04e197fb5b3c21b19799280d3bce275.1490248054.git.baolin.wang@linaro.org>
Hi,
Baolin Wang <baolin.wang@linaro.org> writes:
> Usually usb phy need register one extcon device to get the connection
> notifications. It will remove some duplicate code if the extcon device
> is registered using common code instead of each phy driver having its
> own related extcon APIs. So we add one pointer of extcon device into
> usb phy structure, and some other helper functions to register extcon.
>
> Suggested-by: NeilBrown <neilb@suse.com>
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
will this work with devices which have ID and VBUS from separate EXTCON
devices?
--
balbi
next prev parent reply other threads:[~2017-03-28 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 5:54 [PATCH v2 1/2] usb: phy: Introduce one extcon device into usb phy Baolin Wang
2017-03-23 5:54 ` [PATCH v2 2/2] usb: phy: phy-qcom-8x16-usb: Remove redundant extcon register/unregister Baolin Wang
2017-03-28 13:42 ` Felipe Balbi
2017-03-30 3:26 ` Baolin Wang
2017-03-28 13:40 ` Felipe Balbi [this message]
2017-03-30 2:56 ` [PATCH v2 1/2] usb: phy: Introduce one extcon device into usb phy Baolin Wang
2017-03-28 22:56 ` NeilBrown
2017-03-30 3:00 ` Baolin Wang
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=8737dxh63n.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jun.li@nxp.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=neilb@suse.com \
--cc=peter.chen@freescale.com \
/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.