Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Johan Hovold <johan+linaro@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	vkoul@kernel.org, devicetree@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andy Gross <agross@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	Bjorn Andersson <andersson@kernel.org>
Subject: Re: [PATCH v5 1/6] dt-bindings: phy: Add qcom,snps-eusb2-phy schema file
Date: Tue, 7 Feb 2023 12:44:15 -0600	[thread overview]
Message-ID: <167579545552.3956607.9337813365247017487.robh@kernel.org> (raw)
In-Reply-To: <20230207114024.944314-2-abel.vesa@linaro.org>


On Tue, 07 Feb 2023 13:40:19 +0200, Abel Vesa wrote:
> The SM8550 SoC uses Synopsis eUSB2 PHY. Add a dt-binding schema
> for the new driver.
> 
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> ---
> 
> There will be a binding check warning from Rob's bot because of the tcsr
> clock bindings missing (dt-bindings/clock/qcom,sm8550-tcsr.h), but that
> is expected as the header is already merged through Bjorn's clocks tree.
> 
> The v4 version of this patch was here:
> https://lore.kernel.org/all/20230202132511.3983095-2-abel.vesa@linaro.org/
> 
> Changes since v4:
>  * none
> 
> Changes since v3:
>  * removed blank line, like Rob suggested
>  * dropped quotes and reset description, like Rob suggested
>  * dropped the RPMH_CXO_PAD_CLK clock and the ref_src clock name
>    to match the schema
>  * fixed filenames of the includes in the example (sm8550-gcc and
>    sm8550-tcsr)
> 
> Changes since v2:
>  * none
> 
> Changes since v1:
>  * dropped the "ref src" clock
>  * dropped the usb-repeater property
> 
> 
>  .../bindings/phy/qcom,snps-eusb2-phy.yaml     | 74 +++++++++++++++++++
>  1 file changed, 74 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/phy/qcom,snps-eusb2-phy.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>


  reply	other threads:[~2023-02-07 18:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 11:40 [PATCH v5 0/6] sm8550: Add USB HC and PHYs support Abel Vesa
2023-02-07 11:40 ` [PATCH v5 1/6] dt-bindings: phy: Add qcom,snps-eusb2-phy schema file Abel Vesa
2023-02-07 18:44   ` Rob Herring [this message]
2023-02-07 11:40 ` [PATCH v5 2/6] phy: qcom: Add QCOM SNPS eUSB2 driver Abel Vesa
2023-02-07 11:40 ` [PATCH v5 3/6] dt-bindings: phy: qcom,sc8280xp-qmp-usb43dp: Document SM8550 compatible Abel Vesa
2023-02-07 11:40 ` [PATCH v5 4/6] phy: qcom-qmp: pcs-usb: Add v6 register offsets Abel Vesa
2023-02-07 11:40 ` [PATCH v5 5/6] phy: qcom-qmp: Add v6 DP " Abel Vesa
2023-02-07 11:40 ` [PATCH v5 6/6] phy: qcom-qmp-combo: Add support for SM8550 Abel Vesa
2023-02-08 17:12   ` Johan Hovold

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=167579545552.3956607.9337813365247017487.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=kishon@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.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