linux-kernel - Re: [PATCH] USB: DWC2: Add VBUS overcurrent detection control.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YMh3Ezr86NLPH+Aj@kroah.com>
Date:   Tue, 15 Jun 2021 11:46:59 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     周琰杰 <zhouyanjie@...yeetech.com>
Cc:     hminas@...opsys.com, paul@...pouillou.net,
        linux-mips@...r.kernel.org, linux-usb@...r.kernel.org,
        linux-kernel@...r.kernel.org, dongsheng.qiu@...enic.com,
        aric.pzqi@...enic.com, sernia.zhou@...mail.com,
        Dragan Čečavac <dragancecavac@...oo.com>
Subject: Re: [PATCH] USB: DWC2: Add VBUS overcurrent detection control.

On Tue, Jun 15, 2021 at 04:16:39PM +0800, 周琰杰 wrote:
> Hi Greg,
> 
> Sorry for taking so long to reply.
> 
> 于 Tue, 23 Mar 2021 16:31:29 +0100
> Greg KH <gregkh@...uxfoundation.org> 写道:
> 
> > On Tue, Mar 23, 2021 at 11:24:26PM +0800, 周琰杰 (Zhou Yanjie) wrote:
> > > Introduce configurable option for enabling GOTGCTL register
> > > bits VbvalidOvEn and VbvalidOvVal. Once selected it disables
> > > VBUS overcurrent detection.
> > > 
> > > This patch is derived from Dragan Čečavac (in the kernel 3.18
> > > tree of CI20). It is very useful for the MIPS Creator CI20(r1).
> > > Without this patch, CI20's OTG port has a great probability to
> > > face overcurrent warning, which breaks the OTG functionality.
> > > 
> > > Signed-off-by: 周琰杰 (Zhou Yanjie) <zhouyanjie@...yeetech.com>
> > > Signed-off-by: Dragan Čečavac <dragancecavac@...oo.com>
> > > ---
> > >  drivers/usb/dwc2/Kconfig | 6 ++++++
> > >  drivers/usb/dwc2/core.c  | 9 +++++++++
> > >  2 files changed, 15 insertions(+)
> > > 
> > > diff --git a/drivers/usb/dwc2/Kconfig b/drivers/usb/dwc2/Kconfig
> > > index c131719..e40d187 100644
> > > --- a/drivers/usb/dwc2/Kconfig
> > > +++ b/drivers/usb/dwc2/Kconfig
> > > @@ -94,4 +94,10 @@ config USB_DWC2_DEBUG_PERIODIC
> > >  	  non-periodic transfers, but of course the debug logs
> > > will be incomplete. Note that this also disables some debug messages
> > >  	  for which the transfer type cannot be deduced.
> > > +
> > > +config USB_DWC2_DISABLE_VOD
> > > +	bool "Disable VBUS overcurrent detection"
> > > +	help
> > > +	  Say Y here to switch off VBUS overcurrent detection. It
> > > enables USB
> > > +	  functionality blocked by overcurrent detection.  
> > 
> > Why would this be a configuration option?  Shouldn't this be dynamic
> > and just work properly automatically?
> > 
> > You should not have to do this on a build-time basis, it should be
> > able to be detected and handled properly at run-time for all devices.
> > 
> 
> I consulted the original author Dragan Čečavac, he think since this is
> a feature which disables overcurrent detection, so we are not sure if
> it could be harmful for some devices. Therefore he advise against
> enabling it in runtime, and in favor that user explicitely has to
> enable it.

That will not work AT ALL for systems that build a generic kernel for
multiple devices (i.e. Android kernels), so please make this a runtime
determination based on the hardware capabilities.

> > If you know this is needed for a specific type of device, detect it
> > and make the change then, otherwise this could break working systems,
> > right?
> 
> According to the information provided by Dragan Čečavac, this function
> (select whether to enable over-current detection through the otgctl
> register) don't seem to be available for all dwc2 controllers, so it
> might make sense to add MACH_INGENIC dependency to
> USB_DWC2_DISABLE_VOD, which could provide additional protection from
> unwanted usage.

Again, make this dynamic and only happen for devices that know it will
work on, based on some hardware information (device type of DT value).
Do not make this happen based on a Kconfig option.

thanks,

greg k-h