From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: vkoul@kernel.org, kishon@kernel.org,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] phy: qcom: qmp: Add debug prints for register writes
Date: Thu, 1 Aug 2024 12:28:14 +0530 [thread overview]
Message-ID: <20240801065814.GA3705@thinkpad> (raw)
In-Reply-To: <nkfrtuxv4ueow66bnazyb4ul3pz3z3wo6zsptu6wnw7hflxerx@pkwn7sx6gfqi>
On Wed, Jul 31, 2024 at 09:26:27PM -0500, Bjorn Andersson wrote:
> On Wed, Jul 31, 2024 at 05:26:37PM GMT, 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.
> >
>
> I've written this patch every time I've touched one of these PHYs, so I
> certainly like this.
>
Me too :) I've been carrying this as an out-of-tree patch ever since I started
bringing up Qcom chipsets.
> > Sample debug prints:
> >
> > QMP PHY: Writing Reg: QSERDES_V5_COM_SYSCLK_EN_SEL Offset: 0x0094 Val: 0xd9
> > QMP PHY: Writing Reg: QSERDES_V5_COM_HSCLK_SEL Offset: 0x0158 Val: 0x11
>
> That said, with multiple instances of PHYs being configured at about the
> same time it seems this would benefit greatly from something identifying
> which PHY instance the write relates to?
>
> dev_dbg() would certainly be nice...
>
I understood that after comments from Dmitry. So v4 has this:
qcom-qmp-pcie-phy 1c0e000.phy: Writing Reg: QSERDES_V5_COM_SYSCLK_EN_SEL Offset: 0x0094 Val: 0xd9
- Mani
> >
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > ---
> >
> > Changes in v2:
> >
> > * Modifed the debug print to include reg offset
> >
> > drivers/phy/qualcomm/phy-qcom-qmp-common.h | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-common.h b/drivers/phy/qualcomm/phy-qcom-qmp-common.h
> > index 799384210509..40beb413328f 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;
>
> const?
>
> Regards,
> Bjorn
>
> > /*
> > * 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,8 @@ static inline void qmp_configure_lane(void __iomem *base,
> > if (!(t->lane_mask & lane_mask))
> > continue;
> >
> > + pr_debug("QMP PHY: Writing Reg: %s Offset: 0x%04x Val: 0x%02x\n",
> > + t->name, t->offset, t->val);
> > writel(t->val, base + t->offset);
> > }
> > }
> > --
> > 2.25.1
> >
> >
--
மணிவண்ணன் சதாசிவம்
WARNING: multiple messages have this Message-ID (diff)
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: vkoul@kernel.org, kishon@kernel.org,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] phy: qcom: qmp: Add debug prints for register writes
Date: Thu, 1 Aug 2024 12:28:14 +0530 [thread overview]
Message-ID: <20240801065814.GA3705@thinkpad> (raw)
In-Reply-To: <nkfrtuxv4ueow66bnazyb4ul3pz3z3wo6zsptu6wnw7hflxerx@pkwn7sx6gfqi>
On Wed, Jul 31, 2024 at 09:26:27PM -0500, Bjorn Andersson wrote:
> On Wed, Jul 31, 2024 at 05:26:37PM GMT, 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.
> >
>
> I've written this patch every time I've touched one of these PHYs, so I
> certainly like this.
>
Me too :) I've been carrying this as an out-of-tree patch ever since I started
bringing up Qcom chipsets.
> > Sample debug prints:
> >
> > QMP PHY: Writing Reg: QSERDES_V5_COM_SYSCLK_EN_SEL Offset: 0x0094 Val: 0xd9
> > QMP PHY: Writing Reg: QSERDES_V5_COM_HSCLK_SEL Offset: 0x0158 Val: 0x11
>
> That said, with multiple instances of PHYs being configured at about the
> same time it seems this would benefit greatly from something identifying
> which PHY instance the write relates to?
>
> dev_dbg() would certainly be nice...
>
I understood that after comments from Dmitry. So v4 has this:
qcom-qmp-pcie-phy 1c0e000.phy: Writing Reg: QSERDES_V5_COM_SYSCLK_EN_SEL Offset: 0x0094 Val: 0xd9
- Mani
> >
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > ---
> >
> > Changes in v2:
> >
> > * Modifed the debug print to include reg offset
> >
> > drivers/phy/qualcomm/phy-qcom-qmp-common.h | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-common.h b/drivers/phy/qualcomm/phy-qcom-qmp-common.h
> > index 799384210509..40beb413328f 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;
>
> const?
>
> Regards,
> Bjorn
>
> > /*
> > * 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,8 @@ static inline void qmp_configure_lane(void __iomem *base,
> > if (!(t->lane_mask & lane_mask))
> > continue;
> >
> > + pr_debug("QMP PHY: Writing Reg: %s Offset: 0x%04x Val: 0x%02x\n",
> > + t->name, t->offset, t->val);
> > writel(t->val, base + t->offset);
> > }
> > }
> > --
> > 2.25.1
> >
> >
--
மணிவண்ணன் சதாசிவம்
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2024-08-01 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 11:56 [PATCH v2] phy: qcom: qmp: Add debug prints for register writes Manivannan Sadhasivam
2024-07-31 11:56 ` Manivannan Sadhasivam
2024-08-01 2:26 ` Bjorn Andersson
2024-08-01 2:26 ` Bjorn Andersson
2024-08-01 6:58 ` Manivannan Sadhasivam [this message]
2024-08-01 6:58 ` 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=20240801065814.GA3705@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=andersson@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.