From: Thierry Reding <thierry.reding@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Peter Chen <Peter.Chen@nxp.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Felipe Balbi <balbi@kernel.org>,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/4] usb: phy: tegra: Perform general clean up of the code
Date: Thu, 19 Dec 2019 13:54:37 +0100 [thread overview]
Message-ID: <20191219125437.GB1440537@ulmo> (raw)
In-Reply-To: <20191218175313.16235-4-digetx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
On Wed, Dec 18, 2019 at 08:53:12PM +0300, Dmitry Osipenko wrote:
> This patch fixes few dozens of legit checkpatch warnings, adds missed
> handling of potential error-cases, fixes ULPI clk-prepare refcounting and
> prettifies code where makes sense. All these clean-up changes are quite
> minor and do not fix any problems.
>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
> drivers/usb/phy/phy-tegra-usb.c | 367 +++++++++++++++++---------------
> 1 file changed, 197 insertions(+), 170 deletions(-)
This could've been multiple patches to make it easier to review, but
either way:
Acked-by: Thierry Reding <treding@nvidia.com>
One minor comment below...
> diff --git a/drivers/usb/phy/phy-tegra-usb.c b/drivers/usb/phy/phy-tegra-usb.c
> index 15bd253d53c9..76949dbbbdc2 100644
> --- a/drivers/usb/phy/phy-tegra-usb.c
> +++ b/drivers/usb/phy/phy-tegra-usb.c
[...]
> @@ -310,13 +315,16 @@ static void ulpi_close(struct tegra_usb_phy *phy)
> }
> }
>
> -static void utmip_pad_power_on(struct tegra_usb_phy *phy)
> +static int utmip_pad_power_on(struct tegra_usb_phy *phy)
> {
> - unsigned long val, flags;
> - void __iomem *base = phy->pad_regs;
> struct tegra_utmip_config *config = phy->config;
> + void __iomem *base = phy->pad_regs;
> + unsigned long val, flags;
I think technically the "val" variable would have to be u32 because
that's what readl() and writel() operate on. That could be a separate
patch, though and isn't really a big problem.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-19 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 17:53 [PATCH v1 0/4] NVIDIA Tegra USB2 drivers clean up Dmitry Osipenko
2019-12-18 17:53 ` [PATCH v1 1/4] dt-binding: usb: ci-hdrc-usb2: Document NVIDIA Tegra support Dmitry Osipenko
2019-12-19 6:58 ` Peter Chen
2019-12-19 12:55 ` Thierry Reding
2019-12-18 17:53 ` [PATCH v1 2/4] usb: phy: tegra: Hook up init/shutdown callbacks Dmitry Osipenko
2019-12-19 6:56 ` Peter Chen
2019-12-19 15:24 ` Dmitry Osipenko
2019-12-19 13:01 ` Thierry Reding
2019-12-19 15:18 ` Dmitry Osipenko
2019-12-18 17:53 ` [PATCH v1 3/4] usb: phy: tegra: Perform general clean up of the code Dmitry Osipenko
2019-12-19 12:54 ` Thierry Reding [this message]
2019-12-19 15:37 ` Dmitry Osipenko
2019-12-18 17:53 ` [PATCH v1 4/4] usb: phy: tegra: Use relaxed versions of readl/writel Dmitry Osipenko
2019-12-19 12:55 ` Thierry Reding
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=20191219125437.GB1440537@ulmo \
--to=thierry.reding@gmail.com \
--cc=Peter.Chen@nxp.com \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@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).