From: Krzysztof Kozlowski <krzk@kernel.org>
To: Varadarajan Narayanan <quic_varada@quicinc.com>,
gregkh@linuxfoundation.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, quic_wcheng@quicinc.com,
quic_kriskura@quicinc.com, linux-arm-msm@vger.kernel.org,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: usb: qcom,dwc3: Update ipq5332 interrupt info
Date: Thu, 18 Jul 2024 08:23:28 +0200 [thread overview]
Message-ID: <fe83d463-b52a-44bc-b122-ed4fa4c20bf7@kernel.org> (raw)
In-Reply-To: <20240717094848.3536239-1-quic_varada@quicinc.com>
On 17/07/2024 11:48, Varadarajan Narayanan wrote:
> IPQ5332 has only three interrupts. Update the constraints
> to fix the following dt_binding_check errors.
>
> interrupt-names: ['pwr_event', 'dp_hs_phy_irq', 'dm_hs_phy_irq'] is too short
>
> Fixes: 53c6d854be4e ("dt-bindings: usb: dwc3: Clean up hs_phy_irq in binding")
> Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com>
> ---
> v2: Fix patch version numbering. Incorrectly marked the first version as v0
> Add interrupts and interrupt-names for ipq5332 instead of clubbing it with
> qcom,x1e80100-dwc3
> ---
> Documentation/devicetree/bindings/usb/qcom,dwc3.yaml | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> index 6c5f962bbcf9..5e5cc2175526 100644
> --- a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> @@ -235,6 +235,13 @@ allOf:
> - const: core
> - const: sleep
> - const: mock_utmi
> + interrupts:
> + maxItems: 3
> + interrupt-names:
> + items:
> + - const: pwr_event
> + - const: dp_hs_phy_irq
> + - const: dm_hs_phy_irq
Why are you duplicating interrupts for this variant? This is
qcom,ipq6018-dwc3, not 5332. Read carefully how the file is currently
organized - there is no entry which has clocks and interrupts at one
place. You are bringing inconsistency, why?
>
> - if:
> properties:
> @@ -442,7 +449,6 @@ allOf:
> compatible:
> contains:
> enum:
> - - qcom,ipq5332-dwc3
> - qcom,x1e80100-dwc3
So now 5332 does not have any constraints.
> then:
> properties:
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-18 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 9:48 [PATCH v2 1/2] dt-bindings: usb: qcom,dwc3: Update ipq5332 interrupt info Varadarajan Narayanan
2024-07-17 9:48 ` [PATCH v2 2/2] arm64: dts: qcom: ipq5332: Fix interrupt trigger type for usb Varadarajan Narayanan
2024-07-17 9:55 ` Konrad Dybcio
2024-07-17 15:15 ` Dmitry Baryshkov
2024-07-18 6:23 ` Krzysztof Kozlowski [this message]
2024-07-23 10:05 ` [PATCH v2 1/2] dt-bindings: usb: qcom,dwc3: Update ipq5332 interrupt info Varadarajan Narayanan
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=fe83d463-b52a-44bc-b122-ed4fa4c20bf7@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_kriskura@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=quic_wcheng@quicinc.com \
--cc=robh@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).