Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Matthew Leung" <matthew.leung@oss.qualcomm.com>
Cc: conor+dt@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	neil.armstrong@linaro.org, olteanv@gmail.com,
	linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	vkoul@kernel.org
Subject: Re: [PATCH 09/10] phy: qcom-qmp: pcs-pcie: Add v10.60 register offsets
Date: Fri, 08 May 2026 23:38:01 +0000	[thread overview]
Message-ID: <20260508233802.20366C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260508-hawi-phy-pcie-v1-9-237b894353fc@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The macro `QPHY_PCIE_V10_60_PCS_PCS_TX_RX_CONFIG` contains a redundant `PCS_` substring.
--

commit fa9d92bd2f41dd643566d490312c4a18a8a68214
Author: Matthew Leung <matthew.leung@oss.qualcomm.com>

phy: qcom-qmp: pcs-pcie: Add v10.60 register offsets

This commit adds a new header file containing the specific PCS PCIe register
offsets for the QMP phy version v10.60 used in Hawi SoCs.

> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-pcs-pcie-v10_60.h b/drivers/phy/qualcomm/phy-qcom-qmp-pcs-pcie-v10_60.h
> new file mode 100644
> index 0000000000000..e4a2bdc7c3f03
> --- /dev/null
> +++ b/drivers/phy/qualcomm/phy-qcom-qmp-pcs-pcie-v10_60.h
> @@ -0,0 +1,26 @@
[ ... ]
> +#ifndef QCOM_PHY_QMP_PCS_PCIE_V10_60_H_
> +#define QCOM_PHY_QMP_PCS_PCIE_V10_60_H_
> +
> +/* Only for QMP V10_60 PHY - PCIE PCS registers */
> +#define QPHY_PCIE_V10_60_PCS_POWER_STATE_CONFIG2		0x00c
> +#define QPHY_PCIE_V10_60_PCS_PCS_TX_RX_CONFIG			0x018

This isn't a bug, but there is a redundant "PCS_" substring in
QPHY_PCIE_V10_60_PCS_PCS_TX_RX_CONFIG.

Should this be named QPHY_PCIE_V10_60_PCS_TX_RX_CONFIG to remain consistent
with older PHY version headers like QPHY_PCIE_V8_PCS_TX_RX_CONFIG?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260508-hawi-phy-pcie-v1-0-237b894353fc@oss.qualcomm.com?part=9

  reply	other threads:[~2026-05-08 23:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 23:31 [PATCH 00/10] phy: qcom: qmp-pcie: Add PCIe PHY support for Hawi Matthew Leung
2026-05-08 23:31 ` [PATCH 01/10] dt-bindings: phy: qcom,sc8280xp-qmp-pcie-phy: Add Hawi compatibles Matthew Leung
2026-05-08 23:31 ` [PATCH 02/10] phy: qcom-qmp: qserdes-com: Add v10 register offsets Matthew Leung
2026-05-08 23:31 ` [PATCH 03/10] phy: qcom-qmp: qserdes-txrx: " Matthew Leung
2026-05-08 23:31 ` [PATCH 04/10] phy: qcom-qmp: pcs: " Matthew Leung
2026-05-08 23:31 ` [PATCH 05/10] phy: qcom-qmp: pcs-pcie: " Matthew Leung
2026-05-08 23:31 ` [PATCH 06/10] phy: qcom-qmp: qserdes-com: Add v10.60 " Matthew Leung
2026-05-08 23:31 ` [PATCH 07/10] phy: qcom-qmp: qserdes-txrx: " Matthew Leung
2026-05-08 23:31 ` [PATCH 08/10] phy: qcom-qmp: pcs: " Matthew Leung
2026-05-08 23:31 ` [PATCH 09/10] phy: qcom-qmp: pcs-pcie: " Matthew Leung
2026-05-08 23:38   ` sashiko-bot [this message]
2026-05-08 23:31 ` [PATCH 10/10] phy: qcom: qmp-pcie: Add QMP PCIe PHY support for Hawi Matthew Leung

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=20260508233802.20366C2BCB0@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=matthew.leung@oss.qualcomm.com \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko@lists.linux.dev \
    --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