Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755003AbbLANco (ORCPT ); Tue, 1 Dec 2015 08:32:44 -0500 Received: from mga14.intel.com ([192.55.52.115]:54842 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753810AbbLANcn (ORCPT ); Tue, 1 Dec 2015 08:32:43 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,369,1444719600"; d="scan'208";a="851409458" From: Heikki Krogerus To: Chanwoo Choi , Greg Kroah-Hartman Cc: MyungJoo Ham , David Cohen , Lu Baolu , Mathias Nyman , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] extcon: driver for Intel USB MUX Date: Tue, 1 Dec 2015 15:32:36 +0200 Message-Id: <1448976758-35807-1-git-send-email-heikki.krogerus@linux.intel.com> X-Mailer: git-send-email 2.6.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2131 Lines: 52 Hi, This is a driver for an internal mux which is available on most modern Intel platforms that shares an USB port between USB Device Controller and xHCI. Normally BIOS or ACPI take care of it, but on some platforms that is not possible, and the OS has to control it. When the mux needs to be handled by OS, there is always an external component that detects connection changes in the port behind the mux, for example PMIC. The driver for that component needs to notify this driver. The mux itself has no means to detect connection changes on the port. User selectable kconfig option is deliberately left out. The driver for the mux needs to be always selected by the drivers for the component that can notify the mux driver about connection changes. The only platforms the need the OS to be in control of the mux so far are Cherrytrail based, and on Cherrytrail SOC the mux control registers are mapped to xHCI MMIO. The second patch will register an instance of the mux from pci_quirks.c if the mux is detected and if the driver has been loaded. The mux control registers are defined in Cherrytrail datasheets [1] page 2230-2234. I think these should go via extcon tree, but it's up to you guys of course. [1] http://www.intel.es/content/www/es/es/processors/atom/atom-z8000-datasheet-vol-2.html Heikki Krogerus (2): extcon: add driver for Intel USB mux usb: pci-quirks: register USB mux found on Cherrytrail SOC drivers/extcon/Kconfig | 5 ++ drivers/extcon/Makefile | 1 + drivers/extcon/extcon-intel-usb.c | 112 +++++++++++++++++++++++++++++++++++ drivers/usb/host/pci-quirks.c | 30 +++++++++- include/linux/extcon/intel_usb_mux.h | 31 ++++++++++ 5 files changed, 178 insertions(+), 1 deletion(-) create mode 100644 drivers/extcon/extcon-intel-usb.c create mode 100644 include/linux/extcon/intel_usb_mux.h -- 2.6.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/