All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Benson Leung <bleung@chromium.org>,
	Prashant Malani <pmalani@chromium.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 0/9] usb: typec: Driver for Intel PMC Mux-Agent
Date: Wed, 4 Mar 2020 11:15:05 +0100	[thread overview]
Message-ID: <20200304101505.GA1566030@kroah.com> (raw)
In-Reply-To: <20200302135353.56659-1-heikki.krogerus@linux.intel.com>

On Mon, Mar 02, 2020 at 04:53:44PM +0300, Heikki Krogerus wrote:
> Hi,
> 
> The statements were ended incorrectly with comma instead of semicolon
> in drivers/usb/cdns3/core.c (PATCH 5/9) as pointed out by Peter. I've
> fixed that in this version. There are no other changes.
> 
> v2 commit message:
> 
> I've unified the driver data handling in all drivers in patch 5/9 as
> requested by Peter, and also now using consistently dev_set_drvdata()
> in patch 4/9 as requested by Chunfeng Yun. Those were the only
> changes in this version.
> 
> The original (v1) commit message:
> 
> The Intel PMC (Power Management Controller) microcontroller, which is
> available on most SOCs from Intel, has a function called mux-agent.
> The mux-agent, when visible to the operating system, makes it possible
> to control the various USB muxes on the system.
> 
> In practice the mux-agent is a device that controls multiple muxes.
> Unfortunately both the USB Type-C Class and the USB Role Class don't
> have proper support for that kind of devices that handle multiple
> muxes, which is why I had to tweak the APIs a bit.
> 
> On top of the API changes, and the driver of course, I'm adding a
> header for the Thunderbolt 3 alt mode since the "mux-agent" supports
> it.

Looks good, all now queued up, thanks.

greg k-h

      parent reply	other threads:[~2020-03-04 10:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-02 13:53 [PATCH v3 0/9] usb: typec: Driver for Intel PMC Mux-Agent Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 1/9] usb: typec: mux: Allow the muxes to be named Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 2/9] usb: typec: mux: Add helpers for setting the mux state Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 3/9] usb: typec: mux: Allow the mux handles to be requested with fwnode Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 4/9] usb: roles: Leave the private driver data pointer to the drivers Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 5/9] usb: roles: Provide the switch drivers handle to the switch in the API Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 6/9] usb: roles: Allow the role switches to be named Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 7/9] device property: Export fwnode_get_name() Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 8/9] usb: typec: Add definitions for Thunderbolt 3 Alternate Mode Heikki Krogerus
2020-03-02 13:53 ` [PATCH v3 9/9] usb: typec: driver for Intel PMC mux control Heikki Krogerus
2020-03-04 10:15 ` Greg Kroah-Hartman [this message]

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=20200304101505.GA1566030@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bleung@chromium.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pmalani@chromium.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.