From: Lu Baolu <baolu.lu@linux.intel.com>
To: Felipe Balbi <balbi@kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lee Jones <lee.jones@linaro.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH 0/7] usb: add support for Intel dual role port mux
Date: Thu, 3 Mar 2016 14:37:37 +0800 [thread overview]
Message-ID: <1456987064-3365-1-git-send-email-baolu.lu@linux.intel.com> (raw)
Intel SOC chips are featured with USB dual role. The host role is
provided by Intel xHCI IP, and the gadget role is provided by IP
from designware. Tablet platform designs always share a single
port for both host and gadget controllers. There is a mux to
switch the port to the right controller according to the cable
type. OS needs to provide the callback to control the mux when
a plug-in event raises. The method to control the mux is platform
dependent. At least three types of implementation can be found
across current devices. 1) GPIO pins; 2) a unit which can be
controlled by memory mapped registers; 3) ACPI ASL code.
This patch series adds supports for Intel dual role port mux.
It includes:
(1) A helper layer on top of extcon for individual mux driver.
It listens to the USB-HOST extcon cable and call the switch
call-back when the cable state changes.
(2) Drivers for GPIO controlled port mux which could be found on
Baytrail devices. A mfd driver is used to split the GPIOs into
USB gpio extcon device and a USB mux device. Driver for USB
gpio extcon device is already in upstream Linux. This patch
series includes a driver for GPIO USB mux.
(3) Drivers for USB port mux controlled through memory mapped
registers and the logic to create the mux device. This type
of dual role port mux could be found in Cherry Trail and
Broxton devices.
Lu Baolu (7):
extcon: usb-gpio: add device binding for platform device
extcon: usb-gpio: add support for ACPI gpio interface
usb: misc: add common code for Intel dual role port mux
usb: misc: add driver for Intel gpio controlled port mux
usb: misc: add driver for Intel drcfg controlled port mux
usb: pci-quirks: add Intel USB drcfg mux device
mfd: intel_vuport: Add Intel virtual USB port MFD Driver
MAINTAINERS | 10 +++
drivers/extcon/extcon-usb-gpio.c | 10 ++-
drivers/mfd/Kconfig | 7 ++
drivers/mfd/Makefile | 1 +
drivers/mfd/intel-vuport.c | 79 +++++++++++++++++
drivers/usb/host/pci-quirks.c | 47 +++++++++-
drivers/usb/host/xhci-ext-caps.h | 2 +
drivers/usb/misc/Kconfig | 20 +++++
drivers/usb/misc/Makefile | 4 +
drivers/usb/misc/intel-mux-drcfg.c | 174 +++++++++++++++++++++++++++++++++++++
drivers/usb/misc/intel-mux-gpio.c | 126 +++++++++++++++++++++++++++
drivers/usb/misc/mux.c | 172 ++++++++++++++++++++++++++++++++++++
include/linux/usb/mux.h | 71 +++++++++++++++
13 files changed, 720 insertions(+), 3 deletions(-)
create mode 100644 drivers/mfd/intel-vuport.c
create mode 100644 drivers/usb/misc/intel-mux-drcfg.c
create mode 100644 drivers/usb/misc/intel-mux-gpio.c
create mode 100644 drivers/usb/misc/mux.c
create mode 100644 include/linux/usb/mux.h
--
2.1.4
next reply other threads:[~2016-03-03 6:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 6:37 Lu Baolu [this message]
2016-03-03 6:37 ` [PATCH 1/7] extcon: usb-gpio: add device binding for platform device Lu Baolu
2016-03-03 7:24 ` Chanwoo Choi
2016-03-03 7:35 ` Lu Baolu
2016-03-03 6:37 ` [PATCH 2/7] extcon: usb-gpio: add support for ACPI gpio interface Lu Baolu
2016-03-03 7:24 ` Chanwoo Choi
2016-03-03 7:35 ` Lu Baolu
2016-03-03 6:37 ` [PATCH 3/7] usb: misc: add common code for Intel dual role port mux Lu Baolu
2016-03-03 16:10 ` Greg Kroah-Hartman
2016-03-04 1:11 ` Lu Baolu
2016-03-03 16:15 ` Greg Kroah-Hartman
2016-03-04 1:25 ` Lu Baolu
2016-03-03 6:37 ` [PATCH 4/7] usb: misc: add driver for Intel gpio controlled " Lu Baolu
2016-03-03 8:16 ` [PATCH] usb: misc: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-03-03 8:16 ` [PATCH 4/7] usb: misc: add driver for Intel gpio controlled port mux kbuild test robot
2016-03-03 6:37 ` [PATCH 5/7] usb: misc: add driver for Intel drcfg " Lu Baolu
2016-03-03 15:20 ` kbuild test robot
2016-03-03 16:12 ` Greg Kroah-Hartman
2016-03-04 1:41 ` Lu Baolu
2016-03-03 16:14 ` Greg Kroah-Hartman
2016-03-04 1:38 ` Lu Baolu
2016-03-04 1:44 ` Greg Kroah-Hartman
2016-03-04 1:58 ` Lu Baolu
2016-03-03 6:37 ` [PATCH 6/7] usb: pci-quirks: add Intel USB drcfg mux device Lu Baolu
2016-03-03 6:37 ` [PATCH 7/7] mfd: intel_vuport: Add Intel virtual USB port MFD Driver Lu Baolu
2016-03-03 8:16 ` kbuild test robot
2016-03-03 8:16 ` [PATCH] mfd: intel_vuport: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-03-03 11:35 ` [PATCH 7/7] mfd: intel_vuport: Add Intel virtual USB port MFD Driver kbuild test robot
2016-03-03 17:26 ` kbuild test robot
2016-03-03 19:57 ` kbuild test robot
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=1456987064-3365-1-git-send-email-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=balbi@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=myungjoo.ham@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox