linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Jui <rjui@broadcom.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>, <linux-kernel@vger.kernel.org>,
	"JD (Jiandong) Zheng" <jdzheng@broadcom.com>,
	Arun Parameswaran <arunp@broadcom.com>,
	<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH v5 0/2] Add Cygnus PCIe Serdes/PHY support
Date: Mon, 28 Sep 2015 09:03:52 -0700	[thread overview]
Message-ID: <560964E8.8040507@broadcom.com> (raw)
In-Reply-To: <1442855838-23042-1-git-send-email-rjui@broadcom.com>

Hi Kishon,

Is there any more change that you want me to make with this patch series?

Thanks,

Ray

On 9/21/2015 10:17 AM, Ray Jui wrote:
> This patch series adds support for the Cygnus PCIe PHY
> 
> This patch series is based on Linux v4.3-rc1 and is avaliable in:
> https://github.com/Broadcom/cygnus-linux/tree/cygnus-pcie-phy-v5
> 
> Changes from v4:
>  - Add comment to explain the required 50 ms wait after PCIe AFE is brought
> up
>  - Change some of 'dev_info' print to 'dev_dbg'
> 
> Changes from v3:
>  - Modify the driver to use child node to represent each PCIe PHY
>  - Update device tree binding document and examples accordingly
>  - Add owner filed in phy ops
> 
> Changes from v2:
>  - Dropped MDC/MDIO bus driver since it's not needed to enable/disable the
>    analog-front-end of the PCIe Serdes on Cygnus
>  - Optimized delay waiting for PCIe analog-front-end to be fully enabled
>  - Reduce the #phy-cell to 1 since now the MDIO PHY ID is not required
> 
> Changes from v1:
>  - Move the MDC/MDIO bus driver from drivers/phy/* to drivers/bus/*
>  - Make the PCIe PHY device node child node of the MDIO bus
>  - Change the PCIe PHY driver to tristate so it can be compiled as a module
>  - Other minor changes
> 
> Ray Jui (2):
>   dt-bindings: Add Cygnus PCIe PHY binding doc
>   phy: cygnus: pcie: Add Cygnus PCIe PHY support
> 
>  .../bindings/phy/brcm,cygnus-pcie-phy.txt          |  47 +++++
>  drivers/phy/Kconfig                                |   9 +
>  drivers/phy/Makefile                               |   1 +
>  drivers/phy/phy-bcm-cygnus-pcie.c                  | 213 +++++++++++++++++++++
>  4 files changed, 270 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt
>  create mode 100644 drivers/phy/phy-bcm-cygnus-pcie.c
> 

  parent reply	other threads:[~2015-09-28 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21 17:17 [PATCH v5 0/2] Add Cygnus PCIe Serdes/PHY support Ray Jui
2015-09-21 17:17 ` [PATCH v5 1/2] dt-bindings: Add Cygnus PCIe PHY binding doc Ray Jui
2015-09-21 17:17 ` [PATCH v5 2/2] phy: cygnus: pcie: Add Cygnus PCIe PHY support Ray Jui
2015-10-06 14:25   ` Kishon Vijay Abraham I
2015-10-06 17:13     ` Ray Jui
2015-10-06 19:20       ` Kishon Vijay Abraham I
2015-10-06 19:23         ` Florian Fainelli
2015-10-06 19:25           ` Kishon Vijay Abraham I
2015-10-06 19:23         ` Ray Jui
2015-10-06 19:25           ` Kishon Vijay Abraham I
2015-09-28 16:03 ` Ray Jui [this message]
2015-09-29 13:24   ` [PATCH v5 0/2] Add Cygnus PCIe Serdes/PHY support Kishon Vijay Abraham I

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=560964E8.8040507@broadcom.com \
    --to=rjui@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=arunp@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=jdzheng@broadcom.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).