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
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to