Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Varadarajan Narayanan" <varadarajan.narayanan@oss.qualcomm.com>
Cc: linux-phy@lists.infradead.org, vkoul@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	neil.armstrong@linaro.org, olteanv@gmail.com, robh@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 5/5] phy: qcom-qusb2: add QUSB2 support for ipq5210
Date: Fri, 15 May 2026 11:28:09 +0000	[thread overview]
Message-ID: <20260515112809.EE5B9C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260515-usb2phy-v1-5-5f8338d466bf@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message incorrectly describes the patch contents. It claims to add an init sequence for 'Super Speed ports', but the patch actually modifies the QUSB2 PHY driver, which is responsible for USB 2.0 (High Speed / Full Speed / Low Speed) ports. Furthermore, the patch does not introduce a new initialization sequence; it simply maps the new `qcom,ipq5210-qusb2-phy` compatible string to the existing `ipq6018_phy_cfg` data.
--

commit a327055af09a1520cf8f88735b110f1df7674e64
Author: Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>

phy: qcom-qusb2: add QUSB2 support for ipq5210

This commit adds a new compatible string for the IPQ5210 SoC to the QUSB2
PHY driver. It maps the new compatible string to the existing
ipq6018_phy_cfg data structure.

> Add the phy init sequence for the Super Speed ports found
> on ipq5210.

Does this commit message accurately describe the patch contents?

The QUSB2 PHY driver is responsible for USB 2.0 ports, rather than Super
Speed ports. Additionally, the patch maps the compatible string to the
existing ipq6018_phy_cfg data instead of adding a new initialization
sequence.

Could the commit message be updated to reflect that it adds USB 2.0 PHY
support?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260515-usb2phy-v1-0-5f8338d466bf@oss.qualcomm.com?part=5

      reply	other threads:[~2026-05-15 11:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 10:47 [PATCH 0/5] Enable ipq5210 USB support Varadarajan Narayanan
2026-05-15 10:47 ` [PATCH 1/5] dt-bindings: phy: qcom,qusb2: Document ipq5210 compatible Varadarajan Narayanan
2026-05-15 10:47 ` [PATCH 2/5] dt-bindings: phy: qcom,qmp-usb: Add ipq5210 USB3 PHY Varadarajan Narayanan
2026-05-15 11:13   ` sashiko-bot
2026-05-15 10:47 ` [PATCH 3/5] dt-bindings: usb: qcom,dwc3: Add ipq5210 to USB DWC3 bindings Varadarajan Narayanan
2026-05-15 11:05   ` Krzysztof Kozlowski
2026-05-15 11:18   ` sashiko-bot
2026-05-15 10:47 ` [PATCH 4/5] phy: qcom: qmp: Enable ipq5210 support Varadarajan Narayanan
2026-05-15 11:29   ` Konrad Dybcio
2026-05-15 10:47 ` [PATCH 5/5] phy: qcom-qusb2: add QUSB2 support for ipq5210 Varadarajan Narayanan
2026-05-15 11:28   ` sashiko-bot [this message]

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=20260515112809.EE5B9C2BCB0@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=varadarajan.narayanan@oss.qualcomm.com \
    --cc=vkoul@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