From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751029AbdE3QUi (ORCPT ); Tue, 30 May 2017 12:20:38 -0400 Received: from mail-qt0-f182.google.com ([209.85.216.182]:33761 "EHLO mail-qt0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750985AbdE3QUh (ORCPT ); Tue, 30 May 2017 12:20:37 -0400 MIME-Version: 1.0 In-Reply-To: <84e3fdaf979c070a5c39c7635910fee30c3a8b06.1496104447.git.sathyanarayanan.kuppuswamy@linux.intel.com> References: <84e3fdaf979c070a5c39c7635910fee30c3a8b06.1496104447.git.sathyanarayanan.kuppuswamy@linux.intel.com> From: Andy Shevchenko Date: Tue, 30 May 2017 19:20:35 +0300 Message-ID: Subject: Re: [PATCH v1 1/1] mux: mux-intel-usb: Add Intel USB Multiplexer driver To: Kuppuswamy Sathyanarayanan Cc: Peter Rosin , "Krogerus, Heikki" , "linux-kernel@vger.kernel.org" , Sathyanarayanan Kuppuswamy Natarajan Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 30, 2017 at 3:47 AM, wrote: > From: Kuppuswamy Sathyanarayanan > > In some Intel SOCs, a single USB port is shared between USB device and SoCs > host controller and an internal mux is used to control the selection of > port by host/device controllers. This driver adds support for the USB > internal mux, and all consumers of this mux can use interfaces provided > by mux subsytem to control the state of the internal mux. > +config MUX_INTEL_USB > + tristate "Intel USB Mux" It's indeed Intel's IP? I would rather believe that it is some 3rd party known IP block with platform specific soldering. -- With Best Regards, Andy Shevchenko