public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Jui <rjui@broadcom.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: <linux-kernel@vger.kernel.org>,
	"JD (Jiandong) Zheng" <jdzheng@broadcom.com>,
	Arun Parameswaran <arunp@broadcom.com>,
	<bcm-kernel-feedback-list@broadcom.com>,
	Ray Jui <rjui@broadcom.com>
Subject: [PATCH 0/5] Add Cygnus PCIe PHY support
Date: Tue, 19 May 2015 18:23:29 -0700	[thread overview]
Message-ID: <1432085014-20758-1-git-send-email-rjui@broadcom.com> (raw)

This patch series adds support for the Cygnus PCIe PHY and support of MDC/MDIO
interface found in various iProc based of SoCs. The iProc MDC/MDIO interface
can be used by the host processor to communicate with various internal
Serdes/PHYs including Ethernet, PCIe, USB, etc.

This patch series is based on Linux v4.1-rc4 and is avaliable in:
https://github.com/Broadcom/cygnus-linux/tree/cygnus-pcie-phy-v1

Ray Jui (5):
  phy: iproc-mdio: Define DT binding
  phy: iproc-mdio: Initial iProc MDC/MDIO support
  phy: cygnus: pcie: Define DT binding
  phy: cygnus: pcie: Add Cygnus PCIe PHY support
  ARM: dts: enable PCIe PHY support for Cygnus

 .../bindings/phy/brcm,cygnus-pcie-phy.txt          |   31 ++
 .../devicetree/bindings/phy/brcm,iproc-mdio.txt    |   15 +
 arch/arm/boot/dts/bcm-cygnus.dtsi                  |   17 +
 drivers/phy/Kconfig                                |   27 ++
 drivers/phy/Makefile                               |    2 +
 drivers/phy/phy-cygnus-pcie.c                      |  340 ++++++++++++++++++++
 drivers/phy/phy-iproc-mdio.c                       |  249 ++++++++++++++
 include/linux/phy/iproc_mdio_phy.h                 |   22 ++
 8 files changed, 703 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt
 create mode 100644 Documentation/devicetree/bindings/phy/brcm,iproc-mdio.txt
 create mode 100644 drivers/phy/phy-cygnus-pcie.c
 create mode 100644 drivers/phy/phy-iproc-mdio.c
 create mode 100644 include/linux/phy/iproc_mdio_phy.h

-- 
1.7.9.5


             reply	other threads:[~2015-05-20  1:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  1:23 Ray Jui [this message]
2015-05-20  1:23 ` [PATCH 1/5] phy: iproc-mdio: Define DT binding Ray Jui
2015-05-21 13:07   ` Kishon Vijay Abraham I
2015-05-21 21:29     ` Ray Jui
2015-05-20  1:23 ` [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support Ray Jui
2015-05-21  7:41   ` Paul Bolle
2015-05-21 23:52     ` Ray Jui
2015-05-22  8:39       ` Paul Bolle
2015-05-21 13:12   ` Kishon Vijay Abraham I
2015-05-21 21:35     ` Ray Jui
2015-05-21 21:51       ` Florian Fainelli
2015-05-21 22:02         ` Ray Jui
2015-05-20  1:23 ` [PATCH 3/5] phy: cygnus: pcie: Define DT binding Ray Jui
2015-05-21 13:14   ` Kishon Vijay Abraham I
2015-05-21 21:59     ` Ray Jui
2015-05-21 23:36       ` Ray Jui
2015-05-20  1:23 ` [PATCH 4/5] phy: cygnus: pcie: Add Cygnus PCIe PHY support Ray Jui
2015-05-21  7:52   ` Paul Bolle
2015-05-21 23:53     ` Ray Jui
2015-05-22  8:47       ` Paul Bolle
2015-05-21 13:19   ` Kishon Vijay Abraham I
2015-05-20  1:23 ` [PATCH 5/5] ARM: dts: enable PCIe PHY support for Cygnus Ray Jui

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=1432085014-20758-1-git-send-email-rjui@broadcom.com \
    --to=rjui@broadcom.com \
    --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