From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>, <agross@kernel.org>,
<andersson@kernel.org>, <vkoul@kernel.org>, <kishon@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <gregkh@linuxfoundation.org>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<mturquette@baylibre.com>, <sboyd@kernel.org>,
<p.zabel@pengutronix.de>, <arnd@arndb.de>,
<geert+renesas@glider.be>, <neil.armstrong@linaro.org>,
<nfraprado@collabora.com>, <broonie@kernel.org>,
<rafal@milecki.pl>, <quic_srichara@quicinc.com>,
<quic_varada@quicinc.org>, <quic_wcheng@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <linux-phy@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-clk@vger.kernel.org>
Subject: Re: [PATCH 3/9] phy: qcom-m31: Introduce qcom,m31 USB phy driver
Date: Thu, 15 Jun 2023 11:31:19 +0530 [thread overview]
Message-ID: <20230615060118.GD22186@varda-linux.qualcomm.com> (raw)
In-Reply-To: <cf3c98c1-e283-3fac-3144-5a7354378a6b@linaro.org>
On Wed, Jun 07, 2023 at 03:29:18PM +0300, Dmitry Baryshkov wrote:
> Two minor nits on top of the review:
>
> On 07/06/2023 14:54, Konrad Dybcio wrote:
> >On 7.06.2023 12:56, Varadarajan Narayanan wrote:
> >>Add the M31 USB2 phy driver
> >>
> >>Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com>
> >>---
> >> drivers/phy/qualcomm/phy-qcom-m31.c | 360 ++++++++++++++++++++++++++++++++++++
> >> 1 file changed, 360 insertions(+)
> >> create mode 100644 drivers/phy/qualcomm/phy-qcom-m31.c
> >>
> >>diff --git a/drivers/phy/qualcomm/phy-qcom-m31.c b/drivers/phy/qualcomm/phy-qcom-m31.c
> >>new file mode 100644
> >>index 0000000..d29a91e
> >>--- /dev/null
> >>+++ b/drivers/phy/qualcomm/phy-qcom-m31.c
> >>@@ -0,0 +1,360 @@
> >>+// SPDX-License-Identifier: GPL-2.0+
> >>+/*
> >>+ * Copyright (c) 2014-2016, 2020, The Linux Foundation. All rights reserved.
> >>+ */
> >>+
> >>+#include <linux/module.h>
> >>+#include <linux/kernel.h>
> >>+#include <linux/err.h>
> >>+#include <linux/slab.h>
> >>+#include <linux/clk.h>
> >>+#include <linux/delay.h>
> >>+#include <linux/io.h>
> >>+#include <linux/of.h>
> >>+#include <linux/platform_device.h>
> >>+#include <linux/usb/phy.h>
> >>+#include <linux/reset.h>
> >>+#include <linux/of_device.h>
> >Please sort these
> >
> >>+
> >>+enum clk_reset_action {
> >>+ CLK_RESET_DEASSERT = 0,
> >>+ CLK_RESET_ASSERT = 1
> >>+};
> >>+
> >>+#define USB2PHY_PORT_POWERDOWN 0xA4
> >>+#define POWER_UP BIT(0)
> >>+#define POWER_DOWN 0
> >>+
> >>+#define USB2PHY_PORT_UTMI_CTRL1 0x40
> >>+
> >>+#define USB2PHY_PORT_UTMI_CTRL2 0x44
> >>+#define UTMI_ULPI_SEL BIT(7)
> >>+#define UTMI_TEST_MUX_SEL BIT(6)
> >>+
> >>+#define HS_PHY_CTRL_REG 0x10
> >>+#define UTMI_OTG_VBUS_VALID BIT(20)
> >>+#define SW_SESSVLD_SEL BIT(28)
> >>+
> >>+#define USB_PHY_CFG0 0x94
> >>+#define USB_PHY_UTMI_CTRL5 0x50
> >>+#define USB_PHY_FSEL_SEL 0xB8
> >>+#define USB_PHY_HS_PHY_CTRL_COMMON0 0x54
> >>+#define USB_PHY_REFCLK_CTRL 0xA0
> >>+#define USB_PHY_HS_PHY_CTRL2 0x64
> >>+#define USB_PHY_UTMI_CTRL0 0x3c
> >>+#define USB2PHY_USB_PHY_M31_XCFGI_1 0xBC
> >>+#define USB2PHY_USB_PHY_M31_XCFGI_4 0xC8
> >>+#define USB2PHY_USB_PHY_M31_XCFGI_5 0xCC
> >>+#define USB2PHY_USB_PHY_M31_XCFGI_11 0xE4
> >Could you sort them address-wise?
>
> ... and lowercase the hex values, please.
Ok.
> >>+
> >>+#define USB2_0_TX_ENABLE BIT(2)
> >>+#define HSTX_SLEW_RATE_565PS 3
> >>+#define PLL_CHARGING_PUMP_CURRENT_35UA (3 << 3)
> >>+#define ODT_VALUE_38_02_OHM (3 << 6)
> >>+#define ODT_VALUE_45_02_OHM BIT(2)
> >>+#define HSTX_PRE_EMPHASIS_LEVEL_0_55MA (1)
> >Weird mix of values, bits, bitfields.. perhaps BIT(n) and
> >GENMASK() (+ FIELD_PREP) would be more suitable?
> >
> >>+
> >>+#define UTMI_PHY_OVERRIDE_EN BIT(1)
> >>+#define POR_EN BIT(1)
> >Please associate these with their registers, like
> >
> >#define FOO_REG 0xf00
> > #define POR_EN BIT(1)
> >
> >>+#define FREQ_SEL BIT(0)
> >>+#define COMMONONN BIT(7)
> >>+#define FSEL BIT(4)
> >>+#define RETENABLEN BIT(3)
> >>+#define USB2_SUSPEND_N_SEL BIT(3)
> >>+#define USB2_SUSPEND_N BIT(2)
> >>+#define USB2_UTMI_CLK_EN BIT(1)
> >>+#define CLKCORE BIT(1)
> >>+#define ATERESET ~BIT(0)
> >>+#define FREQ_24MHZ (5 << 4)
> >>+#define XCFG_COARSE_TUNE_NUM (2 << 0)
> >>+#define XCFG_FINE_TUNE_NUM (1 << 3)
> >same comment
> >
> >>+
> >>+static void m31usb_write_readback(void *base, u32 offset,
> >>+ const u32 mask, u32 val);
> >We don't need this forward-definition, just move the function up.
> >
> >>+
> >>+struct m31usb_phy {
> >>+ struct usb_phy phy;
> >>+ void __iomem *base;
> >>+ void __iomem *qscratch_base;
> >>+
> >>+ struct reset_control *phy_reset;
> >>+
> >>+ bool cable_connected;
> >>+ bool suspended;
> >>+ bool ulpi_mode;
> >>+};
> >>+
> >>+static void m31usb_reset(struct m31usb_phy *qphy, u32 action)
> >>+{
> >>+ if (action == CLK_RESET_ASSERT)
> >>+ reset_control_assert(qphy->phy_reset);
> >>+ else
> >>+ reset_control_deassert(qphy->phy_reset);
> >>+ wmb(); /* ensure data is written to hw register */
> >Please move the comment above the call.
> >
> >>+}
>
> Or even better just inline the function. I was never a fan of such
> multiplexers.
>
> Also does wmb() make sense here? Doesn't regmap (which is used by reset
> controller) remove the need for it?
Will inline and remove the wmb.
Thanks
Varada
> >>+
> >>+static void m31usb_phy_enable_clock(struct m31usb_phy *qphy)
> >>+{
> >>+ /* Enable override ctrl */
> >>+ writel(UTMI_PHY_OVERRIDE_EN, qphy->base + USB_PHY_CFG0);
> >Some of the comments are missing a space before '*/'
> >
> >Also, please consider adding some newlines to logically split the
> >actions.
>
>
> --
> With best wishes
> Dmitry
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-15 6:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 10:56 [PATCH 0/9] Enable IPQ5332 USB2 Varadarajan Narayanan
2023-06-07 10:56 ` [PATCH 1/9] dt-bindings: usb: dwc3: Add IPQ5332 compatible Varadarajan Narayanan
2023-06-07 18:33 ` Krzysztof Kozlowski
2023-06-15 4:15 ` Varadarajan Narayanan
2023-06-07 10:56 ` [PATCH 2/9] dt-bindings: phy: qcom,m31: Document qcom,m31 USB phy Varadarajan Narayanan
2023-06-07 11:37 ` Rob Herring
2023-06-07 18:31 ` Krzysztof Kozlowski
2023-06-15 5:27 ` Varadarajan Narayanan
2023-06-17 8:48 ` Krzysztof Kozlowski
2023-06-20 9:32 ` Varadarajan Narayanan
2023-06-21 8:43 ` Krzysztof Kozlowski
2023-06-21 10:12 ` Varadarajan Narayanan
2023-06-07 10:56 ` [PATCH 3/9] phy: qcom-m31: Introduce qcom,m31 USB phy driver Varadarajan Narayanan
2023-06-07 11:54 ` Konrad Dybcio
2023-06-07 12:29 ` Dmitry Baryshkov
2023-06-15 6:01 ` Varadarajan Narayanan [this message]
2023-06-15 5:49 ` Varadarajan Narayanan
2023-06-21 11:05 ` Vinod Koul
2023-06-07 10:56 ` [PATCH 4/9] clk: qcom: ipq5332: Fix USB related clock defines Varadarajan Narayanan
2023-06-07 11:19 ` Dmitry Baryshkov
2023-06-15 6:02 ` Varadarajan Narayanan
2023-06-07 10:56 ` [PATCH 5/9] phy: qcom-m31: Introduce qcom,m31 USB phy Varadarajan Narayanan
2023-06-07 11:20 ` Dmitry Baryshkov
2023-06-07 18:37 ` Krzysztof Kozlowski
2023-06-15 6:05 ` Varadarajan Narayanan
2023-06-07 10:56 ` [PATCH 6/9] phy: qcom: Add qcom,m31 USB phy driver Varadarajan Narayanan
2023-06-07 18:36 ` Krzysztof Kozlowski
2023-06-15 6:14 ` Varadarajan Narayanan
2023-06-07 10:56 ` [PATCH 7/9] arm64: dts: qcom: ipq5332: Add USB related nodes Varadarajan Narayanan
2023-06-07 11:23 ` Dmitry Baryshkov
2023-06-15 6:26 ` Varadarajan Narayanan
2023-06-07 18:24 ` Konrad Dybcio
2023-06-15 6:52 ` Varadarajan Narayanan
2023-06-07 18:35 ` Krzysztof Kozlowski
2023-06-15 7:17 ` Varadarajan Narayanan
2023-06-07 10:56 ` [PATCH 8/9] arm64: dts: qcom: ipq5332: Enable USB Varadarajan Narayanan
2023-06-07 10:56 ` [PATCH 9/9] arm64: defconfig: Enable QCOM M31 USB phy driver Varadarajan Narayanan
2023-06-07 18:36 ` Krzysztof Kozlowski
2023-06-15 8:37 ` Varadarajan Narayanan
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=20230615060118.GD22186@varda-linux.qualcomm.com \
--to=quic_varada@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.org \
--cc=quic_wcheng@quicinc.com \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=vkoul@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).