From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751279AbdE3SuI (ORCPT ); Tue, 30 May 2017 14:50:08 -0400 Received: from mail-qk0-f176.google.com ([209.85.220.176]:36293 "EHLO mail-qk0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750942AbdE3SuG (ORCPT ); Tue, 30 May 2017 14:50:06 -0400 MIME-Version: 1.0 In-Reply-To: <0e2a3df8-e3b4-28d3-eea9-5ec6a684bf53@linux.intel.com> References: <84e3fdaf979c070a5c39c7635910fee30c3a8b06.1496104447.git.sathyanarayanan.kuppuswamy@linux.intel.com> <0e2a3df8-e3b4-28d3-eea9-5ec6a684bf53@linux.intel.com> From: Andy Shevchenko Date: Tue, 30 May 2017 21:50:05 +0300 Message-ID: Subject: Re: [PATCH v1 1/1] mux: mux-intel-usb: Add Intel USB Multiplexer driver To: Kuppuswamy Sathyanarayanan , Hans de Goede 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 9:21 PM, sathyanarayanan kuppuswamy wrote: >> On Tue, May 30, 2017 at 3:47 AM, >> 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