linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: "Alan Stern" <stern@rowland.harvard.edu>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	andrew_gabbasov@mentor.com, "Baxter Jim" <jim_baxter@mentor.com>,
	"Natsume, Wataru (ADITJ/SWG)" <wnatsume@jp.adit-jv.com>,
	"Nishiguchi, Naohiro (ADITJ/SWG)" <nnishiguchi@jp.adit-jv.com>,
	浅野恭史 <yasano@jp.adit-jv.com>,
	"kernel test robot" <rong.a.chen@intel.com>,
	"yasushi asano" <yazzep@gmail.com>,
	"Martin Mueller" <Martin.Mueller5@de.bosch.com>,
	"Eugeniu Rosca" <roscaeugeniu@gmail.com>
Subject: Re: [PATCH v3] USB: hub.c: decrease the number of attempts of enumeration scheme
Date: Tue, 15 Sep 2020 13:01:11 +0200	[thread overview]
Message-ID: <20200915110111.GA269380@kroah.com> (raw)
In-Reply-To: <20200915094531.GA8046@lxhi-065.adit-jv.com>

On Tue, Sep 15, 2020 at 11:45:31AM +0200, Eugeniu Rosca wrote:
> Dear Alan,
> Dear Greg,
> 
> On Fri, Sep 11, 2020 at 11:12:28AM -0400, Alan Stern wrote:
> 
> > The thing is, I'm afraid that without these retry loops, some devices
> > will stop working.  If that happens, we will not be able to keep this
> > patch in place; we will just have to accept that we fail the PET test.
> > 
> > Alan Stern
> 
> Does this mean that Linux community leaves no choice but to ship a
> forked kernel (with no chance of alignment to upstream) for
> organizations which design embedded devices where USB plays a key
> role, hence requires passing the USB-IF Compliance Program [*]?

We are saying that if you ship such a kernel, we _KNOW_ that it will
fail to work in a number of known systems.  I doubt you want that to
happen if you care about shipping a device, right?

> Is there hope to give users a knob (build-time or run-time) which would
> enable the behavior expected and thoroughly described in compliance
> docs, particularly chapter "6.7.22 A-UUT Device No Response for
> connection timeout" of "USB On-The-Go and Embedded Host Automated
> Compliance Plan" [**]?

Given that the USB-IF has explicitly kicked-out the Linux community from
its specification work and orginization, I personally don't really care
what they say here.  If you are a member of the USB-IF, please work with
them to fix the test to reflect real-world systems and not an idealized
system.  Last I heard, they wanted nothing to do with Linux systems at
all :(

thanks,

greg k-h

  reply	other threads:[~2020-09-15 11:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEt1RjrQsb6=reKUKV9uJTG4JoJXErhJFj=2TdVx=N1_Ad1GVg@mail.gmail.com>
2020-08-08  6:40 ` [PATCH] [RFC] USB: hub.c: decrease the number of attempts of enumeration scheme Yasushi Asano
2020-08-08 15:16   ` Alan Stern
2020-08-10  0:19     ` [PATCH v2] [RFC] USB: hub.c: decrease the number of attempts of enumeration Yasushi Asano
2020-08-10  0:19       ` [PATCH v2] [RFC] USB: hub.c: decrease the number of attempts of enumeration scheme Yasushi Asano
2020-08-10  7:46         ` Greg KH
2020-08-11 15:20           ` yasushi asano
2020-09-07 15:50             ` [PATCH v3] " Yasushi Asano
2020-09-07 15:50               ` Yasushi Asano
2020-09-08 19:04                 ` Alan Stern
2020-09-10  4:49                   ` yasushi asano
2020-09-11  8:33                     ` yasushi asano
2020-09-11 15:12                       ` Alan Stern
2020-09-15  9:45                         ` Eugeniu Rosca
2020-09-15 11:01                           ` Greg KH [this message]
2020-09-15 14:52                             ` Alan Stern
2020-09-16 10:16                               ` yasushi asano
2020-09-18 15:00                                 ` yasushi asano
2020-09-20 19:21                                   ` Alan Stern
2020-09-21 14:03                                     ` [PATCH] " Yasushi Asano
2020-09-21 14:48                                       ` Alan Stern
     [not found]                                         ` <CAEt1Rjq-DOwN0+_7F0m-kqUHTzm5YPUaXqUOpTszCsqrfLRt5w@mail.gmail.com>
2020-09-21 15:06                                           ` Alan Stern
2020-09-25  1:05                                             ` yasushi asano
2020-09-25 17:21                                               ` yasushi asano
2020-09-25 18:41                                                 ` Alan Stern
2020-09-27 15:43                                                   ` yasushi asano
2020-09-28 15:20                                                     ` [Patch 1/2]: USB: hub: Clean up use of port initialization schemes and retries Alan Stern
2020-09-28 15:22                                                       ` [Patch 2/2]: USB: hub: Add Kconfig option to reduce number of port initialization retries Alan Stern
2020-09-15 14:48                           ` [PATCH v3] USB: hub.c: decrease the number of attempts of enumeration scheme Alan Stern
2020-08-12 17:09           ` [PATCH v2] " Yasushi Asano

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=20200915110111.GA269380@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Martin.Mueller5@de.bosch.com \
    --cc=andrew_gabbasov@mentor.com \
    --cc=erosca@de.adit-jv.com \
    --cc=jim_baxter@mentor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nnishiguchi@jp.adit-jv.com \
    --cc=rong.a.chen@intel.com \
    --cc=roscaeugeniu@gmail.com \
    --cc=stern@rowland.harvard.edu \
    --cc=wnatsume@jp.adit-jv.com \
    --cc=yasano@jp.adit-jv.com \
    --cc=yazzep@gmail.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;
as well as URLs for NNTP newsgroup(s).