From: Johan Hovold <johan@kernel.org>
To: Krishna Kurapati PSSNV <quic_kriskura@quicinc.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Conor Dooley <conor+dt@kernel.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Felipe Balbi <balbi@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_ppratap@quicinc.com, quic_jackp@quicinc.com
Subject: Re: [PATCH v15 2/9] usb: dwc3: core: Access XHCI address space temporarily to read port info
Date: Mon, 4 Mar 2024 09:40:56 +0100 [thread overview]
Message-ID: <ZeWJGCsUiZFw6ECl@hovoldconsulting.com> (raw)
In-Reply-To: <c4607aa4-7af7-443f-8ccc-aa4fe3ede3cc@quicinc.com>
On Thu, Feb 29, 2024 at 05:23:08PM +0530, Krishna Kurapati PSSNV wrote:
> On 2/29/2024 3:17 PM, Johan Hovold wrote:
> > On Fri, Feb 16, 2024 at 06:27:49AM +0530, Krishna Kurapati wrote:
> >> Currently Multiport DWC3 controllers are host-only capable.
> >
> > I already asked you to rephrase this so that it becomes clear that you
> > are describing a property of the current hardware (and similar
> > throughout the series):
> >
> > https://lore.kernel.org/all/ZTI7AtCJWgAnACSh@hovoldconsulting.com/
> IMO, the statement is describing a property unique to current hardware,
> that "If it is a multiport controller, it is then host-only capable"
>
> I used the word "Currently" to indicate that "Today, the multiport
> devices present...". Let me know if there is any ambiguity in the sentence.
>
> In v13, I wrote:
> "Currently host-only capable DWC3 controllers support Multiport."
> You were right. It was ambiguous as it might refer to even single port
> controllers.
>
> So I changed it saying all the DWC3 multiport controllers are host only
> capable.
>
> How about:
>
> "All the DWC3 Multi Port controllers that exist today only support host
> mode"
That should be clear enough, thanks.
> >> + /*
> >> + * Currently only DWC3 controllers that are host-only capable
> >> + * support Multiport.
> >> + */
> >
> > So again, also here, rephrase the comment so that it is clear that you
> > are referring to a property of the current hardware.
>
> I put the comment this way to indicate that we don't want to check for
> existence of multiple ports if the controller is not "host-only"
> capable. We should only check for multport support only if we are
> host-only capable. I think the statement clearly tells that "check for
> host-only" configuration before proceeding to check for xhci register reads.
Fair enough, this comment could be considered to apply only to the
implementation. Perhaps the following would be more clear though:
Currently only DWC3 controllers that are host-only capable
can have more than one port.
or simply
Host-only capable controllers can have more than one port.
Both of these also gives a hint that this is a property of the hardware.
> I replied the same on:
> https://lore.kernel.org/all/279a54f2-7260-4270-83c7-d6f5c5ba0873@quicinc.com/
>
> And since you didn't mention anything else at this part of code in your
> return reply in:
> https://lore.kernel.org/all/ZTYyXhyZN3jBXEfm@hovoldconsulting.com/
I left in the following quote on purpose in that reply:
> > Please rephrase accordingly throughout so that this becomes clear.
Johan
next prev parent reply other threads:[~2024-03-04 8:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 0:57 [PATCH v15 0/9] Add multiport support for DWC3 controllers Krishna Kurapati
2024-02-16 0:57 ` [PATCH v15 1/9] dt-bindings: usb: Add bindings for multiport properties on DWC3 controller Krishna Kurapati
2024-02-16 0:57 ` [PATCH v15 2/9] usb: dwc3: core: Access XHCI address space temporarily to read port info Krishna Kurapati
2024-02-29 9:47 ` Johan Hovold
2024-02-29 11:53 ` Krishna Kurapati PSSNV
2024-03-04 8:40 ` Johan Hovold [this message]
2024-02-16 0:57 ` [PATCH v15 3/9] usb: dwc3: core: Skip setting event buffers for host only controllers Krishna Kurapati
2024-02-16 0:57 ` [PATCH v15 4/9] usb: dwc3: core: Refactor PHY logic to support Multiport Controller Krishna Kurapati
2024-03-01 13:50 ` Johan Hovold
2024-02-16 0:57 ` [PATCH v15 5/9] dt-bindings: usb: qcom,dwc3: Add bindings for SC8280 Multiport Krishna Kurapati
2024-02-16 0:57 ` [PATCH v15 6/9] usb: dwc3: qcom: Add helper function to request wakeup interrupts Krishna Kurapati
2024-02-16 0:57 ` [PATCH v15 7/9] usb: dwc3: qcom: Refactor IRQ handling in glue driver Krishna Kurapati
2024-03-01 13:53 ` Johan Hovold
2024-03-05 15:39 ` Krishna Kurapati PSSNV
2024-02-16 0:57 ` [PATCH v15 8/9] usb: dwc3: qcom: Enable wakeup for applicable ports of multiport Krishna Kurapati
2024-03-01 15:43 ` Johan Hovold
2024-02-16 0:57 ` [PATCH v15 9/9] usb: dwc3: qcom: Add multiport suspend/resume support for wrapper Krishna Kurapati
2024-03-01 15:55 ` Johan Hovold
2024-02-17 17:39 ` [PATCH v15 0/9] Add multiport support for DWC3 controllers Greg Kroah-Hartman
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=ZeWJGCsUiZFw6ECl@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=andersson@kernel.org \
--cc=balbi@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).