From: Xu Yang <xu.yang_2@nxp.com>
To: Frank Li <Frank.li@nxp.com>
Cc: vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, gregkh@linuxfoundation.org,
peter.chen@kernel.org, herve.codina@bootlin.com,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-usb@vger.kernel.org, jun.li@nxp.com
Subject: Re: [PATCH 1/6] usb: phy: mxs: Using regulator phy-3p0
Date: Fri, 19 Jul 2024 15:05:16 +0800 [thread overview]
Message-ID: <20240719070516.bhzt3wglwlu3q4po@hippo> (raw)
In-Reply-To: <Zpkp2URtnfSdm0EL@lizhi-Precision-Tower-5810>
On Thu, Jul 18, 2024 at 10:42:33AM -0400, Frank Li wrote:
> On Thu, Jul 18, 2024 at 06:26:32PM +0800, Xu Yang wrote:
> > It is one of PHY's power, and we need to enable it to keep signal
> > quality good, and pass eye diagram test.
>
> "Enable regulator 'phy-3p0' to pass eye diagram test since it improve signal
> qualilty."
>
> My question is why it just improve signal quality instead of make it work.
> It should not work if no power supply.
I'm cleaning up these old local patch and I'm not very clear about the history.
But I think this 3p0 is not the main power of phy, it's just one of phy's power.
I can only get below info about this reg-3p0:
37.6.2 Regulator 3P0 Register (PMU_REG_3P0)
"This register defines the control and status bits for the 3.0V regulator
powered by the host USB VBUS pin."
I've just tested it works well without this phy-3p0. I'll rewrite the commit
message to avoid confusion.
>
> >
> > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> > ---
> > drivers/usb/phy/phy-mxs-usb.c | 30 ++++++++++++++++++++++++++++++
> > 1 file changed, 30 insertions(+)
> >
> > diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c
> > index 920a32cd094d..42fcc8ad9492 100644
> > --- a/drivers/usb/phy/phy-mxs-usb.c
> > +++ b/drivers/usb/phy/phy-mxs-usb.c
> > @@ -18,6 +18,7 @@
> > #include <linux/regmap.h>
> > #include <linux/mfd/syscon.h>
> > #include <linux/iopoll.h>
> > +#include <linux/regulator/consumer.h>
> >
> > #define DRIVER_NAME "mxs_phy"
> >
> > @@ -204,6 +205,7 @@ struct mxs_phy {
> > int port_id;
> > u32 tx_reg_set;
> > u32 tx_reg_mask;
> > + struct regulator *phy_3p0;
> > };
> >
> > static inline bool is_imx6q_phy(struct mxs_phy *mxs_phy)
> > @@ -288,6 +290,16 @@ static int mxs_phy_hw_init(struct mxs_phy *mxs_phy)
> > if (ret)
> > goto disable_pll;
> >
> > + if (mxs_phy->phy_3p0) {
> > + ret = regulator_enable(mxs_phy->phy_3p0);
> > + if (ret) {
> > + dev_err(mxs_phy->phy.dev,
> > + "Failed to enable 3p0 regulator, ret=%d\n",
> > + ret);
> > + return ret;
> > + }
> > + }
> > +
> > /* Power up the PHY */
> > writel(0, base + HW_USBPHY_PWD);
> >
> > @@ -448,6 +460,9 @@ static void mxs_phy_shutdown(struct usb_phy *phy)
> > if (is_imx7ulp_phy(mxs_phy))
> > mxs_phy_pll_enable(phy->io_priv, false);
> >
> > + if (mxs_phy->phy_3p0)
> > + regulator_disable(mxs_phy->phy_3p0);
> > +
> > clk_disable_unprepare(mxs_phy->clk);
> > }
> >
> > @@ -789,6 +804,21 @@ static int mxs_phy_probe(struct platform_device *pdev)
> > mxs_phy->clk = clk;
> > mxs_phy->data = of_device_get_match_data(&pdev->dev);
> >
> > + mxs_phy->phy_3p0 = devm_regulator_get(&pdev->dev, "phy-3p0");
>
> Does binding doc update?
Yes.
>
> > + if (PTR_ERR(mxs_phy->phy_3p0) == -EPROBE_DEFER) {
> > + return -EPROBE_DEFER;
> > + } else if (PTR_ERR(mxs_phy->phy_3p0) == -ENODEV) {
> > + /* not exist */
> > + mxs_phy->phy_3p0 = NULL;
> > + } else if (IS_ERR(mxs_phy->phy_3p0)) {
> > + dev_err(&pdev->dev, "Getting regulator error: %ld\n",
> > + PTR_ERR(mxs_phy->phy_3p0));
> > + return PTR_ERR(mxs_phy->phy_3p0);
> > + }
>
> just need call dev_err_probe()
Ok. Will change it.
>
> > +
> > + if (mxs_phy->phy_3p0)
> > + regulator_set_voltage(mxs_phy->phy_3p0, 3200000, 3200000);
> > +
> > platform_set_drvdata(pdev, mxs_phy);
> >
> > device_set_wakeup_capable(&pdev->dev, true);
> > --
> > 2.34.1
> >
prev parent reply other threads:[~2024-07-19 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 10:26 [PATCH 1/6] usb: phy: mxs: Using regulator phy-3p0 Xu Yang
2024-07-18 10:26 ` [PATCH 2/6] usb: phy: mxs: keep USBPHY2's clk always on Xu Yang
2024-07-18 15:00 ` Frank Li
2024-07-19 7:16 ` Xu Yang
2024-07-18 10:26 ` [PATCH 3/6] dt-bindings: phy: mxs-usb-phy: add nxp,sim property Xu Yang
2024-07-23 2:51 ` Rob Herring
2024-07-24 1:29 ` Xu Yang
2024-07-18 10:26 ` [PATCH 4/6] usb: phy: mxs: add wakeup enable for imx7ulp Xu Yang
2024-07-18 10:26 ` [PATCH 5/6] usb: phy: mxs: enable weak 1p1 regulator for imx6ul during suspend Xu Yang
2024-07-18 15:12 ` Frank Li
2024-07-19 7:37 ` Xu Yang
2024-07-18 10:26 ` [PATCH 6/6] ARM: dts: imx7ulp: add "nxp,sim" property for usbphy1 Xu Yang
2024-07-18 14:42 ` [PATCH 1/6] usb: phy: mxs: Using regulator phy-3p0 Frank Li
2024-07-19 7:05 ` Xu Yang [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=20240719070516.bhzt3wglwlu3q4po@hippo \
--to=xu.yang_2@nxp.com \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=herve.codina@bootlin.com \
--cc=imx@lists.linux.dev \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox