From: Shawn Guo <shawn.guo@linaro.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Sriharsha Allenki <sallenki@codeaurora.org>,
Anu Ramanathan <anur@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] phy: qualcomm: Add Synopsys High-Speed USB PHY driver
Date: Mon, 17 Dec 2018 08:34:40 +0800 [thread overview]
Message-ID: <20181217003434.GA7208@dragon> (raw)
In-Reply-To: <20181204060104.GA11391@dragon>
On Tue, Dec 04, 2018 at 02:01:07PM +0800, Shawn Guo wrote:
> Hi Kishon,
>
> On Tue, Dec 04, 2018 at 10:38:19AM +0530, Kishon Vijay Abraham I wrote:
> > Hi,
> >
> > On 27/11/18 3:37 PM, Shawn Guo wrote:
> > > It adds Synopsys 28nm Femto High-Speed USB PHY driver support, which
> > > is usually paired with Synopsys DWC3 USB controllers on Qualcomm SoCs.
> >
> > Is this Synopsys PHY specific to Qualcomm or could it be used by other vendors
> > (with just changing tuning parameters)? If it could be used by other vendors
> > then it would make sense to add this PHY driver in synopsys directory.
>
> My knowledge is that this Synopsys PHY is specific to Qualcomm SoCs.
> @Sriharsha, correct me if I'm wrong.
Kishon,
Do you have any further comments on the patches? We are close the 4.21
merge window, and I really hope they can hit mainline with 4.21 release.
Thanks.
Shawn
next prev parent reply other threads:[~2018-12-17 0:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 10:07 [PATCH v5 0/2] Add Synopsys High-Speed USB PHY driver for Qualcomm SoCs Shawn Guo
2018-11-27 10:07 ` [PATCH v5 1/2] dt-bindings: phy: Add Qualcomm Synopsys High-Speed USB PHY binding Shawn Guo
2018-11-27 10:07 ` [PATCH v5 2/2] phy: qualcomm: Add Synopsys High-Speed USB PHY driver Shawn Guo
2018-12-04 5:08 ` Kishon Vijay Abraham I
2018-12-04 6:01 ` Shawn Guo
2018-12-17 0:34 ` Shawn Guo [this message]
2018-12-18 14:16 ` Kishon Vijay Abraham I
2018-12-19 1:07 ` Shawn Guo
2018-12-19 18:49 ` Jack Pham
2018-12-20 0:47 ` Shawn Guo
2018-12-19 20:01 ` Jack Pham
2018-12-20 0:48 ` Shawn Guo
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=20181217003434.GA7208@dragon \
--to=shawn.guo@linaro.org \
--cc=anur@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sallenki@codeaurora.org \
--cc=vkoul@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).