Re: [PATCH] usb: host: ehci-tegra: Avoid getting the same reset twice

From: Alan Stern
Date: Tue May 03 2016 - 15:17:04 EST

On Tue, 3 May 2016, Thierry Reding wrote:

> From: Thierry Reding <treding@xxxxxxxxxx>
> Starting with commit 0b52297f2288 ("reset: Add support for shared reset
> controls") there is a reference count for reset control assertions. The
> goal is to allow resets to be shared by multiple devices and an assert
> will take effect only when all instances have asserted the reset.
> In order to preserve backwards-compatibility, all reset controls become
> exclusive by default. This is to ensure that reset_control_assert() can
> immediately assert in hardware.
> However, this new behaviour triggers the following warning in the EHCI
> driver for Tegra:


> The reason is that the EHCI implements three ports, each with a separate
> reset line. However the first port's reset also serves as a means to
> reset the UTMI pad for all ports. There is special code in the driver to
> assert and deassert this shared reset at probe time. It needs to do this
> regardless of which port is probed first. Unfortunately this means that
> if the first port is probed first, it will request its own reset line
> and subsequently request the same reset line again (temporarily) to
> perform the reset. This used to work fine before the above-mentioned
> commit, but now triggers the new WARN.
> Work around this by making sure we reuse the port's reset if it happens
> to be the same as the UTMI pad reset.
> Cc: Philipp Zabel <p.zabel@xxxxxxxxxxxxxx>
> Cc: Hans de Goede <hdegoede@xxxxxxxxxx>
> Signed-off-by: Thierry Reding <treding@xxxxxxxxxx>

Possibly related to the problems you are still seeing, I noticed
something odd about the patch.

> --- a/drivers/usb/host/ehci-tegra.c
> +++ b/drivers/usb/host/ehci-tegra.c
> @@ -81,15 +81,23 @@ static int tegra_reset_usb_controller(struct platform_device *pdev)
> struct usb_hcd *hcd = platform_get_drvdata(pdev);
> struct tegra_ehci_hcd *tegra =
> (struct tegra_ehci_hcd *)hcd_to_ehci(hcd)->priv;
> + bool has_utmi_pad_registers = false;
> phy_np = of_parse_phandle(pdev->dev.of_node, "nvidia,phy", 0);
> if (!phy_np)
> return -ENOENT;
> + if (of_property_read_bool(phy_np, "nvidia,has-utmi-pad-registers"))
> + has_utmi_pad_registers = true;

I would have writte simply:

has_utmi_pad_registers = of_property_read_bool(phy_np,

Regardless, notice that has_utmi_pad_registers gets set to true if the
OF property value is true.


> - if (!of_property_read_bool(phy_np, "nvidia,has-utmi-pad-registers")) {
> + if (has_utmi_pad_registers) {

But down here the sense of the test is reversed. Now the conditional
block gets executed if the property is true, whereas the original code
executed it if the property was false.

> reset_control_assert(tegra->rst);
> udelay(1);
> reset_control_deassert(tegra->rst);

Alan Stern