From: Vinod Koul <vkoul@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: kishon@kernel.org, linux-arm-msm@vger.kernel.org,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: qcom: qmp: Add debug prints for register writes
Date: Wed, 31 Jul 2024 16:28:46 +0530 [thread overview]
Message-ID: <ZqoY5kFLDEmkb495@matsya> (raw)
In-Reply-To: <20240730100351.51454-1-manivannan.sadhasivam@linaro.org>
On 30-07-24, 15:33, Manivannan Sadhasivam wrote:
> These register prints are useful to validate the init sequence against the
> Qcom internal documentation and also to share with the Qcom hw engineers to
> debug issues related to PHY.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> drivers/phy/qualcomm/phy-qcom-qmp-common.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-common.h b/drivers/phy/qualcomm/phy-qcom-qmp-common.h
> index 799384210509..e6a6bcfcac28 100644
> --- a/drivers/phy/qualcomm/phy-qcom-qmp-common.h
> +++ b/drivers/phy/qualcomm/phy-qcom-qmp-common.h
> @@ -9,6 +9,7 @@
> struct qmp_phy_init_tbl {
> unsigned int offset;
> unsigned int val;
> + char *name;
> /*
> * mask of lanes for which this register is written
> * for cases when second lane needs different values
> @@ -20,6 +21,7 @@ struct qmp_phy_init_tbl {
> { \
> .offset = o, \
> .val = v, \
> + .name = #o, \
> .lane_mask = 0xff, \
> }
>
> @@ -27,6 +29,7 @@ struct qmp_phy_init_tbl {
> { \
> .offset = o, \
> .val = v, \
> + .name = #o, \
> .lane_mask = l, \
> }
>
> @@ -45,6 +48,7 @@ static inline void qmp_configure_lane(void __iomem *base,
> if (!(t->lane_mask & lane_mask))
> continue;
>
> + pr_debug("QMP PHY: Writing: %s --> 0x%02x\n", t->name, t->val);
This lgtm, but fails to help when offset _might_ be incorrect, including
the offset value as well (not just the name) would be better imo...
> writel(t->val, base + t->offset);
> }
> }
> --
> 2.25.1
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-07-31 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 10:03 [PATCH] phy: qcom: qmp: Add debug prints for register writes Manivannan Sadhasivam
2024-07-31 10:58 ` Vinod Koul [this message]
2024-07-31 12:18 ` Dmitry Baryshkov
2024-07-31 12:19 ` Dmitry Baryshkov
2024-07-31 15:29 ` Manivannan Sadhasivam
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=ZqoY5kFLDEmkb495@matsya \
--to=vkoul@kernel.org \
--cc=kishon@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.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).