From: sathyanarayanan kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Peter Rosin <peda@axentia.se>,
"Krogerus, Heikki" <heikki.krogerus@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sathyanarayanan Kuppuswamy Natarajan <sathyaosid@gmail.com>
Subject: Re: [PATCH v1 1/1] mux: mux-intel-usb: Add Intel USB Multiplexer driver
Date: Tue, 30 May 2017 11:21:00 -0700 [thread overview]
Message-ID: <0e2a3df8-e3b4-28d3-eea9-5ec6a684bf53@linux.intel.com> (raw)
In-Reply-To: <CAHp75VcqBuWHq=VVvVPnbGiOpxuEGSPhyed2oNcigL3scSVPMA@mail.gmail.com>
Hi Andy,
On 05/30/2017 09:20 AM, Andy Shevchenko wrote:
> On Tue, May 30, 2017 at 3:47 AM,
> <sathyanarayanan.kuppuswamy@linux.intel.com> wrote:
>> From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.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
next prev parent reply other threads:[~2017-05-30 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 0:47 [PATCH v1 1/1] mux: mux-intel-usb: Add Intel USB Multiplexer driver sathyanarayanan.kuppuswamy
2017-05-30 13:40 ` Peter Rosin
2017-05-30 17:47 ` sathyanarayanan kuppuswamy
2017-05-31 6:29 ` Peter Rosin
2017-05-31 23:33 ` sathyanarayanan kuppuswamy
2017-05-30 16:20 ` Andy Shevchenko
2017-05-30 18:21 ` sathyanarayanan kuppuswamy [this message]
2017-05-30 18:50 ` Andy Shevchenko
2017-05-31 12:21 ` Hans de Goede
2017-05-31 13:05 ` Peter Rosin
2017-05-31 14:18 ` Hans de Goede
2017-05-31 15:30 ` Peter Rosin
2017-05-31 18:27 ` Hans de Goede
2017-05-31 23:29 ` sathyanarayanan kuppuswamy
2017-05-31 23:21 ` sathyanarayanan kuppuswamy
2017-05-31 23:12 ` sathyanarayanan kuppuswamy
2017-06-01 14:54 ` Hans de Goede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e2a3df8-e3b4-28d3-eea9-5ec6a684bf53@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=sathyaosid@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox