From: Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@linaro.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Johan Hovold <johan@kernel.org>,
Bjorn Andersson <quic_bjorande@quicinc.com>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
<quic_ppratap@quicinc.com>, <quic_jackp@quicinc.com>,
Andy Gross <agross@kernel.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: usb: dwc3: Clean up hs_phy_irq in binding
Date: Wed, 27 Dec 2023 07:48:14 +0530 [thread overview]
Message-ID: <a2108be4-5f35-4625-9c80-e7d6db978bab@quicinc.com> (raw)
In-Reply-To: <1f8fdd47-0c48-4ccd-9352-41c830ec9240@linaro.org>
On 12/27/2023 12:34 AM, Krzysztof Kozlowski wrote:
> On 26/12/2023 16:03, Krishna Kurapati PSSNV wrote:
>>
>>
>> On 12/26/2023 5:52 PM, Krzysztof Kozlowski wrote:
>>
>>>>>
>>>>> This does not answer why, you sc8280xp and x1e80100 not get one optional
>>>>> interrupt. I asked "why" you are doing this change. Why do you need it?
>>>>> What is the rationale?
>>>>>
>>>>> Then I grunted about unmanageable commit, because all my troubles to
>>>>> review it are the effect of it: it is very difficult to read. It is also
>>>>> difficult for you, because you keep making here mistakes. So if you
>>>>> cannot write this commit properly and I cannot review it, then it is way
>>>>> over-complicated, don't you think? But this is still second problem
>>>>> here, don't ignore the fist - "why?"
>>>>
>>>> HI Krzysztof,
>>>>
>>>> Thanks for the review.
>>>> To answer the question,
>>>>
>>>> "why ?" : The interrupts have been mis-interpreted on many platforms or
>>>> many interrupts are missing.
>>>
>>> I asked about these two specific platforms. Please explain these
>>> changes. Above is so generic that tells me nothing.
>>>
>>
>> Is the question, "Why do x1e80100 and sc8280 don't have hs_phy_irq ?"
>
> No, not entirely, the question was why these have flexible number of
> IRQs (last one optional)?
>
>
>> If so, I checked the SC8280 HW specifics and I see one small error. The
>> name was printed wrong. I got it from another source. Will move sc8280
>> to list having 5 interrupts. As per x1e80100, I wasn't able to get my
>> hands on the hw specifics and I followed the following link by Abel Vesa:
>>
>> https://lore.kernel.org/r/20231214-x1e80100-usb-v1-1-c22be5c0109e@linaro.org
>>
>> As per the above patch, x1e80100 had only 4 interrupts.
>
> Hm, ok, you say "4" but your patch says "minItems: 3". 3 != 4.
>
Actually, you are right. We don't need the max/min items as we are sure
that the targets mentioned under this have 4 interrupts definitively.
But the optional interrupt was put in just in case any target comes in
that has no ss_phy and no hs_phy and has only the other 3 interrupts.
Since those targets are not present currently, I will remove the max/min
items from this.
Thanks for the catch. Sorry for bothering you with a couple of mails
because I didn't understand the question you were trying to ask.
Regards,
Krishna,
next prev parent reply other threads:[~2023-12-27 2:18 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
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 [this message]
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=a2108be4-5f35-4625-9c80-e7d6db978bab@quicinc.com \
--to=quic_kriskura@quicinc.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=agross@kernel.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=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_jackp@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