[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <814824d9-9509-4b5d-84ad-de0cbf5808a0@quicinc.com>
Date: Wed, 3 Jan 2024 20:22:15 +0530
From: Krishna Kurapati PSSNV <quic_kriskura@...cinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Krzysztof Kozlowski
<krzysztof.kozlowski+dt@...aro.org>,
Wesley Cheng <quic_wcheng@...cinc.com>
CC: <linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Conor Dooley
<conor+dt@...nel.org>, Rob Herring <robh+dt@...nel.org>,
Greg Kroah-Hartman
<gregkh@...uxfoundation.org>,
<linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
Thinh Nguyen <Thinh.Nguyen@...opsys.com>, <quic_ppratap@...cinc.com>,
<quic_jackp@...cinc.com>, Andy Gross
<agross@...nel.org>,
Johan Hovold <johan@...nel.org>,
Konrad Dybcio
<konrad.dybcio@...aro.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: usb: dwc3: Clean up hs_phy_irq in
binding
>>>> 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.
>>>
>>
>> In v3 as well, the hs_phy_irq is before qusb2_phy interrupt:
>> https://lore.kernel.org/all/20231211121124.4194-2-quic_kriskura@quicinc.com/
>
> ? How v3 matters?
>
I was thinking whether I modified the order between v3 and v5 and didn't
mention in change log and hence I compared with v3. Thanks for the catch.
I made qusb2_phy the second one in the list and pushed v6:
https://lore.kernel.org/all/20231227091951.685-1-quic_kriskura@quicinc.com/
Can you help provide you review on v6 as well.
Regards,
Krishna,
Powered by blists - more mailing lists