mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@opendingux.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: 周琰杰 <zhouyanjie@wanyeetech.com>,
	hminas@synopsys.com, paul@crapouillou.net,
	linux-mips@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, dongsheng.qiu@ingenic.com,
	aric.pzqi@ingenic.com, sernia.zhou@foxmail.com,
	"Dragan Čečavac" <dragancecavac@yahoo.com>
Subject: Re: [PATCH] USB: DWC2: Add VBUS overcurrent detection control.
Date: Tue, 15 Jun 2021 11:06:17 +0100	[thread overview]
Message-ID: <HQMQUQ.3AEG9G7WVQKQ2@opendingux.net> (raw)
In-Reply-To: <YMh3bpRjyTZC2Hsd@kroah.com>

Hi Greg,

Le mar., juin 15 2021 at 11:48:30 +0200, Greg KH 
<gregkh@linuxfoundation.org> a écrit :
> On Tue, Jun 15, 2021 at 09:52:20AM +0100, Paul Cercueil wrote:
>>  Hi Zhou,
>> 
>>  Le mar., juin 15 2021 at 16:16:39 +0800, 周琰杰 
>> <zhouyanjie@wanyeetech.com>
>>  a écrit :
>>  > Hi Greg,
>>  >
>>  > Sorry for taking so long to reply.
>>  >
>>  > 于 Tue, 23 Mar 2021 16:31:29 +0100
>>  > Greg KH <gregkh@linuxfoundation.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@wanyeetech.com>
>>  > >  > Signed-off-by: Dragan Čečavac <dragancecavac@yahoo.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.
>> 
>>  This could still be enabled at runtime, though, via a module 
>> parameter.
>>  Leave it enabled by default, and those who want to disable it can 
>> do it.
> 
> This is not the 1990's, please NEVER add new module parameters,

First time I hear this.

> especially ones that are somehow supposed to be device-specific.
> 
> Remember, module options are code-wide, not device-specific.

Right. I thought "just make the option available on devices that 
support it" but that's not how it works.

-Paul

> Just do this based on the device type, or something else dynamic, do 
> NOT
> make this be forced to be selected by a kernel configuration option 
> or a
> random module option at runtime.
> 
> thanks,
> 
> greg k-h



  reply	other threads:[~2021-06-15 10:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 15:24 周琰杰 (Zhou Yanjie)
2021-03-23 15:31 ` Greg KH
2021-06-15  8:16   ` 周琰杰
2021-06-15  8:52     ` Paul Cercueil
2021-06-15  9:14       ` 周琰杰
2021-06-15  9:48       ` Greg KH
2021-06-15 10:06         ` Paul Cercueil [this message]
2021-06-15  9:46     ` Greg KH

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=HQMQUQ.3AEG9G7WVQKQ2@opendingux.net \
    --to=paul@opendingux.net \
    --cc=aric.pzqi@ingenic.com \
    --cc=dongsheng.qiu@ingenic.com \
    --cc=dragancecavac@yahoo.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hminas@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=sernia.zhou@foxmail.com \
    --cc=zhouyanjie@wanyeetech.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

all inboxes | Powered by JetHome®