From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Krishna Kurapati <quic_kriskura@quicinc.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Conor Dooley <conor+dt@kernel.org>,
Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
quic_ppratap@quicinc.com, quic_jackp@quicinc.com
Subject: Re: [PATCH v5 1/2] dt-bindings: usb: dwc3: Clean up hs_phy_irq in binding
Date: Mon, 25 Dec 2023 14:05:39 +0100 [thread overview]
Message-ID: <e6419898-0d77-4286-a04b-7240eb90d8df@linaro.org> (raw)
In-Reply-To: <20231222063648.11193-2-quic_kriskura@quicinc.com>
On 22/12/2023 07:36, Krishna Kurapati wrote:
> The high speed related interrupts present on QC targets are as follows:
>
>
> interrupt-names:
> - minItems: 1
> - maxItems: 4
> + minItems: 2
> + maxItems: 5
>
> qcom,select-utmi-as-pipe-clk:
> description:
> @@ -361,60 +378,21 @@ allOf:
> compatible:
> contains:
> enum:
> - - qcom,ipq4019-dwc3
Why do you remove it, without adding it somewhere else. Nothing in the
commit msg explains it.
> + - qcom,ipq5018-dwc3
> - qcom,ipq6018-dwc3
> - - qcom,ipq8064-dwc3
> - qcom,ipq8074-dwc3
> - - qcom,msm8994-dwc3
> - - qcom,qcs404-dwc3
> - - qcom,sc7180-dwc3
> - - qcom,sdm670-dwc3
> - - qcom,sdm845-dwc3
> - - qcom,sdx55-dwc3
> - - qcom,sdx65-dwc3
> - - qcom,sdx75-dwc3
> - - qcom,sm4250-dwc3
> - - qcom,sm6350-dwc3
> - - qcom,sm8150-dwc3
> - - qcom,sm8250-dwc3
> - - qcom,sm8350-dwc3
> - - qcom,sm8450-dwc3
> - - qcom,sm8550-dwc3
> - - qcom,sm8650-dwc3
> - then:
> - properties:
> - interrupts:
> - items:
> - - description: The interrupt that is asserted
> - when a wakeup event is received on USB2 bus.
> - - description: The interrupt that is asserted
> - when a wakeup event is received on USB3 bus.
> - - description: Wakeup event on DM line.
> - - description: Wakeup event on DP line.
> - interrupt-names:
> - items:
> - - const: hs_phy_irq
> - - const: ss_phy_irq
> - - const: dm_hs_phy_irq
> - - const: dp_hs_phy_irq
> -
> - - if:
> - properties:
> - compatible:
> - contains:
> - enum:
> - qcom,msm8953-dwc3
> - - qcom,msm8996-dwc3
> - qcom,msm8998-dwc3
> - - qcom,sm6115-dwc3
> - - qcom,sm6125-dwc3
> + - qcom,qcm2290-dwc3
> then:
> properties:
> interrupts:
> - maxItems: 2
> + minItems: 2
> + maxItems: 3
> interrupt-names:
> items:
> - - const: hs_phy_irq
> + - const: pwr_event
> + - const: qusb2_phy
> - const: ss_phy_irq
>
> - if:
> @@ -422,37 +400,21 @@ allOf:
> compatible:
> contains:
> enum:
> - - qcom,ipq5018-dwc3
> - - qcom,ipq5332-dwc3
> + - qcom,msm8996-dwc3
> + - qcom,qcs404-dwc3
> - qcom,sdm660-dwc3
> - then:
> - properties:
> - interrupts:
> - minItems: 1
> - maxItems: 2
> - interrupt-names:
> - minItems: 1
> - items:
> - - const: hs_phy_irq
> - - const: ss_phy_irq
> -
> - - if:
> - properties:
> - compatible:
> - contains:
> - enum:
> - - qcom,sc7280-dwc3
> + - qcom,sm6115-dwc3
> + - qcom,sm6125-dwc3
> then:
> properties:
> interrupts:
> minItems: 3
> maxItems: 4
> interrupt-names:
> - minItems: 3
> items:
> + - const: pwr_event
> - const: hs_phy_irq
> - - const: dp_hs_phy_irq
> - - const: dm_hs_phy_irq
> + - const: qusb2_phy
Why qusb2_phy is after hs_phy_irq? In the earlier if:then: it is the
second one.
> - const: ss_phy_irq
>
> - if:
> @@ -460,11 +422,13 @@ allOf:
> compatible:
> contains:
> enum:
> + - qcom,ipq5332-dwc3
> - qcom,sc8280xp-dwc3
> - qcom,x1e80100-dwc3
> then:
> properties:
> interrupts:
> + minItems: 3
Hm, why? This commit is unmanageable. Your commit msg is already huge
but still does not explain this. Are you sure you are fixing only one
logical thing per patch? Does not look like.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-25 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 6:36 [PATCH v5 0/2] Refine USB interrupt vectors on Qualcomm platforms Krishna Kurapati
2023-12-22 6:36 ` [PATCH v5 1/2] dt-bindings: usb: dwc3: Clean up hs_phy_irq in binding Krishna Kurapati
2023-12-25 13:05 ` Krzysztof Kozlowski [this message]
2023-12-26 5:37 ` Krishna Kurapati PSSNV
2023-12-26 9:33 ` Krzysztof Kozlowski
2023-12-26 10:03 ` Krishna Kurapati PSSNV
2023-12-26 12:22 ` Krzysztof Kozlowski
2023-12-26 15:03 ` Krishna Kurapati PSSNV
2023-12-26 19:04 ` Krzysztof Kozlowski
2023-12-27 2:18 ` Krishna Kurapati PSSNV
2024-01-03 14:52 ` Krishna Kurapati PSSNV
2023-12-22 6:36 ` [PATCH v5 2/2] usb: dwc3: qcom: Rename hs_phy_irq to qusb2_phy_irq Krishna Kurapati
2023-12-22 22:14 ` Thinh Nguyen
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=e6419898-0d77-4286-a04b-7240eb90d8df@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan@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-usb@vger.kernel.org \
--cc=quic_jackp@quicinc.com \
--cc=quic_kriskura@quicinc.com \
--cc=quic_ppratap@quicinc.com \
--cc=quic_wcheng@quicinc.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