From: Ray Jui <ray.jui@broadcom.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Ray Jui <ray.jui@broadcom.com>
Subject: [PATCH v4 0/2] Add Broadcom Stingray PCIe PHY support
Date: Fri, 6 Jul 2018 17:18:31 -0700 [thread overview]
Message-ID: <1530922713-22964-1-git-send-email-ray.jui@broadcom.com> (raw)
This patch series adds PCIe PHY support for both PAXB and PAXC root complex in
Broadcom Stingray SOC
This patch series is based off v4.18-rc3 and is available on GIHUB:
repo: https://github.com/Broadcom/arm64-linux.git
branch: sr-pcie-phy-v4
Changes since v3:
- Add missing node unit address in binding document
- Remove redundant dummy PHY callbacks in the driver
- Other miscellaneous minor fixes based on feedback from Kishon
Changes since v2:
- Add 'reg' property to the driver so it can access the PCIe SS PHY block
- Rebase to v4.18-rc3
Changes since v1:
- Rebase from v4.17-rc5 to v4.18-rc1
Ray Jui (2):
dt-bindings: phy: Add binding doc for Stingray PCIe PHY
phy: bcm-sr-pcie: Add Stingray PCIe PHY driver
.../devicetree/bindings/phy/brcm,sr-pcie-phy.txt | 41 +++
drivers/phy/broadcom/Kconfig | 10 +
drivers/phy/broadcom/Makefile | 2 +
drivers/phy/broadcom/phy-bcm-sr-pcie.c | 305 +++++++++++++++++++++
4 files changed, 358 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/brcm,sr-pcie-phy.txt
create mode 100644 drivers/phy/broadcom/phy-bcm-sr-pcie.c
--
2.1.4
next reply other threads:[~2018-07-07 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 0:18 Ray Jui [this message]
2018-07-07 0:18 ` [PATCH v4 1/2] dt-bindings: phy: Add binding doc for Stingray PCIe PHY Ray Jui
2018-07-07 0:18 ` [PATCH v4 2/2] phy: bcm-sr-pcie: Add Stingray PCIe PHY driver 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=1530922713-22964-1-git-send-email-ray.jui@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).