mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>, JC Kuo <jckuo@nvidia.com>,
	<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] phy: tegra: xusb: Add Tegra186 support
Date: Mon, 18 Mar 2019 14:26:17 +0530	[thread overview]
Message-ID: <5dbaa0ad-9567-621d-9836-9cdb6ed366b0@ti.com> (raw)
In-Reply-To: <20190221154634.10684-1-thierry.reding@gmail.com>

Hi Thierry,

On 21/02/19 9:16 PM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> This series adds support for Tegra186 to the XUSB pad controller driver.
> Patch 1 extends the device tree bindings with support for Tegra186 while
> patches 2-4 are preparatory work for the final patch 5 that adds the
> Tegra186 specific programming for the UPHY blocks.
> 
> Changes in v2:
> - address review comments from Kishon
> - added Reviewed-by tags from JC

I've merged this series.
However I'd like to see if we can add the features of xusb.c to phy-core.c and
remove xusb.c. This will be useful if there are other PHY vendors with similar
design as Tegra.

Thanks
Kishon

> 
> Thierry
> 
> JC Kuo (2):
>   phy: tegra: xusb: Skip single function lane programming
>   phy: tegra: xusb: Add Tegra186 support
> 
> Thierry Reding (3):
>   dt-bindings: phy: tegra: Add Tegra186 support
>   phy: tegra: xusb: Parse dual-role mode property
>   phy: tegra: xusb: Add support for power supplies
> 
>  .../phy/nvidia,tegra124-xusb-padctl.txt       |   9 +
>  MAINTAINERS                                   |   5 +
>  drivers/phy/tegra/Makefile                    |   1 +
>  drivers/phy/tegra/xusb-tegra186.c             | 899 ++++++++++++++++++
>  drivers/phy/tegra/xusb.c                      |  67 +-
>  drivers/phy/tegra/xusb.h                      |  35 +
>  6 files changed, 1014 insertions(+), 2 deletions(-)
>  create mode 100644 drivers/phy/tegra/xusb-tegra186.c
> 

      parent reply	other threads:[~2019-03-18  8:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 15:46 Thierry Reding
2019-02-21 15:46 ` [PATCH v2 1/5] dt-bindings: phy: tegra: " Thierry Reding
2019-02-22 23:39   ` Rob Herring
2019-02-21 15:46 ` [PATCH v2 2/5] phy: tegra: xusb: Skip single function lane programming Thierry Reding
2019-02-21 15:46 ` [PATCH v2 3/5] phy: tegra: xusb: Parse dual-role mode property Thierry Reding
2019-02-21 15:46 ` [PATCH v2 4/5] phy: tegra: xusb: Add support for power supplies Thierry Reding
2019-02-21 15:46 ` [PATCH v2 5/5] phy: tegra: xusb: Add Tegra186 support Thierry Reding
2019-03-18  8:56 ` Kishon Vijay Abraham I [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=5dbaa0ad-9567-621d-9836-9cdb6ed366b0@ti.com \
    --to=kishon@ti.com \
    --cc=jckuo@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@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

all inboxes | Powered by JetHome®