From: Scott Branden <scott.branden@broadcom.com>
To: Srinath Mannam <srinath.mannam@broadcom.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Kishon Vijay Abraham I <kishon@ti.com>
Cc: Tejun Heo <tj@kernel.org>,
Jayachandran C <jnair@caviumnetworks.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/3] Stingray USB PHY driver support
Date: Tue, 19 Mar 2019 11:38:28 -0700 [thread overview]
Message-ID: <7490f894-3c0b-c7cd-5ff0-4eea6ea2c199@broadcom.com> (raw)
In-Reply-To: <1552986944-3398-1-git-send-email-srinath.mannam@broadcom.com>
Thanks Srinath and Rob - patch series looks good now.
patch series,
Acked-by: Scott Branden <scott.branden@broadcom.com>
On 2019-03-19 2:15 a.m., Srinath Mannam wrote:
> These patches add Stingray USB PHY driver and its corresponding
> DT nodes with documentation.
>
> This patch set is based on Linux-5.0-rc2.
>
> Changes from v5:
> - Removed redundant address and size cells in DT nodes.
>
> Changes from v4:
> - Addressed Rob Herring review comments
> - Removed child nodes and added #phy-cells 1
> - Added xlate function to get phy using phandle argument.
>
> Changes from v3:
> - Addressed Rob Herring review comments
> - Changed compatible strings.
> - updated driver based on new compatible strings.
>
> Changes from v2:
> - Addressed Kishon review comments
> - Updated patchset to Linux-5.0-rc2
>
> Changes from v1:
> - Addressed Kishon review comments
> - phy init call return value handle
>
> Srinath Mannam (3):
> dt-bindings: phy: Add Stingray USB PHY binding document
> phy: sr-usb: Add Stingray USB PHY driver
> arm64: dts: Add USB DT nodes for Stingray SoC
>
> .../bindings/phy/brcm,stingray-usb-phy.txt | 32 ++
> .../boot/dts/broadcom/stingray/stingray-usb.dtsi | 72 ++++
> .../arm64/boot/dts/broadcom/stingray/stingray.dtsi | 1 +
> drivers/phy/broadcom/Kconfig | 11 +
> drivers/phy/broadcom/Makefile | 1 +
> drivers/phy/broadcom/phy-bcm-sr-usb.c | 393 +++++++++++++++++++++
> 6 files changed, 510 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/brcm,stingray-usb-phy.txt
> create mode 100644 arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi
> create mode 100644 drivers/phy/broadcom/phy-bcm-sr-usb.c
>
next prev parent reply other threads:[~2019-03-19 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 9:15 [PATCH v6 0/3] Stingray USB PHY driver support Srinath Mannam
2019-03-19 9:15 ` [PATCH v6 1/3] dt-bindings: phy: Add Stingray USB PHY binding document Srinath Mannam
2019-03-19 9:15 ` [PATCH v6 2/3] phy: sr-usb: Add Stingray USB PHY driver Srinath Mannam
2019-03-19 9:15 ` [PATCH v6 3/3] arm64: dts: Add USB DT nodes for Stingray SoC Srinath Mannam
2019-03-26 17:23 ` Florian Fainelli
2019-03-19 18:38 ` Scott Branden [this message]
2019-03-22 16:42 ` [PATCH v6 0/3] Stingray USB PHY driver support Florian Fainelli
2019-03-26 7:29 ` Kishon Vijay Abraham I
2019-03-26 8:17 ` Srinath Mannam
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=7490f894-3c0b-c7cd-5ff0-4eea6ea2c199@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=jnair@caviumnetworks.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinath.mannam@broadcom.com \
--cc=tj@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).