public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Amelie Delaunay <amelie.delaunay@st.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v4] usb: dwc2: dwc2_vbus_supply_init: fix error check
Date: Tue, 10 Apr 2018 17:37:46 +0200	[thread overview]
Message-ID: <41174786.HiOuqceMIB@diego> (raw)
In-Reply-To: <410670D7E743164D87FA6160E7907A560113AE7E5C@am04wembxb.internal.synopsys.com>

Am Dienstag, 10. April 2018, 15:52:25 CEST schrieb Minas Harutyunyan:
> Hi Heiko,
> 
> On 4/10/2018 4:28 PM, Heiko Stuebner wrote:
> > Am Montag, 26. März 2018, 11:00:01 CEST schrieb Tomeu Vizoso:
> >> devm_regulator_get_optional returns -ENODEV if the regulator isn't
> >> there, so if that's the case we have to make sure not to leave -ENODEV
> >> in the regulator pointer.
> >> 
> >> Also, make sure we return 0 in that case, but correctly propagate any
> >> other errors. Also propagate the error from _dwc2_hcd_start.
> >> 
> >> Fixes: 531ef5ebea96 ("usb: dwc2: add support for host mode external vbus
> >> supply") Cc: Amelie Delaunay <amelie.delaunay@st.com>
> >> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> > 
> > The patch that gets fixed here also breaks display-output on dwc2-based
> > Rockchip devices (likely even more), probably due to making the regulator
> > framework hickup.
> 
> Could you please elaborate what mean "breaks display-output".
> On which Kernel version you apply this patch?

I think I may have written that poorly. _Without_ this patch I get
display breakage on the most recent torvalds/master (merge-window)
where "usb: dwc2: add support for host mode external vbus supply" is
applied and this patch fixes the issue.

"breaks display output" means both hdmi + edp output are missing
also including the backlight staying off.

The patch we're fixing here, causes a null-pointer dereference in the
regulator framework, which seems to also cause issues when other
regulators are enabled, which I think is what I'm seeing here.


Heiko

> 
> Thanks,
> Minas
> 
> > With this patch applied, apart from not seeing the NULL-ptr, I also get
> > display output on my rk3288-veycron Chromebook again, so
> > 
> > Tested-by: Heiko Stuebner <heiko@sntech.de>
> > 
> >> v2: Only overwrite the error in the pointer after checking it (Heiko
> >> 
> >>      Stübner <heiko@sntech.de>)
> >> 
> >> v3: Remove hunks that shouldn't be in this patch
> >> v4: Don't overwrite the error code before returning it (kbuild test
> >> 
> >>      robot <lkp@intel.com>)
> >> 
> >> ---
> >> 
> >>   drivers/usb/dwc2/hcd.c | 13 ++++++++-----
> >>   1 file changed, 8 insertions(+), 5 deletions(-)
> >> 
> >> diff --git a/drivers/usb/dwc2/hcd.c b/drivers/usb/dwc2/hcd.c
> >> index 190f95964000..c51b73b3e048 100644
> >> --- a/drivers/usb/dwc2/hcd.c
> >> +++ b/drivers/usb/dwc2/hcd.c
> >> @@ -358,9 +358,14 @@ static void dwc2_gusbcfg_init(struct dwc2_hsotg
> >> *hsotg)>> 
> >>   static int dwc2_vbus_supply_init(struct dwc2_hsotg *hsotg)
> >>   {
> >> 
> >> +	int ret;
> >> +
> >> 
> >>   	hsotg->vbus_supply = devm_regulator_get_optional(hsotg->dev, "vbus");
> >> 
> >> -	if (IS_ERR(hsotg->vbus_supply))
> >> -		return 0;
> >> +	if (IS_ERR(hsotg->vbus_supply)) {
> >> +		ret = PTR_ERR(hsotg->vbus_supply);
> >> +		hsotg->vbus_supply = NULL;
> >> +		return ret == -ENODEV ? 0 : ret;
> >> +	}
> >> 
> >>   	return regulator_enable(hsotg->vbus_supply);
> >>   
> >>   }
> >> 
> >> @@ -4342,9 +4347,7 @@ static int _dwc2_hcd_start(struct usb_hcd *hcd)
> >> 
> >>   	spin_unlock_irqrestore(&hsotg->lock, flags);
> >> 
> >> -	dwc2_vbus_supply_init(hsotg);
> >> -
> >> -	return 0;
> >> +	return dwc2_vbus_supply_init(hsotg);
> >> 
> >>   }
> >>   
> >>   /*



  reply	other threads:[~2018-04-10 15:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  9:39 [PATCH] usb: dwc2: dwc2_vbus_supply_init: fix error check Tomeu Vizoso
2018-03-22 11:39 ` Heiko Stübner
2018-03-22 11:41   ` Heiko Stübner
2018-03-22 12:21     ` Amelie DELAUNAY
2018-03-22 13:06 ` [PATCH v2] " Tomeu Vizoso
2018-03-22 13:14 ` [PATCH v3] " Tomeu Vizoso
2018-03-22 13:26   ` Heiko Stübner
2018-03-22 13:34     ` Tomeu Vizoso
2018-03-24  0:24   ` kbuild test robot
2018-03-26  9:00 ` [PATCH v4] " Tomeu Vizoso
2018-03-26 10:56   ` Amelie DELAUNAY
2018-03-26 11:51   ` Heiko Stübner
2018-04-04 13:33     ` Tomeu Vizoso
2018-04-05  7:54   ` Minas Harutyunyan
2018-04-05  8:10     ` Tomeu Vizoso
2018-04-05  9:02       ` Grigor Tovmasyan
2018-04-05  8:58   ` Grigor Tovmasyan
2018-04-05  9:51     ` Minas Harutyunyan
2018-04-10 12:28   ` Heiko Stuebner
2018-04-10 13:52     ` Minas Harutyunyan
2018-04-10 15:37       ` Heiko Stübner [this message]
2018-04-11  6:50         ` Minas Harutyunyan
2018-04-23 13:24           ` Tomeu Vizoso
2018-04-24  8:58             ` Heiko Stübner

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=41174786.HiOuqceMIB@diego \
    --to=heiko@sntech.de \
    --cc=Minas.Harutyunyan@synopsys.com \
    --cc=amelie.delaunay@st.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tomeu.vizoso@collabora.com \
    /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