[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcqBuWHq=VVvVPnbGiOpxuEGSPhyed2oNcigL3scSVPMA@mail.gmail.com>
Date: Tue, 30 May 2017 19:20:35 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.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
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? I would rather believe that it is some 3rd
party known IP block with platform specific soldering.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists