From: Felipe Balbi <balbi@ti.com>
To: "Ivan T. Ivanov" <iivanov@mm-sol.com>
Cc: balbi@ti.com, rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, swarren@wwwdotorg.org,
ian.campbell@citrix.com, rob@landley.net,
gregkh@linuxfoundation.org, grant.likely@linaro.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [RFC 2/2] usb: dwc3: Add Qualcomm DWC3 glue layer driver
Date: Fri, 9 Aug 2013 16:23:49 +0300 [thread overview]
Message-ID: <20130809132349.GC12041@radagast> (raw)
In-Reply-To: <1375789991-30041-3-git-send-email-iivanov@mm-sol.com>
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
Hi,
On Tue, Aug 06, 2013 at 02:53:11PM +0300, Ivan T. Ivanov wrote:
> diff --git a/drivers/usb/dwc3/dwc3-msm.c b/drivers/usb/dwc3/dwc3-msm.c
> new file mode 100644
> index 0000000..e509abc
> --- /dev/null
> +++ b/drivers/usb/dwc3/dwc3-msm.c
> @@ -0,0 +1,175 @@
> +#undef CONFIG_REGULATOR
why ??????
> +static int dwc3_msm_probe(struct platform_device *pdev)
> +{
> + struct device_node *node = pdev->dev.of_node;
> + struct dwc3_msm *mdwc;
> + struct resource *res;
> + void __iomem *tcsr;
> + int ret = 0;
> +
> + dev_info(&pdev->dev, "MSM DWC3\n");
please don't. This is hardly necessary.
> + mdwc = devm_kzalloc(&pdev->dev, sizeof(*mdwc), GFP_KERNEL);
> + if (!mdwc) {
> + dev_err(&pdev->dev, "not enough memory\n");
this message isn't needed either
> + /*
> + * DWC3 Core requires its CORE CLK (aka master / bus clk) to
> + * run at 125Mhz in SSUSB mode and >60MHZ for HSUSB mode.
> + */
> + clk_set_rate(mdwc->core_clk, 125000000);
if this is dwc3's core clock, why don't we teach dwc3.ko about this
requirement ? Just make sure to have it optional, since x86 and OMAP
wouldn't need direct fiddling with the clocks.
> + clk_prepare_enable(mdwc->core_clk);
> + clk_prepare_enable(mdwc->iface_clk);
> + clk_prepare_enable(mdwc->sleep_clk);
> + clk_prepare_enable(mdwc->utmi_clk);
do you really need to enable your clocks here ? Why don't you enable
them on runtime_resume and disable on runtime_suspend ?
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + tcsr = devm_ioremap_resource(&pdev->dev, res);
> + if (!tcsr) {
> + dev_dbg(&pdev->dev, "tcsr ioremap failed\n");
no need to ioremap, also you're likely leaking clocks and regulators
enabled here.
Make sure to have something like:
if (!tcsr)
goto err_disable_clocks;
/* TODO This has to be revised */\
[...]
> + } else {
> + /* TODO: This has to be revised */
> +
> + /* Enable USB3 on the primary USB port. */
> + writel_relaxed(0x1, tcsr);
> + /*
> + * Ensure that TCSR write is completed before
> + * USB registers initialization.
> + */
> + mb();
why don't you use writel() instead. It will add the memory barrier for
you.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-09 13:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 11:53 [RFC 0/2] DWC3 USB support for Qualcomm platform Ivan T. Ivanov
2013-08-06 11:53 ` [RFC 1/2] usb: phy: Add Qualcomm SS-USB and HS-USB drivers for DWC3 core Ivan T. Ivanov
2013-08-06 12:12 ` Pawel Moll
2013-08-06 13:30 ` Ivan T. Ivanov
2013-08-06 14:03 ` Mark Rutland
2013-08-06 14:36 ` Ivan T. Ivanov
2013-08-08 9:16 ` Mark Rutland
2013-08-06 11:53 ` [RFC 2/2] usb: dwc3: Add Qualcomm DWC3 glue layer driver Ivan T. Ivanov
2013-08-06 12:21 ` Pawel Moll
2013-08-06 13:46 ` Ivan T. Ivanov
2013-08-06 15:15 ` Pawel Moll
2013-08-06 17:53 ` Ivan T. Ivanov
2013-08-09 13:24 ` Felipe Balbi
2013-08-06 14:07 ` Mark Rutland
2013-08-06 14:41 ` Ivan T. Ivanov
2013-08-09 13:23 ` Felipe Balbi [this message]
2013-08-09 16:09 ` Ivan T. Ivanov
2013-08-12 18:24 ` Felipe Balbi
2013-08-14 9:28 ` Ivan T. Ivanov
2013-08-27 18:46 ` Felipe Balbi
2013-08-14 9:43 ` Ivan T. Ivanov
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=20130809132349.GC12041@radagast \
--to=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ian.campbell@citrix.com \
--cc=iivanov@mm-sol.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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).