From: Vinod Koul <vkoul@kernel.org>
To: Jack Pham <jackp@codeaurora.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Wesley Cheng <wcheng@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Manu Gautam <mgautam@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: phy: qcom,qmp: Add SM8150, SM8250 and SM8350 USB PHY bindings
Date: Tue, 19 Jan 2021 20:32:47 +0530 [thread overview]
Message-ID: <20210119150247.GX2771@vkoul-mobl> (raw)
In-Reply-To: <20210115174723.7424-2-jackp@codeaurora.org>
On 15-01-21, 09:47, Jack Pham wrote:
> Add the compatible strings for the USB3 PHYs found on SM8150, SM8250
> and SM8350 SoCs. These require separate subschemas due to the different
> required clock entries.
>
> Note the SM8150 and SM8250 compatibles have already been in place in
> the dts as well as the driver implementation but were missing from
> the documentation.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2021-01-19 18:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 17:47 [PATCH v2 0/4] SM8350 USB and dt-bindings updates Jack Pham
2021-01-15 17:47 ` [PATCH v2 1/4] dt-bindings: phy: qcom,qmp: Add SM8150, SM8250 and SM8350 USB PHY bindings Jack Pham
2021-01-18 5:03 ` Bjorn Andersson
2021-01-19 15:02 ` Vinod Koul [this message]
2021-01-15 17:47 ` [PATCH v2 2/4] phy: qcom-qmp: Add SM8350 USB QMP PHYs Jack Pham
2021-01-18 5:04 ` Bjorn Andersson
2021-01-19 15:03 ` Vinod Koul
2021-01-15 17:47 ` [PATCH v2 3/4] dt-bindings: phy: qcom,usb-snps-femto-v2: Add SM8250 and SM8350 bindings Jack Pham
2021-01-18 5:05 ` Bjorn Andersson
2021-01-19 15:03 ` Vinod Koul
2021-01-15 17:47 ` [PATCH v2 4/4] dt-bindings: usb: qcom,dwc3: Add bindings for SM8150, SM8250, SM8350 Jack Pham
2021-01-18 5:05 ` Bjorn Andersson
2021-01-18 11:39 ` Felipe Balbi
2021-01-19 15:03 ` Vinod Koul
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=20210119150247.GX2771@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jackp@codeaurora.org \
--cc=kishon@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgautam@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=wcheng@codeaurora.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).