From: Lu Baolu <baolu.lu@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: felipe.balbi@linux.intel.com,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 2/7] usb: mux: add generic code for dual role port mux
Date: Fri, 27 May 2016 16:07:46 +0800 [thread overview]
Message-ID: <57480052.1070606@linux.intel.com> (raw)
In-Reply-To: <20160527080027.GE22411@kuha.fi.intel.com>
Hi,
On 05/27/2016 04:00 PM, Heikki Krogerus wrote:
>> I agree with you that we should move extcon out of the framework.
>> >
>> > In order to support multiport systems, I have below proposal.
>> >
>> > Currently, we have below interfaces.
>> >
>> > struct portmux_dev *portmux_register(struct portmux_desc *desc);
>> > void portmux_unregister(struct portmux_dev *pdev);
>> >
>> > I will add below ones.
>> >
>> > struct portmux_dev *portmux_lookup_by_name(char *name);
>> > int portmux_switch(struct portmux_dev *pdev, enum port_role);
>> >
>> > The normal usage mode is
>> > 1) the mux device is registered as soon as a mux is detected with
>> > portmux_register();
>> > 2) In components like USB PHY or changer drivers, the mux could
>> > be retrieved with portmux_lookup_by_name() and controlled via
>> > portmux_switch().
>> >
>> > Is this helpful?
> It works for me, and we can improve it later if needed.
Okay, thanks.
Best regards,
Lu Baolu
next prev parent reply other threads:[~2016-05-27 8:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 5:32 [PATCH v8 0/7] usb: add support for Intel dual role port mux Lu Baolu
2016-05-05 5:32 ` [PATCH v8 1/7] regulator: fixed: add support for ACPI interface Lu Baolu
2016-05-13 11:17 ` Mark Brown
2016-05-16 1:00 ` Lu Baolu
2016-05-05 5:32 ` [PATCH v8 2/7] usb: mux: add generic code for dual role port mux Lu Baolu
2016-05-25 11:06 ` Heikki Krogerus
2016-05-26 1:03 ` Lu Baolu
2016-05-27 8:00 ` Heikki Krogerus
2016-05-27 8:07 ` Lu Baolu [this message]
2016-05-05 5:32 ` [PATCH v8 3/7] usb: mux: add driver for Intel gpio controlled " Lu Baolu
2016-05-05 5:33 ` [PATCH v8 4/7] usb: mux: add driver for Intel drcfg " Lu Baolu
2016-05-05 5:33 ` [PATCH v8 5/7] mfd: intel_vuport: Add Intel virtual USB port MFD Driver Lu Baolu
2016-05-09 14:26 ` Lee Jones
2016-05-05 5:33 ` [PATCH v8 6/7] usb: pci-quirks: add Intel USB drcfg mux device Lu Baolu
2016-05-05 5:33 ` [PATCH v8 7/7] MAINTAINERS: add maintainer entry for Intel USB dual role mux drivers Lu Baolu
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=57480052.1070606@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=broonie@kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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.