mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Badhri Jagan Sridharan <badhri@google.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kyle Tso <kyletso@google.com>
Subject: Re: [PATCH v1 2/2] usb: typec: tcpm: Enable limit_src_current_set callback
Date: Mon, 7 Feb 2022 08:31:41 +0100	[thread overview]
Message-ID: <YgDK3VtDKlgKh9XQ@kroah.com> (raw)
In-Reply-To: <20220207043907.2758424-2-badhri@google.com>

On Sun, Feb 06, 2022 at 08:39:07PM -0800, Badhri Jagan Sridharan wrote:
> This change allows TCPM to support limit_src_current_set
> callback. When limit_src_current_set is enabled, tcpm
> updates the local source capabilities to only publish
> vSafe5V fixed pdo with the current limit passed through
> limit_src_current_set callback. When limit_src_current_set
> is disabled, tcpm revert back to publishing the default
> source caps.
> 
> This patch is co-authored with kyletso@google.com and
> also uses some of parts of the code that was reverted
> by c17c7cf147ac56312156eaaaf8b2e19c9a59a71a.

Please use the standard format for commits as described in the
documentation.

thanks,

greg k-h

  reply	other threads:[~2022-02-07  7:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  4:39 [PATCH v1 1/2] usb: typec: Introduce typec attributes for limiting source current Badhri Jagan Sridharan
2022-02-07  4:39 ` [PATCH v1 2/2] usb: typec: tcpm: Enable limit_src_current_set callback Badhri Jagan Sridharan
2022-02-07  7:31   ` Greg Kroah-Hartman [this message]
2022-02-07  9:22 ` [PATCH v1 1/2] usb: typec: Introduce typec attributes for limiting source current Heikki Krogerus
2022-02-07 22:38   ` Badhri Jagan Sridharan

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=YgDK3VtDKlgKh9XQ@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=badhri@google.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kyletso@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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
all inboxes | Powered by JetHome®