[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Ve=1X9X_QYDWcRmRC4gaCyHdVcwzKKxBFEEg3L8UUe7dQ@mail.gmail.com>
Date: Tue, 30 May 2017 21:50:05 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Hans de Goede <hdegoede@...hat.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 9:21 PM, sathyanarayanan kuppuswamy
<sathyanarayanan.kuppuswamy@...ux.intel.com> wrote:
>> On Tue, May 30, 2017 at 3:47 AM,
>> <sathyanarayanan.kuppuswamy@...ux.intel.com> wrote:
>>> + 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).
Okay, the best people to give a feedback here are Heikki and Hans.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists