All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] PHY: For 5.2
Date: Thu, 25 Apr 2019 10:50:20 +0200	[thread overview]
Message-ID: <20190425085020.GA10136@kroah.com> (raw)
In-Reply-To: <20190423121032.3910-1-kishon@ti.com>

On Tue, Apr 23, 2019 at 05:40:32PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
> 
> Please find the pull request of 5.2 merge window below.
> 
> It adds a new PHY ops to _release_ the PHY which can be used by PHY drivers
> for cleaning up any initializations done during phy_get.
> It adds a number of new PHY driver including Amlogic's USB2 PHY and a
> shared USB3 + PCIE PHY, Broadcom's Stingray USB PHY, Hisilicon's USB PHY
> in hi3660, MediaTek's UFS M-PHY, Nvidia's XUSB pad controller in
> Tegra186 and TI's AM654 SERDES.
> 
> For the complete list of changes, see the tag message below.
> 
> There is a change in ufs-qcom.c (SCSI subsystem) which now exposes the
> reset controller to be used by PHY. This is required to disable the
> regulator that powers UFS in order to save power during system suspend
> while following the PHY initialization sequence.
> 
> All of these were present in linux-next for quite a while and shouldn't
> have any conflicts.
> 
> Let me know If I have to make any changes.
> 
> Thanks
> Kishon
> 
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> 
>   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git tags/phy-for-5.2

Now pulled and pushed out, thansk.

greg k-h

      reply	other threads:[~2019-04-25  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 12:10 [GIT PULL] PHY: For 5.2 Kishon Vijay Abraham I
2019-04-25  8:50 ` 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=20190425085020.GA10136@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.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.