[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0e2a3df8-e3b4-28d3-eea9-5ec6a684bf53@linux.intel.com>
Date: Tue, 30 May 2017 11:21:00 -0700
From: sathyanarayanan kuppuswamy
<sathyanarayanan.kuppuswamy@...ux.intel.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Peter Rosin <peda@...ntia.se>,
"Krogerus, Heikki" <heikki.krogerus@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sathyanarayanan Kuppuswamy Natarajan <sathyaosid@...il.com>
Subject: Re: [PATCH v1 1/1] mux: mux-intel-usb: Add Intel USB Multiplexer
driver
Hi Andy,
On 05/30/2017 09:20 AM, Andy Shevchenko wrote:
> On Tue, May 30, 2017 at 3:47 AM,
> <sathyanarayanan.kuppuswamy@...ux.intel.com> wrote:
>> From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>
>>
>> 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?
Register map to control this MUX comes from Intel vendor defined XHCI
extended cap region of SOC.
> I would rather believe that it is some 3rd
> party known IP block with platform specific soldering.
I don't think its platform specific support. I believe its a SOC
specific thing( mainly for CHT and APL SoCs).
>
--
Sathyanarayanan Kuppuswamy
Linux kernel developer
Powered by blists - more mailing lists