From: "Rob Herring (Arm)" <robh@kernel.org>
To: Varadarajan Narayanan <quic_varada@quicinc.com>
Cc: linux-kernel@vger.kernel.org, konrad.dybcio@linaro.org,
quic_kriskura@quicinc.com, conor+dt@kernel.org,
linux-usb@vger.kernel.org, andersson@kernel.org,
devicetree@vger.kernel.org, quic_wcheng@quicinc.com,
linux-arm-msm@vger.kernel.org, gregkh@linuxfoundation.org,
krzk+dt@kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: usb: qcom,dwc3: Update ipq5332 interrupt info
Date: Tue, 23 Jul 2024 16:25:36 -0500 [thread overview]
Message-ID: <172176993521.1129772.4265722303661810586.robh@kernel.org> (raw)
In-Reply-To: <20240723100151.402300-2-quic_varada@quicinc.com>
On Tue, 23 Jul 2024 15:31:50 +0530, 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>
> ---
> v3: In the previous version, the hunk got mixed up while rebasing.
> Fix that
>
> 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
> ---
> .../devicetree/bindings/usb/qcom,dwc3.yaml | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-07-23 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 10:01 [PATCH v3 0/2] Fix ipq5332 usb interrupt trigger type Varadarajan Narayanan
2024-07-23 10:01 ` [PATCH v3 1/2] dt-bindings: usb: qcom,dwc3: Update ipq5332 interrupt info Varadarajan Narayanan
2024-07-23 21:25 ` Rob Herring (Arm) [this message]
2024-07-23 10:01 ` [PATCH v3 2/2] arm64: dts: qcom: ipq5332: Fix interrupt trigger type for usb Varadarajan Narayanan
2024-07-29 3:58 ` (subset) [PATCH v3 0/2] Fix ipq5332 usb interrupt trigger type Bjorn Andersson
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=172176993521.1129772.4265722303661810586.robh@kernel.org \
--to=robh@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 \
/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).